Skip to content

Commit d95e165

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into redactfaces
2 parents c526843 + a392a87 commit d95e165

File tree

1,633 files changed

+19440
-13707
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,633 files changed

+19440
-13707
lines changed

.openpublishing.publish.config.json

+6
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,12 @@
7474
"branch": "main",
7575
"branch_mapping": {}
7676
},
77+
{
78+
"path_to_root": "ms-identity-ciam-dotnet-tutorial",
79+
"url": "https://github.com/Azure-Samples/ms-identity-ciam-dotnet-tutorial",
80+
"branch": "main",
81+
"branch_mapping": {}
82+
},
7783
{
7884
"path_to_root": "_themes",
7985
"url": "https://github.com/Microsoft/templates.docs.msft",

.openpublishing.redirection.active-directory.json

+92
Original file line numberDiff line numberDiff line change
@@ -11221,6 +11221,11 @@
1122111221
"redirect_url": "/azure/active-directory/privileged-identity-management/pim-create-azure-ad-roles-and-resource-roles-review",
1122211222
"redirect_document_id": false
1122311223
},
11224+
{
11225+
"source_path_from_root": "/articles/active-directory-b2c/user-manage-inactive.md",
11226+
"redirect_url": "/azure/active-directory-b2c/manage-users-portal",
11227+
"redirect_document_id": false
11228+
},
1122411229
{
1122511230
"source_path_from_root": "/articles/active-directory-b2c/troubleshoot-custom-policies.md",
1122611231
"redirect_url": "/azure/active-directory-b2c/troubleshoot",
@@ -12892,7 +12897,94 @@
1289212897
"source_path_from_root": "/articles/active-directory/authentication/active-directory-certificate-based-authentication-get-started.md",
1289312898
"redirect_url": "/azure/active-directory/authentication/certificate-based-authentication-federation-get-started",
1289412899
"redirect_document_id": false
12900+
},
12901+
{
12902+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-access-create-new-tenant.md",
12903+
"redirect_url": "/azure/active-directory/fundamentals/create-new-tenant",
12904+
"redirect_document_id": false
12905+
},
12906+
{
12907+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-architecture.md",
12908+
"redirect_url": "/azure/active-directory/fundamentals/architecture",
12909+
"redirect_document_id": false
12910+
},
12911+
{
12912+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-data-storage-australia.md",
12913+
"redirect_url": "/azure/active-directory/fundamentals/data-storage-australia",
12914+
"redirect_document_id": false
12915+
},
12916+
{
12917+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-data-storage-australia-newzealand.md",
12918+
"redirect_url": "/azure/active-directory/fundamentals/data-storage-australia-newzealand",
12919+
"redirect_document_id": false
12920+
},
12921+
{
12922+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-data-storage-eu.md",
12923+
"redirect_url": "/azure/active-directory/fundamentals/data-storage-eu",
12924+
"redirect_document_id": false
12925+
},
12926+
{
12927+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-faq.yml",
12928+
"redirect_url": "/azure/active-directory/fundamentals/faq",
12929+
"redirect_document_id": false
12930+
},
12931+
{
12932+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-data-storage-japan.md",
12933+
"redirect_url": "/azure/active-directory/fundamentals/data-storage-japan",
12934+
"redirect_document_id": false
12935+
},
12936+
{
12937+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-get-started-premium.md",
12938+
"redirect_url": "/azure/active-directory/fundamentals/get-started-premium",
12939+
"redirect_document_id": false
12940+
},
12941+
{
12942+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-groups-view-azure-portal.md",
12943+
"redirect_url": "/azure/active-directory/fundamentals/groups-view-azure-portal",
12944+
"redirect_document_id": false
12945+
},
12946+
{
12947+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md",
12948+
"redirect_url": "/azure/active-directory/fundamentals/how-subscriptions-associated-directory",
12949+
"redirect_document_id": false
12950+
},
12951+
{
12952+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-how-to-find-tenant.md",
12953+
"redirect_url": "/azure/active-directory/fundamentals/how-to-find-tenant.md",
12954+
"redirect_document_id": false
12955+
},
12956+
{
12957+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-users-assign-role-azure-portal.md",
12958+
"redirect_url": "/azure/active-directory/fundamentals/how-subscriptions-associated-directory",
12959+
"redirect_document_id": false
12960+
},
12961+
{
12962+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-properties-area.md",
12963+
"redirect_url": "/azure/active-directory/fundamentals/properties-area",
12964+
"redirect_document_id": false
12965+
},
12966+
{
12967+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-licensing-whatis-azure-portal.md",
12968+
"redirect_url": "/azure/active-directory/fundamentals/licensing-whatis-azure-portal",
12969+
"redirect_document_id": false
12970+
},
12971+
{
12972+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-users-reset-password-azure-portal.md",
12973+
"redirect_url": "/azure/active-directory/fundamentals/users-reset-password-azure-portal",
12974+
"redirect_document_id": false
12975+
},
12976+
{
12977+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-users-restore.md",
12978+
"redirect_url": "/azure/active-directory/fundamentals/users-restore",
12979+
"redirect_document_id": false
1289512980
}
1289612981

