Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions policies/migrate-to-entra-external-id-for-customers/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This sample will use AAD B2C as the journey orchestrator, whilst creating and au

## How it works

Users are sent to the AAD B2C authentiaction endpoint. An Azure function orchestrates all Read/Write operations to the Entra External Id directory.
Users are sent to the AAD B2C authentication endpoint. An Azure function orchestrates all Read/Write operations to the Entra External Id directory.

![High level design](media/high-level-design.png)

Expand Down Expand Up @@ -53,4 +53,4 @@ Scenarios to test:
1. Assign the user to a group/role in Entra External Id tenant, then perform a sign in
1. Create a User Flow in Entra External Id tenant, and perform a Sign In via Entra External Id tenant with an account that was created via this AAD B2C custom policy
1. Sign in via this AAD B2C custom policy with an account that was created using the User Flow from Entra External Id tenant
1. View the User Profile after Sign Up in the Entra External Id tenant. Ensure the `Authentication Methods` menu is correctly populated with the users phone number visible, after sign up via this AAD B2C custom policy
1. View the User Profile after Sign Up in the Entra External Id tenant. Ensure the `Authentication Methods` menu is correctly populated with the users phone number visible, after sign up via this AAD B2C custom policy