Skip to content

Commit b8a8c8c

Browse files
committed
edits
1 parent 26ccad8 commit b8a8c8c

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

articles/active-directory/b2b/self-service-sign-up-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,20 +22,20 @@ ms.collection: M365-identity-device-management
2222
| Self-service sign-up is a public preview feature of Azure Active Directory. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).|
2323
| |
2424

25-
When sharing an application with external users, you might not always know in advance who will need access to an 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 for Azure AD or social identity providers and collect information about the user.
25+
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 for Azure AD or social identity providers and collect information about the user.
2626

2727
> [!NOTE]
2828
> You can associate user flows with apps built by your organization. User flows can't be used for Microsoft apps, like SharePoint or Teams.
2929
3030
## User flow for self-service sign-up
3131

32-
A self-service sign-up user flow creates a sign-up experience for your external users through the application you want to share. The user flow can be associated with one or more of your applications. First you'll enable self-service sign-up for your tenant and federate with any identity providers you want to allow external users to use for sign-in. Then you'll create and customize the sign-up user flow and assign your applications to it.
32+
A self-service sign-up user flow creates a sign-up experience for your external users through the application you want to share. The user flow can be associated with one or more of your applications. First you'll enable self-service sign-up for your tenant and federate with the identity providers you want to allow external users to use for sign-in. Then you'll create and customize the sign-up user flow and assign your applications to it.
3333
You can configure user flow settings to control how the user signs up for the application:
3434

3535
- Account types used for sign-in, such as social accounts like Facebook, or Azure AD accounts
3636
- Attributes to be collected from the user signing up, such as first name, postal code, or country of residency
3737

38-
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 they complete a sign-up user flow, Azure AD generates a token, then redirects the user back to your application. Multiple applications can use the same user flow.
38+
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.
3939

4040
## Example of self-service sign-up
4141

@@ -48,7 +48,7 @@ They use the email of their choice to sign up.
4848

4949
![Example showing selection of Facebook for sign-in](media/self-service-sign-up-overview/example-sign-in-with-facebook.png)
5050

51-
Azure AD creates a relationship with Woodgrove using the partner's Facebook account, and creates a new account.
51+
Azure AD creates a relationship with Woodgrove using the partner's Facebook account, and creates a new account.
5252

5353
Woodgrove wants to know more about the user, like name, business name, business registration code, phone number.
5454

articles/active-directory/b2b/self-service-sign-up-user-flow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ ms.collection: M365-identity-device-management
2525
You can create user flows for apps that are built by your organization. Associating your user flow with an application allows you to enable sign-up on that app. You can choose more than one application to be associated with the user flow. Once you associate the user flow with one or more applications, users who visit that app will be able to sign up using the options configured in the user flow.
2626

2727
> [!NOTE]
28-
> User flows can't be used for Microsoft apps, like SharePoint or Teams.
28+
> You can associate user flows with apps built by your organization. User flows can't be used for Microsoft apps, like SharePoint or Teams.
2929
3030
## Before you begin
3131

0 commit comments

Comments
 (0)