12982+
12983+
12984+
12985+
12986+
12987+
12988+
1289712989
]
1289812990
}

.openpublishing.redirection.defender-for-cloud.json

+10
Original file line numberDiff line numberDiff line change
@@ -480,6 +480,11 @@
480480
"redirect_url": "/azure/defender-for-cloud/enable-enhanced-security",
481481
"redirect_document_id": true
482482
},
483+
{
484+
"source_path_from_root": "/articles/defender-for-cloud/enable-enhanced-security.md",
485+
"redirect_url": "/azure/defender-for-cloud/enable-all-plans",
486+
"redirect_document_id": true
487+
},
483488
{
484489
"source_path_from_root": "/articles/security-center/enhanced-security-features-overview.md",
485490
"redirect_url": "/azure/defender-for-cloud/enhanced-security-features-overview",
@@ -815,6 +820,11 @@
815820
"redirect_url": "/azure/defender-for-cloud/faq-data-collection-agents",
816821
"redirect_document_id": true
817822
},
823+
{
824+
"source_path_from_root": "/articles/defender-for-cloud/quickstart-enable-database-protections.md",
825+
"redirect_url": "/azure/defender-for-cloud/tutorial-enable-databases-plan",
826+
"redirect_document_id": true
827+
},
818828
{
819829
"source_path_from_root": "/articles/defender-for-cloud/defender-for-storage-exclude.md",
820830
"redirect_url": "/azure/defender-for-cloud/defender-for-storage-classic-enable#exclude-a-storage-account-from-a-protected-subscription-in-the-per-transaction-plan",

.openpublishing.redirection.healthcare-apis.json

+7-2
Original file line numberDiff line numberDiff line change
@@ -479,9 +479,14 @@
479479
},
480480
{
481481
"source_path_from_root": "/articles/healthcare-apis/data-transformation/convert-data.md",
482-
"redirect_url": "/azure/healthcare-apis/fhir/convert-data",
483-
"redirect_document_id": true
482+
"redirect_url": "/azure/healthcare-apis/fhir/overview-of-convert-data",
483+
"redirect_document_id": false
484484
},
485+
{
486+
"source_path_from_root": "/articles/healthcare-apis/fhir/convert-data.md",
487+
"redirect_url": "/azure/healthcare-apis/fhir/overview-of-convert-data",
488+
"redirect_document_id": true
489+
},
485490
{
486491
"source_path_from_root": "/articles/healthcare-apis/fhir/bulk-importing-fhir-data.md",
487492
"redirect_url": "/azure/healthcare-apis/fhir/configure-import-data",

.openpublishing.redirection.json

+20
Original file line numberDiff line numberDiff line change
@@ -23967,6 +23967,26 @@
2396723967
"source_path_from_root": "/articles/active-directory/manage-apps/migrate-okta-sync-provisioning-to-azure-active-directory.md",
2396823968
"redirect_url": "/azure/active-directory/manage-apps/migrate-okta-sync-provisioning",
2396923969
"redirect_document_id": true
23970+
},
23971+
{
23972+
"source_path_from_root": "/articles/networking/connectivty-interoperability-preface.md",
23973+
"redirect_url": "/azure/networking/manage-apps/connectivity-interoperability-preface",
23974+
"redirect_document_id": false
23975+
},
23976+
{
23977+
"source_path_from_root": "/articles/networking/connectivty-interoperability-configuration.md",
23978+
"redirect_url": "/azure/networking/manage-apps/connectivity-interoperability-configuration",
23979+
"redirect_document_id": false
23980+
},
23981+
{
23982+
"source_path_from_root": "/articles/networking/connectivty-interoperability-control-plane.md",
23983+
"redirect_url": "/azure/networking/manage-apps/connectivity-interoperability-control-plane",
23984+
"redirect_document_id": false
23985+
},
23986+
{
23987+
"source_path_from_root": "/articles/networking/connectivty-interoperability-data-plane.md",
23988+
"redirect_url": "/azure/networking/manage-apps/connectivity-interoperability-data-plane",
23989+
"redirect_document_id": false
2397023990
}
2397123991
]
2397223992
}
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
{
2+
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/reliability/reliability-energy-data-services.md",
5+
"redirect_url": "/azure/energy-data-services/reliability-energy-data-services",
6+
"redirect_document_id": true
7+
}
8+
]
9+
}
10+
11+

