Skip to content

Commit f00a598

Browse files
Learn Build Service GitHub AppLearn Build Service GitHub App
authored andcommitted
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents bd2e0fe + 474d4c3 commit f00a598

File tree

552 files changed

+7095
-4214
lines changed

Some content is hidden

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

552 files changed

+7095
-4214
lines changed

.openpublishing.redirection.healthcare-apis.json

Lines changed: 7 additions & 2 deletions
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",
-25.2 KB
Loading
Binary file not shown.
Binary file not shown.

articles/active-directory-b2c/overview.md

Lines changed: 2 additions & 60 deletions
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

Lines changed: 1 addition & 1 deletion
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

Lines changed: 1 addition & 7 deletions
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/whats-new-docs.md

Lines changed: 22 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,28 @@ manager: CelesteDG
1515

1616
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Azure Active Directory](../active-directory/fundamentals/whats-new.md) and [Azure AD B2C developer release notes](custom-policy-developer-notes.md)
1717

18+
## June 2023
19+
20+
### New articles
21+
22+
- [Microsoft Azure Active Directory B2C external identity video series](external-identities-videos.md)
23+
- [Manage directory size quota of your Azure Active Directory B2C tenant](tenant-management-directory-quota.md)
24+
25+
### Updated articles
26+
27+
- [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md) - [Azure AD B2C] Azure AD B2C Go-Local opt-in feature
28+
- [Tutorial: Configure security analytics for Azure Active Directory B2C data with Microsoft Sentinel](configure-security-analytics-sentinel.md) - Removing product name from filename and links. Exempt from Acrolinx by prior arrangement
29+
- [Tutorial: Configure Azure Active Directory B2C with Azure Web Application Firewall](partner-web-application-firewall.md) - Removing product name from filename and links. Exempt from Acrolinx by prior arrangement
30+
- [Title not found in: #240919](azure-ad-external-identities-videos.md) - Delete azure-ad-external-identities-videos.md
31+
- [Build a global identity solution with funnel-based approach](b2c-global-identity-funnel-based-design.md) - Removing product name from filename and links. Exempt from Acrolinx by prior arrangement
32+
- [Azure Active Directory B2C global identity framework proof of concept for funnel-based configuration](b2c-global-identity-proof-of-concept-funnel.md) - Removing product name from filename and links. Exempt from Acrolinx by prior arrangement
33+
- [Azure Active Directory B2C global identity framework proof of concept for region-based configuration](b2c-global-identity-proof-of-concept-regional.md) - Removing product name from filename and links. Exempt from Acrolinx by prior arrangement
34+
- [Build a global identity solution with region-based approach](b2c-global-identity-region-based-design.md) - Removing product name from filename and links. Exempt from Acrolinx by prior arrangement
35+
- [Azure Active Directory B2C global identity framework](b2c-global-identity-solutions.md) - Removing product name from filename and links. Exempt from Acrolinx by prior arrangement
36+
- [Azure Active Directory B2C: What's new](whats-new-docs.md) - [Azure AD B2C] What is new May 2023
37+
- [Use the Azure portal to create and delete consumer users in Azure AD B2C](manage-users-portal.md) - [Azure AD B2C] Revoke user's session
38+
- [Monitor Azure AD B2C with Azure Monitor](azure-monitor.md) - Added steps to disable Azure monitor
39+
1840
## May 2023
1941

2042
### New articles
@@ -37,34 +59,3 @@ Welcome to what's new in Azure Active Directory B2C documentation. This article
3759
- [Configure Transmit Security with Azure Active Directory B2C for passwordless authentication](partner-bindid.md) - Update partner-bindid.md
3860
- [Tutorial: Enable secure hybrid access for applications with Azure Active Directory B2C and F5 BIG-IP](partner-f5.md) - Update partner-f5.md
3961

40-
## March 2023
41-
42-
### Updated articles
43-
44-
- [Configure SAML identity provider options with Azure Active Directory B2C](identity-provider-generic-saml-options.md)
45-
- [Tutorial: Configure BioCatch with Azure Active Directory B2C](partner-biocatch.md)
46-
- [Tutorial: Configure Nok Nok Passport with Azure Active Directory B2C for passwordless FIDO2 authentication](partner-nok-nok.md)
47-
- [Pass an identity provider access token to your application in Azure Active Directory B2C](idp-pass-through-user-flow.md)
48-
- [Tutorial: Configure Haventec Authenticate with Azure Active Directory B2C for single-step, multi-factor passwordless authentication](partner-haventec.md)
49-
- [Configure Trusona Authentication Cloud with Azure Active Directory B2C](partner-trusona.md)
50-
- [Tutorial: Configure IDEMIA Mobile ID with Azure Active Directory B2C](partner-idemia.md)
51-
- [Configure Azure Active Directory B2C with Bluink eID-Me for identity verification](partner-eid-me.md)
52-
- [Tutorial: Configure Azure Active Directory B2C with BlokSec for passwordless authentication](partner-bloksec.md)
53-
- [Tutorial: Configure Azure Active Directory B2C with Azure Web Application Firewall](partner-web-application-firewall.md)
54-
- [Tutorial to configure Saviynt with Azure Active Directory B2C](partner-saviynt.md)
55-
- [Tutorial: Configure Keyless with Azure Active Directory B2C](partner-keyless.md)
56-
- [Tutorial: Configure security analytics for Azure Active Directory B2C data with Microsoft Sentinel](configure-security-analytics-sentinel.md)
57-
- [Configure authentication in a sample Python web app by using Azure AD B2C](configure-authentication-sample-python-web-app.md)
58-
- [Billing model for Azure Active Directory B2C](billing.md)
59-
- [Azure Active Directory B2C: Region availability & data residency](data-residency.md)
60-
- ['Azure AD B2C: Frequently asked questions (FAQ)'](faq.yml)
61-
- [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md)
62-
63-
## February 2023
64-
65-
### Updated articles
66-
67-
- [Azure Active Directory B2C code samples](integrate-with-app-code-samples.md)
68-
- [JSON claims transformations](json-transformations.md)
69-
- [Set up sign-in for a specific Azure Active Directory organization in Azure Active Directory B2C](identity-provider-azure-ad-single-tenant.md)
70-
- [Page layout versions](page-layout.md)

articles/active-directory/app-provisioning/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,8 @@ items:
3535
href: on-premises-web-services-connector.md
3636
- name: Provisioning with custom connectors
3737
href: on-premises-custom-connector.md
38+
- name: Provisioning to SAP ECC 7.0
39+
href: on-premises-sap-connector-configure.md
3840
- name: Customize attribute mappings
3941
href: customize-application-attributes.md
4042
- name: Concepts

articles/active-directory/authentication/how-to-mfa-server-migration-utility.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: multi-factor-authentication
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: how-to
9-
ms.date: 05/01/2023
9+
ms.date: 06/29/2023
1010

1111
ms.author: justinha
1212
author: justinha
@@ -217,7 +217,13 @@ The **Settings** option allows you to change the settings for the migration proc
217217

218218
:::image type="content" border="true" source="./media/how-to-mfa-server-migration-utility/settings.png" alt-text="Screenshot of settings.":::
219219

220-
- Migrate – This setting allows you to specify which method(s) should be migrated for the selection of users
220+
- Migrate – there are three options for migrating the user's default authentication method:
221+
- Always migrate
222+
- Only migrate if not already set in Azure AD
223+
- Set to the most secure method available if not already set in Azure AD
224+
225+
These options provide flexibility when you migrate the default method. In addition, the Authentication methods policy is checked during migration. If the default method being migrated isn't allowed by policy, it's set to the most secure method available instead.
226+
221227
- User Match – Allows you to specify a different on-premises Active Directory attribute for matching Azure AD UPN instead of the default match to userPrincipalName:
222228
- The migration utility tries direct matching to UPN before using the on-premises Active Directory attribute.
223229
- If no match is found, it calls a Windows API to find the Azure AD UPN and get the SID, which it uses to search the MFA Server user list.

0 commit comments

Comments
 (0)