Skip to content

Commit e3b4ad8

Browse files
committed
Merge branch 'main' into release-updatecenterv2-publicpreview
2 parents f4628a4 + cc847e1 commit e3b4ad8

File tree

171 files changed

+3173
-35040
lines changed

Some content is hidden

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

171 files changed

+3173
-35040
lines changed

articles/active-directory-b2c/configure-authentication-in-azure-static-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ Once you've added the app ID and secrete, use the following steps to add the Azu
127127

128128
1. Navigate to `/.auth/login/aadb2c`. The `/.auth/login` points the Azure Static app login endpoint. The `aadb2c` references to your [OpenID Connect identity provider](#31-add-an-openid-connect-identity-provider). The following URL demonstrates an Azure Static app login endpoint: `https://witty-island-11111111.azurestaticapps.net/.auth/login/aadb2c`.
129129
1. Complete the sign up or sign in process.
130-
1. In your browser debugger, [run the following JavaScript in the Console](/microsoft-edge/devtools-guide-chromium/console/console-javascript.md). The JavaScript code will present information about the sign in user.
130+
1. In your browser debugger, [run the following JavaScript in the Console](/microsoft-edge/devtools-guide-chromium/console/console-javascript). The JavaScript code will present information about the sign in user.
131131

132132
```javascript
133133
async function getUserInfo() {
@@ -147,4 +147,4 @@ Once you've added the app ID and secrete, use the following steps to add the Azu
147147
## Next steps
148148
149149
* After successful authentication, you can show display name on the navigation bar. To view the claims that the Azure AD B2C token returns to your app, check out [Accessing user information in Azure Static Web Apps](../static-web-apps/user-information.md).
150-
* Learn how to [customize and enhance the Azure AD B2C authentication experience for your web app](enable-authentication-azure-static-app-options.md).
150+
* Learn how to [customize and enhance the Azure AD B2C authentication experience for your web app](enable-authentication-azure-static-app-options.md).

articles/active-directory-b2c/configure-authentication-in-azure-web-app-file-based.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.custom: "b2c-support"
1515

1616
# Configure authentication in an Azure Web App configuration file by using Azure AD B2C
1717

18-
This article explains how to add Azure Active Directory B2C (Azure AD B2C) authentication functionality to an Azure Web App. For more information, check out the [File-based configuration in Azure App Service authentication](/app-service/configure-authentication-file-based.md) article.
18+
This article explains how to add Azure Active Directory B2C (Azure AD B2C) authentication functionality to an Azure Web App. For more information, check out the [File-based configuration in Azure App Service authentication](/azure/app-service/configure-authentication-file-based) article.
1919

2020
## Overview
2121

@@ -141,6 +141,6 @@ From your server code, the provider-specific tokens are injected into the reques
141141

142142
## Next steps
143143

144-
* After successful authentication, you can show display name on the navigation bar. To view the claims that the Azure AD B2C token returns to your app, check out the [Work with user identities in Azure App Service authentication](/app-service/configure-authentication-user-identities).
145-
* Lear how to [Work with OAuth tokens in Azure App Service authentication](/app-service/configure-authentication-oauth-tokens).
144+
* After successful authentication, you can show display name on the navigation bar. To view the claims that the Azure AD B2C token returns to your app, check out the [Work with user identities in Azure App Service authentication](/azure/app-service/configure-authentication-user-identities).
145+
* Lear how to [Work with OAuth tokens in Azure App Service authentication](/azure/app-service/configure-authentication-oauth-tokens).
146146

articles/active-directory-b2c/configure-authentication-in-azure-web-app.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.custom: "b2c-support"
1515

1616
# Configure authentication in an Azure Web App by using Azure AD B2C
1717

18-
This article explains how to add Azure Active Directory B2C (Azure AD B2C) authentication functionality to an Azure Web App. For more information, check out the [configure your App Service or Azure Functions app to login using an OpenID Connect provider](/app-service/configure-authentication-provider-openid-connect.md) article.
18+
This article explains how to add Azure Active Directory B2C (Azure AD B2C) authentication functionality to an Azure Web App. For more information, check out the [configure your App Service or Azure Functions app to login using an OpenID Connect provider](/azure/app-service/configure-authentication-provider-openid-connect) article.
1919

2020
## Overview
2121

@@ -94,7 +94,7 @@ To register your application, follow these steps:
9494
1. For the **Client Secret** provide the Web App (client) secret from [step 2.2](#step-22-create-a-client-secret).
9595
9696
> [!TIP]
97-
> Your client secret will be stored as an app setting to ensure secrets are stored in a secure fashion. You can update that setting later to use [Key Vault references](/app-service/app-service-key-vault-references.md) if you wish to manage the secret in Azure Key Vault.
97+
> Your client secret will be stored as an app setting to ensure secrets are stored in a secure fashion. You can update that setting later to use [Key Vault references](/azure/app-service/app-service-key-vault-references) if you wish to manage the secret in Azure Key Vault.
9898
9999
1. Keep the rest of the settings with the default values.
100100
1. Press the **Add** button to finish setting up the identity provider.
@@ -119,6 +119,6 @@ From your server code, the provider-specific tokens are injected into the reques
119119
120120
## Next steps
121121
122-
* After successful authentication, you can show display name on the navigation bar. To view the claims that the Azure AD B2C token returns to your app, check out the [Work with user identities in Azure App Service authentication](/app-service/configure-authentication-user-identities).
123-
* Lear how to [Work with OAuth tokens in Azure App Service authentication](/app-service/configure-authentication-oauth-tokens).
122+
* After successful authentication, you can show display name on the navigation bar. To view the claims that the Azure AD B2C token returns to your app, check out the [Work with user identities in Azure App Service authentication](/azure/app-service/configure-authentication-user-identities).
123+
* Lear how to [Work with OAuth tokens in Azure App Service authentication](/azure/app-service/configure-authentication-oauth-tokens).
124124

articles/active-directory-b2c/validation-technical-profile.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Following example uses these validation technical profiles:
8686
```xml
8787
<ValidationTechnicalProfiles>
8888
<ValidationTechnicalProfile ReferenceId="login-NonInteractive" ContinueOnError="false" />
89-
<ValidationTechnicalProfile ReferenceId="REST-ReadProfileFromCustomertsDatabase" ContinueOnError="true" >
89+
<ValidationTechnicalProfile ReferenceId="REST-ReadProfileFromCustomersDatabase" ContinueOnError="true" >
9090
<Preconditions>
9191
<Precondition Type="ClaimsExist" ExecuteActionsIf="false">
9292
<Value>userType</Value>

articles/active-directory/app-provisioning/application-provisioning-quarantine-status.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ After the first failure, the first retry happens within the next 2 hours (usuall
8282
- The fifth retry happens 48 hours after the first failure.
8383
- The sixth retry happens 72 hours after the first failure.
8484
- The seventh retry happens 96 hours after the first failure.
85-
- The eigth retry happens 120 hours after the first failure.
85+
- The eighth retry happens 120 hours after the first failure.
8686

8787
This cycle is repeated every 24 hours until the 30th day when retries are stopped and the job is disabled.
8888

articles/active-directory/cloud-infrastructure-entitlement-management/faqs.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -42,16 +42,12 @@ Yes, non-Azure customers can use our solution. Permissions Management is a multi
4242

4343
## Is Permissions Management available for tenants hosted in the European Union (EU)?
4444

45-
No, the Permissions Management PREVIEW is currently not available for tenants hosted in the European Union (EU).
45+
Yes, Permissions Management is currently for tenants hosted in the European Union (EU).
4646

4747
## If I'm already using Azure AD Privileged Identity Management (PIM) for Azure, what value does Permissions Management provide?
4848

4949
Permissions Management complements Azure AD PIM. Azure AD PIM provides just-in-time access for admin roles in Azure (as well as Microsoft Online Services and apps that use groups), while Permissions Management allows multi-cloud discovery, remediation, and monitoring of privileged access across Azure, AWS, and GCP.
5050

51-
## What languages does Permissions Management support?
52-
53-
Permissions Management currently supports English.
54-
5551
## What public cloud infrastructures are supported by Permissions Management?
5652

5753
Permissions Management currently supports the three major public clouds: Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.
@@ -109,7 +105,6 @@ Yes, Permissions Management has various types of system report available that ca
109105

110106
For information about permissions usage reports, see [Generate and download the Permissions analytics report](product-permissions-analytics-reports.md).
111107

112-
113108
## Does Permissions Management integrate with third-party ITSM (Information Technology Service Management) tools?
114109

115110
Permissions Management integrates with ServiceNow.
@@ -144,7 +139,7 @@ We also have the ability to remove, export or modify specific data should the Gl
144139

145140
## Do I require a license to use Entra Permissions Management?
146141

147-
Yes, as of July 1st, 2022, new customers must acquire a free 90-trial license or a paid license to use the service. You can enable a trial or purchase licenses here: [https://aka.ms/TryPermissionsManagement](https://aka.ms/TryPermissionsManagement)
142+
Yes, as of July 1st, 2022, new customers must acquire a free 90-trial license or a paid license to use the service. You can enable a trial here: [https://aka.ms/TryPermissionsManagement](https://aka.ms/TryPermissionsManagement) or you can directly purchase resource-based licenses here: [https://aka.ms/BuyPermissionsManagement](https://aka.ms/BuyPermissionsManagement)
148143

149144
## What do I do if I’m using Public Preview version of Entra Permissions Management?
150145

articles/active-directory/external-identities/google-federation.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,11 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: how-to
10-
ms.date: 03/02/2022
10+
ms.date: 07/12/2022
1111

1212
ms.author: mimart
1313
author: msmimart
1414
manager: celestedg
15-
ms.reviewer: mal
1615
ms.custom: "it-pro, seo-update-azuread-jan, has-adal-ref"
1716
ms.collection: M365-identity-device-management
1817
---
@@ -33,7 +32,7 @@ By setting up federation with Google, you can allow invited users to sign in to
3332
3433
## What is the experience for the Google user?
3534

36-
When a Google user redeems your invitation, their experience varies depending on whether they're already signed in to Google:
35+
You can invite a Google user to B2B collaboration in various ways. For example, you can [add them to your directory via the Azure portal](b2b-quickstart-add-guest-users-portal.md). When they redeem your invitation, their experience varies depending on whether they're already signed in to Google:
3736

3837
- Guest users who aren't signed in to Google will be prompted to do so.
3938
- Guest users who are already signed in to Google will be prompted to choose the account they want to use. They must choose the account you used to invite them.

articles/active-directory/fundamentals/road-to-the-cloud-implement.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,7 @@ You can enrich user attributes in Azure AD to make more user attributes availabl
2424

2525
* App provisioning - The data source of app provisioning is Azure AD and necessary user attributes must be in there.
2626

27-
* Application authorization - Token issued by Azure AD can include claims generated from user attributes.
28-
29-
* Application can make authorization decision based on the claims in token.
27+
* Application authorization - Token issued by Azure AD can include claims generated from user attributes so that applications can make authorization decision based on the claims in token.
3028

3129
* Group membership population and maintenance - Dynamic groups enables dynamic population of group membership based on user attributes such as department information.
3230

articles/active-directory/fundamentals/road-to-the-cloud-posture.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The five states have exit criteria to help you determine where your environment
3434

3535
The content then provides more detailed guidance organized to help with intentional changes to people, process, and technology to:
3636

37-
* Establish Azure AD capabilities
37+
* Establish Azure AD footprint
3838

3939
* Implement a cloud-first approach
4040

@@ -101,7 +101,7 @@ In enterprise-sized organizations, IAM transformation, or even transformation fr
101101

102102
The transformation between the states is similar to moving locations:
103103

104-
* **Establish new location** - You purchase your destination and establish connectivity between the current location and the new location. This enables you to maintain your productivity and ability to operate. In this content, the activities are described in **[Establish Azure AD capabilities](road-to-the-cloud-establish.md)**. The results transition you to State 2.
104+
* **Establish new location** - You purchase your destination and establish connectivity between the current location and the new location. This enables you to maintain your productivity and ability to operate. In this content, the activities are described in **[Establish Azure AD footprint](road-to-the-cloud-establish.md)**. The results transition you to State 2.
105105

106106
* **Limit new items in old location** - You stop investing in the old location and set policy to stage new items in new location. In this content, the activities are described in **[Implement cloud-first approach](road-to-the-cloud-implement.md)**. The activities set the foundation to migrate at scale and reach State 3.
107107

@@ -122,7 +122,7 @@ As a migration of IAM to Azure AD is started, organizations must determine the p
122122

123123
:::image type="content" source="media/road-to-cloud-posture/road-to-the-cloud-migration.png" alt-text="Table depicting three major milestones that organizations move through when implementing an AD to Azure AD migration. These include Establish Azure AD capabilities, Implement cloud-first approach, and Move workloads to the cloud." border="false":::
124124

125-
## Establish Azure AD capabilities
125+
## Establish Azure AD footprint
126126

127127
* **Initialize tenant** - Create your new Azure AD tenant that supports the vision for your end-state deployment.
128128

articles/active-directory/governance/what-is-identity-lifecycle-management.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -35,19 +35,19 @@ The typical process for establishing identity lifecycle management in an organiz
3535

3636
2. Connect those systems of record with one or more directories and databases used by applications, and resolve any inconsistencies between the directories and the systems of record. For example, a directory may have obsolete data, such as an account for a former employee, that is no longer needed.
3737

38-
3. Determine what processes can be used to supply authoritative information in the absence of a system of record. For example, if there are digital identities but visitors, but the organization has no database for visitors, then it may be necessary to find an alternate way to determine when an digital identity for a visitor is no longer needed.
38+
3. Determine what processes can be used to supply authoritative information in the absence of a system of record. For example, if there are digital identities for visitors, but the organization has no database for visitors, then it may be necessary to find an alternate way to determine when an digital identity for a visitor is no longer needed.
3939

40-
4. Configure that changes from the system of record or other processes are replicated to each of the directories or databases that require an update.
40+
4. Ensure that changes from the system of record or other processes are replicated to each of the directories or databases that require an update.
4141

4242
## Identity lifecycle management for representing employees and other individuals with an organizational relationship
4343

4444
When planning identity lifecycle management for employees, or other individuals with an organizational relationship such as a contractor or student, many organizations model the "join, move, and leave" process. These are:
4545

4646
- Join - when an individual comes into scope of needing access, an identity is needed by those applications, so a new digital identity may need to be created if one is not already available
47-
- Move - when an individual moves between boundaries, that require additional access authorizations to be added or removed to their digital identity
48-
- Leave- when an individual leaves the scope of needing access, access may need to be removed, and subsequently the identity may no longer by required by applications other than for audit or forensics purposes
47+
- Move - when an individual moves between boundaries that require additional access authorizations to be added or removed to their digital identity
48+
- Leave- when an individual leaves the scope of needing access, access may need to be removed, and subsequently the identity may no longer be required by applications other than for audit or forensics purposes
4949

50-
So for example, if a new employee joins your organization, who has never been affiliated with your organization before, that employee will require a new digital identity, represented as a user account in Azure AD. The creation of this account would fall into a "Joiner" process, which could be automated if there was a system of record such as Workday that could indicate when the new employee starts work. Later, if your organization has an employee move from say, Sales to Marketing, they would fall into a "Mover" process. This would require removing the access rights they had in the Sales organization which they no longer require, and granting them rights in the Marketing organization that they new require.
50+
So for example, if a new employee joins your organization and that employee has never been affiliated with your organization before, that employee will require a new digital identity, represented as a user account in Azure AD. The creation of this account would fall into a "Joiner" process, which could be automated if there was a system of record such as Workday that could indicate when the new employee starts work. Later, if your organization has an employee move from say, Sales to Marketing, they would fall into a "Mover" process. This would require removing the access rights they had in the Sales organization which they no longer require, and granting them rights in the Marketing organization that they new require.
5151

5252
## Identity lifecycle management for guests
5353

0 commit comments

Comments
 (0)