articles/active-directory-b2c/TOC.yml

+1-4
Original file line numberDiff line numberDiff line change
@@ -403,10 +403,7 @@
403403
displayName: create users, add users, delete users, revoke sessions
404404
- name: Migrate users
405405
href: user-migration.md
406-
displayName: bulk import
407-
- name: Manage inactive users
408-
href: user-manage-inactive.md
409-
displayName: Manage and delete inactive users
406+
displayName: bulk import
410407
- name: Partner integration
411408
items:
412409
- name: N8identity

articles/active-directory-b2c/enable-authentication-web-application-options.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -303,7 +303,7 @@ To support a secured logout redirect in your application, first follow the steps
303303
1. In the **Startup.cs** class, parse the `id_token_hint` value and append the value to the authentication request. The following code snippet demonstrates how to pass the `id_token_hint` value to the authentication request:
304304

305305
```csharp
306-
private async Task OnRedirectToIdentityProviderFunc(RedirectContext context)
306+
private async Task OnRedirectToIdentityProviderForSignOutFunc(RedirectContext context)
307307
{
308308
var id_token_hint = context.Properties.Items.FirstOrDefault(x => x.Key == "id_token_hint").Value;
309309
if (id_token_hint != null)
@@ -324,7 +324,7 @@ To support a secured logout redirect in your application, first follow the steps
324324
{
325325
Configuration.Bind("AzureAdB2C", options);
326326
options.Events ??= new OpenIdConnectEvents();
327-
options.Events.OnRedirectToIdentityProvider += OnRedirectToIdentityProviderFunc;
327+
options.Events.OnRedirectToIdentityProviderForSignOut += OnRedirectToIdentityProviderForSignOutFunc;
328328
options.SaveTokens = true;
329329
});
330330
```
Binary file not shown.
Binary file not shown.

articles/active-directory-b2c/overview.md

+2-60
Original file line numberDiff line numberDiff line change
@@ -66,63 +66,7 @@ Use Azure AD B2C to facilitate identity verification and proofing by collecting
6666

6767
:::image type="content" source="./media/overview/scenario-idproofing.png" alt-text="A diagram showing the user flow for third-party identity proofing.":::
6868

