You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sharing an application with external users, you might not always know in advance who will need access to the application. As an alternative to sending invitations directly to individuals, you can allow external users to sign up for specific applications themselves by enabling self-service sign-up. You can create a personalized sign-up experience by customizing the self-service sign-up user flow. For example, you can provide options to sign up with Azure AD or social identity providers and collect information about the user during the sign-up process.
20
+
When sharing an application with external users, you might not always know in advance who will need access to the application. As an alternative to sending invitations directly to individuals, you can allow external users to sign up for specific applications themselves by enabling [self-service sign-up user flow](self-service-sign-up-user-flow.md). You can create a personalized sign-up experience by customizing the self-service sign-up user flow. For example, you can provide options to sign up with Azure AD or social identity providers and collect information about the user during the sign-up process.
21
21
22
22
> [!NOTE]
23
23
> You can associate user flows with apps built by your organization. User flows can't be used for Microsoft apps, like SharePoint or Teams.
@@ -30,11 +30,11 @@ You can configure user flow settings to control how the user signs up for the ap
30
30
- Account types used for sign-in, such as social accounts like Facebook, or Azure AD accounts
31
31
- Attributes to be collected from the user signing up, such as first name, postal code, or country/region of residency
32
32
33
-
When a user wants to sign in to your application, whether it's a web, mobile, desktop, or single-page application (SPA), the application initiates an authorization request to the user flow-provided endpoint. The user flow defines and controls the user's experience. When the user completes the sign-up user flow, Azure AD generates a token and redirects the user back to your application. Upon completion of sign-up, a guest account is provisioned for the user in the directory. Multiple applications can use the same user flow.
33
+
The user can sign in to your application, via the web, mobile, desktop, or single-page application (SPA). The application initiates an authorization request to the user flow-provided endpoint. The user flow defines and controls the user's experience. When the user completes the sign-up user flow, Azure AD generates a token and redirects the user back to your application. Upon completion of sign-up, a guest account is provisioned for the user in the directory. Multiple applications can use the same user flow.
34
34
35
35
## Example of self-service sign-up
36
36
37
-
The following example illustrates how we're bringing social identity providers to Azure AD with self-service signup capabilities for guest users.
37
+
The following example illustrates how we're bringing social identity providers to Azure AD with self-service sign-up capabilities for guest users.
38
38
A partner of Woodgrove opens the Woodgrove app. They decide they want to sign up for a supplier account, so they select Request your supplier account, which initiates the self-service sign-up flow.
39
39
40
40

@@ -55,4 +55,4 @@ The user enters the information, continues the sign-up flow, and gets access to
55
55
56
56
## Next steps
57
57
58
-
For details, see how to [add self-service sign-up to an app](self-service-sign-up-user-flow.md).
58
+
For details, see how to [add self-service sign-up to an app](self-service-sign-up-user-flow.md).
0 commit comments