Skip to content

Commit 3f6d347

Browse files
Merge pull request #108064 from MicrosoftDocs/repo_sync_working_branch
Resolve syncing conflicts from repo_sync_working_branch to main
2 parents 27ce474 + b0d6d69 commit 3f6d347

File tree

1,100 files changed

+13068
-5114
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,100 files changed

+13068
-5114
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,26 @@
4545
"redirect_url": "/azure/azure-monitor/app/app-insights-overview",
4646
"redirect_document_id": false
4747
},
48+
{
49+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-runtime-exceptions.md",
50+
"redirect_url": "/previous-versions/azure/azure-monitor/app/tutorial-runtime-exceptions",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-performance.md",
55+
"redirect_url": "/previous-versions/azure/azure-monitor/app/tutorial-performance",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-users.md",
60+
"redirect_url": "/previous-versions/azure/azure-monitor/app/tutorial-users",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path_from_root": "/articles/azure-monitor/app/custom-data-correlation.md",
65+
"redirect_url": "/previous-versions/azure/azure-monitor/app/custom-data-correlation",
66+
"redirect_document_id": false
67+
},
4868
{
4969
"source_path_from_root": "/articles/azure-monitor/app/correlation.md",
5070
"redirect_url": "/previous-versions/azure/azure-monitor/app/distributed-tracing-telemetry-correlation",
-4.51 KB
Loading

articles/active-directory/app-provisioning/plan-auto-user-provisioning.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.topic: conceptual
1010
ms.workload: identity
11-
ms.date: 04/11/2023
11+
ms.date: 04/12/2023
1212
ms.author: kenwith
1313
ms.reviewer: arvinh
1414
---
@@ -57,7 +57,7 @@ This article uses the following terms:
5757

5858
* Target system - The repository of users that the Azure AD provisions to. The Target system is typically a SaaS application such as ServiceNow, Zscaler, and Slack. The target system can also be an on-premises system such as AD.
5959

60-
* [System for Cross-domain Identity Management (SCIM)](https://aka.ms/scimoverview) - An open standard that allows for the automation of user provisioning. SCIM communicates user identity data between identity providers such as Microsoft, and service providers like Salesforce or other SaaS apps that require user identity information.
60+
* [System for Cross-domain Identity Management (SCIM)](https://aka.ms/scimoverview) - An open standard that allows for the automation of user provisioning. SCIM communicates user identity data between identity providers and service providers. Microsoft is an example of an identity provider. Salesforce is an example of a service provider. Service providers require user identity information and an identity provider fulfills that need. SCIM is the mechanism the identity provider and service provider use to send information back and forth.
6161

6262
### Training resources
6363

@@ -128,7 +128,7 @@ When technology projects fail, it's typically because of mismatched expectations
128128

129129
### Plan communications
130130

131-
Communication is critical to the success of any new service. Proactively communicate with your users how their experience will change, when it will change, and how to gain support if they experience issues.
131+
Communication is critical to the success of any new service. Proactively communicate to your users about their experience, how the experience is changing, when to expect any change, and how to gain support if they experience issues.
132132

133133
### Plan a pilot
134134

@@ -140,7 +140,7 @@ A pilot allows you to test with a small group before deploying a capability for
140140

141141
In your first wave, target IT, usability, and other appropriate users who can test and provide feedback. Use this feedback to further develop the communications and instructions you send to your users, and to give insights into the types of issues your support staff may see.
142142

143-
Widen the rollout to larger groups of users by increasing the scope of the group(s) targeted. This can be done through [dynamic group membership](../enterprise-users/groups-dynamic-membership.md), or by manually adding users to the targeted group(s).
143+
Widen the rollout to larger groups of users by increasing the scope of the group(s) targeted. Increasing the scope of the group(s) is done through [dynamic group membership](../enterprise-users/groups-dynamic-membership.md), or by manually adding users to the targeted group(s).
144144

145145
## Plan application connections and administration
146146

@@ -150,7 +150,7 @@ Use the Azure portal to view and manage all the applications that support provis
150150

151151
The actual steps required to enable and configure automatic provisioning vary depending on the application. If the application you wish to automatically provision is listed in the [Azure AD SaaS app gallery](../saas-apps/tutorial-list.md), then you should select the [app-specific integration tutorial](../saas-apps/tutorial-list.md) to configure its pre-integrated user provisioning connector.
152152

153-
If not, follow the steps below:
153+
If not, follow the steps:
154154

155155
1. [Create a request](../manage-apps/v2-howto-app-gallery-listing.md) for a pre-integrated user provisioning connector. Our team will work with you and the application developer to onboard your application to our platform if it supports SCIM.
156156

@@ -164,7 +164,7 @@ For more information, see [What applications and systems can I use with Azure AD
164164

165165
Setting up automatic user provisioning is a per-application process. For each application, you need to provide [administrator credentials](../app-provisioning/configure-automatic-user-provisioning-portal.md) to connect to the target system’s user management endpoint.
166166

167-
The image below shows one version of the required admin credentials:
167+
The image shows one version of the required admin credentials:
168168

169169
![Provisioning screen to manage user account provisioning settings](./media/plan-auto-user-provisioning/userprovisioning-admincredentials.png)
170170

@@ -235,7 +235,7 @@ It's common for a security review to be required as part of a deployment. If you
235235

236236
### Plan rollback
237237

238-
If the automatic user provisioning implementation fails to work as desired in the production environment, the following rollback steps below can assist you in reverting to a previous known good state:
238+
If the automatic user provisioning implementation fails to work as desired in the production environment, the following rollback steps can assist you in reverting to a previous known good state:
239239

240240
1. Review the [provisioning logs](../app-provisioning/check-status-user-account-provisioning.md) to determine what incorrect operations occurred on the affected users and/or groups.
241241

articles/active-directory/authentication/how-to-migrate-mfa-server-to-azure-mfa.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,9 +107,10 @@ As part of enrolling users to use Microsoft Authenticator as a second factor, we
107107
Microsoft Identity Manager (MIM) SSPR can use MFA Server to invoke SMS one-time passcodes as part of the password reset flow.
108108
MIM can't be configured to use Azure AD Multi-Factor Authentication.
109109
We recommend you evaluate moving your SSPR service to Azure AD SSPR.
110-
111110
You can use the opportunity of users registering for Azure AD Multi-Factor Authentication to use the combined registration experience to register for Azure AD SSPR.
112111

112+
If you can't move your SSPR service, or you leverage MFA Server to invoke MFA requests for Privileged Access Management (PAM) scenarios, we recommend you update to an [alternate 3rd party MFA option](https://learn.microsoft.com/microsoft-identity-manager/working-with-custommfaserver-for-mim).
113+
113114
### RADIUS clients and Azure AD Multi-Factor Authentication
114115

115116
MFA Server supports RADIUS to invoke multifactor authentication for applications and network devices that support the protocol.

articles/active-directory/authentication/howto-mfa-app-passwords.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,8 +99,7 @@ By default, users can't create app passwords. The app passwords feature must be
9999

100100
When users complete their initial registration for Azure AD Multi-Factor Authentication, there's an option to create app passwords at the end of the registration process.
101101

102-
Users can also create app passwords after registration. For more information and detailed steps for your users, see the following resources:
103-
* [What are app passwords in Azure AD Multi-Factor Authentication?](https://support.microsoft.com/account-billing/manage-app-passwords-for-two-step-verification-d6dc8c6d-4bf7-4851-ad95-6d07799387e9)
102+
Users can also create app passwords after registration. For more information and detailed steps for your users, see the following resource:
104103
* [Create app passwords from the Security info page](https://support.microsoft.com/account-billing/create-app-passwords-from-the-security-info-preview-page-d8bc744a-ce3f-4d4d-89c9-eb38ab9d4137)
105104

106105
## Next steps
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
title: "Quickstart: Add sign in to a React SPA"
3+
description: Learn how to run a sample React SPA to sign in users
4+
services: active-directory
5+
author: kengaderdus
6+
manager: mwongerapk
7+
ms.author: kengaderdus
8+
ms.service: active-directory
9+
ms.workload: identity
10+
ROBOTS: NOINDEX
11+
ms.subservice: ciam
12+
ms.topic: portal
13+
ms.date: 04/12/2023
14+
---
15+
16+
# Portal quickstart for React SPA
17+
18+
> [!div renderon="portal" class="sxs-lookup"]
19+
> In this quickstart, you download and run a code sample that demonstrates how a React single-page application (SPA) can sign in users with Azure AD CIAM.
20+
>
21+
> ## Prerequisites
22+
>
23+
> * Azure subscription - [Create an Azure subscription for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)
24+
> * [Node.js](https://nodejs.org/en/download/)
25+
> * [Visual Studio Code](https://code.visualstudio.com/download) or another code editor
26+
>
27+
> ## Download the code
28+
>
29+
> > [!div class="nextstepaction"]
30+
> > [Download the code sample](https://github.com/Azure-Samples/ms-identity-ciam-javascript-tutorial/archive/react-quickstart.zip)
31+
>
32+
> ## Run the sample
33+
>
34+
> 1. Unzip the downloaded file.
35+
>
36+
> 1. Locate the folder that contains the `package.json` file in your terminal, then run the following command:
37+
>
38+
> ```console
39+
> npm install && npm start
40+
> ```
41+
>
42+
> 1. Open your browser and visit `http://locahost:3000`.
43+
>
44+
> 1. Select the **Sign-in** link on the navigation bar.
45+
>

articles/active-directory/fundamentals/whats-deprecated-azure-ad.md

Lines changed: 21 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.workload: identity
99
ms.topic: conceptual
1010
ms.date: 01/27/2023
1111
ms.author: jricketts
12-
ms.reviewer: ramical
12+
ms.reviewer: merill
1313
ms.custom: it-pro
1414

1515
---
@@ -30,12 +30,25 @@ Use the following table to learn about changes including deprecations, retiremen
3030
|Functionality, feature, or service|Change|Change date |
3131
|---|---|---:|
3232
|Microsoft Authenticator app [Number matching](../authentication/how-to-mfa-number-match.md)|Feature change|May 8, 2023|
33-
|Azure AD DS [virtual network deployments](../../active-directory-domain-services/migrate-from-classic-vnet.md)|Retirement|Mar 1, 2023|
33+
|[My Groups experience](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Feature change|May 2023|
34+
|[My Apps browser extension](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Feature change|May 2023|
35+
|[System-preferred authentication methods](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Feature change|On GA|
36+
|[Azure AD Authentication Library (ADAL)](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Retirement|Jun 30, 2023|
37+
|[Azure AD Graph API](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Deprecation|Jun 30, 2023|
38+
|[Azure AD PowerShell and MSOnline PowerShell](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Deprecation|Jun 30, 2023|
39+
|[My Apps improvements](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Feature change|Jun 30, 2023|
40+
|[Terms of Use experience](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Feature change|Jul 2023|
41+
|[Azure AD MFA Server](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Retirement|Sep 30, 2024|
42+
|[Legacy MFA & SSPR policy](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-march-2023-train/ba-p/2967448)|Retirement|Sep 30, 2024|
43+
|[‘Require approved client app’ Conditional Access Grant](https://aka.ms/RetireApprovedClientApp)|Retirement|Mar 31, 2026|
44+
45+
46+
## Past changes
47+
48+
|Functionality, feature, or service|Change|Change date |
49+
|---|---|---:|
50+
|[Azure AD Domain Services virtual network deployments](../../active-directory-domain-services/migrate-from-classic-vnet.md)|Retirement|Mar 1, 2023|
3451
|[License management API, PowerShell](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/migrate-your-apps-to-access-the-license-managements-apis-from/ba-p/2464366)|Retirement|*Mar 31, 2023|
35-
|[Azure AD Authentication Library (ADAL)](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-september-2022-train/ba-p/2967454)|Retirement|Jun 30, 2023|
36-
|[Azure AD Graph API](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-september-2022-train/ba-p/2967454)|Deprecation|Jun 30, 2023|
37-
|[Azure AD PowerShell and MSOnline PowerShell](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-september-2022-train/ba-p/2967454)|Deprecation|Jun 30, 2023|
38-
|[Azure AD MFA Server](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/microsoft-entra-change-announcements-september-2022-train/ba-p/2967454)|Retirement|Sep 30, 2024|
3952

4053
\* The legacy license management API and PowerShell cmdlets will not work for **new tenants** created after Nov 1, 2022.
4154

@@ -51,11 +64,9 @@ Use the definitions in this section help clarify the state, availability, and su
5164

5265
|Category|Definition|Communication schedule|
5366
|---|---|---|
54-
|Deprecation|The state of a feature, functionality, or service no longer in active development. A deprecated feature might be retired and removed from future releases.|2 times per year: March and September|
55-
|Retirement|Signals retirement in a specified period. Customers can’t adopt the service or feature, and engineering investments are reduced. Later, the feature reaches end-of-life and is unavailable to any customer.|2 times per year: March and September|
67+
|Retirement|Signals retirement of a feature, capability, or product in a specified period. Customers can’t adopt the service or feature, and engineering investments are reduced. Later, the feature reaches end-of-life and is unavailable to any customer.|2 times per year: March and September|
5668
|Breaking change|A change that might break the customer or partner experience if action isn’t taken, or a change made, for continued operation.|4 times per year: March, June, September, and December|
57-
|Feature change|Change to an IDNA feature that requires no customer action, but is noticeable to them. Typically, these changes are in the user interface/user experperience (UI/UX).|4 times per year: March, June, September, and December|
58-
|Rebranding|A new name, term, symbol, design, concept or combination thereof for an established brand to develop a differentiated experience.|As scheduled or announced|
69+
|Feature change|Change to an existing Identity feature that requires no customer action, but is noticeable to them. Typically, these changes are in the user interface/user experperience (UI/UX).|4 times per year: March, June, September, and December|
5970

6071
### Terminology
6172

articles/active-directory/reports-monitoring/howto-manage-inactive-user-accounts.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,6 @@ The following details relate to the `lastSignInDateTime` property.
5757

5858
- To read the property, you need to grant the app the following Microsoft Graph permissions:
5959
- AuditLog.Read.All
60-
- Directory.Read.All
6160
- User.Read.All
6261

6362
- Each interactive sign-in that was successful results in an update of the underlying data store. Typically, successful sign-ins show up in the related sign-in report within 10 minutes.

articles/active-directory/roles/TOC.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@
3030
href: security-planning.md
3131
- name: Create emergency accounts
3232
href: security-emergency-access.md
33+
- name: Protected actions
34+
href: protected-actions-overview.md
3335
- name: How-to guides
3436
items:
3537
- name: Prerequisites
@@ -84,6 +86,10 @@
8486
href: admin-units-members-dynamic.md
8587
- name: Assign roles with scope
8688
href: admin-units-assign-roles.md
89+
- name: Protected actions
90+
items:
91+
- name: Add, remove, or test
92+
href: protected-actions-add.md
8793
- name: Delegate
8894
items:
8995
- name: Delegate admin role

articles/active-directory/roles/custom-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ Azure AD provides multiple options for assigning roles:
101101

102102
## License requirements
103103

104-
Using built-in roles in Azure AD is free, while custom roles require an Azure AD Premium P1 license. To find the right license for your requirements, see [Comparing generally available features of the Free and Premium editions](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing).
104+
Using built-in roles in Azure AD is free. Using custom roles require an Azure AD Premium P1 license for every user with a custom role assignment. To find the right license for your requirements, see [Comparing generally available features of the Free and Premium editions](https://www.microsoft.com/security/business/identity-access-management/azure-ad-pricing).
105105

106106
## Next steps
107107

0 commit comments

Comments
 (0)