69-
You have learned some of the things you can do with Azure AD B2C as your business-to-customer identity platform. The following sections of this overview walk you through a demo application that uses Azure AD B2C. You're also welcome to move on directly to a more in-depth [technical overview of Azure AD B2C](technical-overview.md).
70-
71-
## Example: WoodGrove Groceries
72-
73-
[WoodGrove Groceries][woodgrove] is a live web application created by Microsoft to demonstrate several Azure AD B2C features. The next few sections review some of the authentication options provided by Azure AD B2C to the WoodGrove website.
74-
75-
### Business overview
76-
77-
WoodGrove is an online grocery store that sells groceries to both individual consumers and business customers. Their business customers buy groceries on behalf of their company, or businesses that they manage.
78-
79-
### Sign-in options
80-
81-
WoodGrove Groceries offers several sign-in options based on the relationship their customers have with the store:
82-
83-
* **Individual** customers can sign-up or sign in with individual accounts, such as with a social identity provider or an email address and password.
84-
* **Business** customers can sign-up or sign in with their enterprise credentials.
85-
* **Partners** and suppliers are individuals who supply the grocery store with products to sell. Partner identity is provided by [Azure Active Directory B2B](../active-directory/external-identities/what-is-b2b.md).
86-
87-
![Individual (B2C), business (B2C), and partner (B2B) sign-in pages](./media/overview/woodgrove-overview.png)
88-
89-
### Authenticate individual customers
90-
91-
When a customer selects **Sign in with your personal account**, they're redirected to a customized sign-in page hosted by Azure AD B2C. You can see in the following image that we've customized the user interface (UI) to look and feel just like the WoodGrove Groceries website. WoodGrove's customers should be unaware that the authentication experience is hosted and secured by Azure AD B2C.
92-
93-
![Custom WoodGrove sign-in page hosted by Azure AD B2C](./media/overview/sign-in.png)
94-
95-
WoodGrove allows their customers to sign-up and sign in by using their Google, Facebook, or Microsoft accounts as their identity provider. Or, they can sign-up by using their email address and a password to create what's called a *local account*.
96-
97-
When a customer selects **Sign-up with your personal account** and then **Sign-up now**, they're presented with a custom sign-up page.
98-
99-
![Custom WoodGrove sign-up page hosted by Azure AD B2C](./media/overview/sign-up.png)
100-
101-
After entering an email address and selecting **Send verification code**, Azure AD B2C sends them the code. Once they enter their code, select **Verify code**, and then enter the other information on the form, they must also agree to the terms of service.
102-
103-
Clicking the **Create** button causes Azure AD B2C to redirect the user back to the WoodGrove Groceries website. When it redirects, Azure AD B2C passes an OpenID Connect authentication token to the WoodGrove web application. The user is now signed-in and ready to go, their display name shown in the top-right corner to indicate they're signed in.
104-
105-
![WoodGrove Groceries website header showing user is signed in](./media/overview/signed-in-individual.png)
106-
107-
### Authenticate business customers
108-
109-
When a customer selects one of the options under **Business customers**, the WoodGrove Groceries website invokes a different Azure AD *B2C policy* than it does for individual customers. You learn what a *B2C policy* is in [technical overview of Azure AD B2C](technical-overview.md)
110-
111-
This policy presents the user with an option to use their corporate credentials for sign-up and sign-in. In the WoodGrove example, users are prompted to sign in with any work or school account. This policy uses a [multi-tenant Azure AD application](../active-directory/develop/howto-convert-app-to-be-multi-tenant.md) and the `/common` Azure AD endpoint to federate Azure AD B2C with any Microsoft 365 customer in the world.
112-
113-
### Authenticate partners
114-
115-
The **Sign in with your supplier account** link uses Azure Active Directory B2B's collaboration functionality. Azure AD B2B is a family of features in Azure Active Directory to manage partner identities. Those identities can be federated from Azure Active Directory for access into Azure AD B2C-protected applications.
116-
117-
Learn more about Azure AD B2B in [What is guest user access in Azure Active Directory B2B?](../active-directory/external-identities/what-is-b2b.md).
118-
119-
<!-- UNCOMMENT WHEN REPO IS UPDATED WITH LATEST DEMO CODE
120-
### Sample code
121-
122-
If you'd like to jump right into the code to see how the WoodGrove Groceries application is built, you can find the repository on GitHub:
123-
124-
[Azure-Samples/active-directory-external-identities-woodgrove-demo][woodgrove-repo] (GitHub)
125-
-->
69+
You have learned some of the things you can do with Azure AD B2C as your business-to-customer identity platform. You may now move on directly to a more in-depth [technical overview of Azure AD B2C](technical-overview.md).
12670

12771
## Next steps
12872

@@ -131,6 +75,4 @@ Now that you have an idea of what Azure AD B2C is and some of the scenarios it c
13175
> [!div class="nextstepaction"]
13276
> [Azure AD B2C technical overview >](technical-overview.md)
13377
134-
<!-- LINKS - External -->
135-
[woodgrove]: https://aka.ms/ciamdemo
136-
[woodgrove-repo]: https://github.com/Azure-Samples/active-directory-external-identities-woodgrove-demo
78+

articles/active-directory-b2c/publish-app-to-azure-ad-app-gallery.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ To allow employees and consumers from any Azure AD tenant to sign in by using Az
7171

7272
In your app, copy the URL of the sign-in endpoint. If you use the [web application sample](configure-authentication-sample-web-app.md), the sign-in URL is `https://localhost:5001/MicrosoftIdentity/Account/SignIn?`. This URL is where the Azure AD app gallery takes users to sign in to your app.
7373

74-
In production environments, the app registration redirect URI is ordinarily a publicly accessible endpoint where your app is running, such as `https://woodgrovedemo.com/Account/SignIn`. The reply URL must begin with `https`.
74+
In production environments, the app registration redirect URI is ordinarily a publicly accessible endpoint where your app is running. The reply URL must begin with `https`.
7575

7676
## Step 4: Publish your Azure AD B2C app
7777

articles/active-directory-b2c/technical-overview.md

+1-7
Original file line numberDiff line numberDiff line change
@@ -117,8 +117,6 @@ In Azure AD B2C, you can craft your users' identity experiences so that the page
117117
> [!NOTE]
118118
> Customizing the pages rendered by third parties when using social accounts is limited to the options provided by that identity provider, and are outside the control of Azure AD B2C.
119119
120-
:::image type="content" source="media/technical-overview/seamless-ux.png" alt-text="Screenshots of brand-customized sign-up sign-in page.":::
121-
122120
For information on UI customization, see:
123121

124122
* [Customize the user interface](customize-ui.md)
@@ -127,11 +125,7 @@ For information on UI customization, see:
127125

128126
## Custom domain
129127

130-
You can customize your Azure AD B2C domain in the redirect URIs for your application. Custom domain allows you to create a seamless experience so that the pages that are shown blend seamlessly with the domain name of your application.
131-
132-
:::image type="content" source="media/technical-overview/custom-domain.png" alt-text="Screenshot of the sign in page of the WoodGrove sample app with a red box highlighting the custom domain in the address bar.":::
133-
134-
From the user's perspective, they remain in your domain during the sign-in process rather than redirecting to the Azure AD B2C default domain .b2clogin.com.
128+
You can customize your Azure AD B2C domain in the redirect URIs for your application. Custom domain allows you to create a seamless experience so that the pages that are shown blend seamlessly with the domain name of your application. From the user's perspective, they remain in your domain during the sign-in process rather than redirecting to the Azure AD B2C default domain .b2clogin.com.
135129

136130
For more information, see [Enable custom domains](custom-domain.md).
137131

articles/active-directory-b2c/tenant-management-directory-quota.md

+1-5
Original file line numberDiff line numberDiff line change
@@ -81,8 +81,4 @@ If your tenant usage is higher that 80%, you can remove inactive users or reques
8181

8282
## Request increase directory quota size
8383

84-
You can request to increase the quota size by [contacting support](find-help-open-support-ticket.md)
85-
86-
## Next steps
87-
88-
- Learn [how to manage inactive user accounts](user-manage-inactive.md).
84+
You can request to increase the quota size by [contacting support](find-help-open-support-ticket.md)

0 commit comments

Comments
 (0)