Skip to content

Commit d4cadfa

Browse files
committed
add tip referencing customer content
1 parent d323436 commit d4cadfa

File tree

7 files changed

+9
-9
lines changed

7 files changed

+9
-9
lines changed

articles/active-directory/external-identities/facebook-federation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ ms.collection: engagement-fy23, M365-identity-device-management
2121
# Add Facebook as an identity provider for External Identities
2222

2323
> [!TIP]
24-
> This article applies to workforce tenants. For customer tenant information, see [Add Facebook as an identity provider](/customers/how-to-facebook-federation-customers.md).
24+
> This article applies to workforce tenants. For customer tenant information, see [Add Facebook as an identity provider](customers/how-to-facebook-federation-customers.md).
2525
2626
You can add Facebook to your self-service sign-up user flows so that users can sign in to your applications using their own Facebook accounts. To allow users to sign in using Facebook, you'll first need to [enable self-service sign-up](self-service-sign-up-user-flow.md) for your tenant. After you add Facebook as an identity provider, set up a user flow for the application and select Facebook as one of the sign-in options.
2727

articles/active-directory/external-identities/google-federation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
1919
# Add Google as an identity provider for B2B guest users
2020

2121
> [!TIP]
22-
> This article applies to workforce tenants. For customer tenant information, see [Add Google as an identity provider](/customers/how-to-google-federation-customers.md).
22+
> This article applies to workforce tenants. For customer tenant information, see [Add Google as an identity provider](customers/how-to-google-federation-customers.md).
2323
2424
By setting up federation with Google, you can allow invited users to sign in to your shared apps and resources with their own Gmail accounts, without having to create Microsoft accounts. After you've added Google as one of your application's sign-in options, on the **Sign in** page, a user can simply enter the Gmail address they use to sign in to Google.
2525

articles/active-directory/external-identities/identity-providers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717
# Identity Providers for External Identities
1818

1919
> [!TIP]
20-
> This article applies to workforce tenants. For customer tenant information, see [Authentication methods and identity providers for customers](/customers/concept-authentication-methods-customers.md).
20+
> This article applies to workforce tenants. For customer tenant information, see [Authentication methods and identity providers for customers](customers/concept-authentication-methods-customers.md).
2121
2222
An *identity provider* creates, maintains, and manages identity information while providing authentication services to applications. When sharing your apps and resources with external users, Azure AD is the default identity provider for sharing. This means when you invite external users who already have an Azure AD or Microsoft account, they can automatically sign in without further configuration on your part.
2323

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ ms.collection: M365-identity-device-management
2020
Self-service sign-up is an essential feature for your External ID workforce and customer scenarios. It gives your partners, consumers, and other external users a frictionless way to sign up and get access to your apps without any intervention on your part.
2121

2222
- In a B2B collaboration scenario, you might not always know in advance who will need access to an application you want to share. As an alternative to sending invitations directly to individuals, you can allow external users to sign up for specific applications themselves. Learn how to [create a self-service sign-up user flow for B2B collaboration](self-service-sign-up-user-flow.md).
23-
- In a customer identity and access management (CIAM) scenario, probably one of your topmost priorities is to create a personalized sign-up experience for the apps you build for consumers. You can do so by configuring self-service sign-up user flows. Learn more about [planning the customer experience](concept-planning-your-solution.md) or [creating a sign-up and sign-in user flow for customers](how-to-user-flow-sign-up-sign-in-customers.md).
23+
- In a customer identity and access management (CIAM) scenario, probably one of your topmost priorities is to create a personalized sign-up experience for the apps you build for consumers. You can do so by configuring self-service sign-up user flows. Learn more about [planning the customer experience](customers/concept-planning-your-solution.md) or [creating a sign-up and sign-in user flow for customers](customers/how-to-user-flow-sign-up-sign-in-customers.md).
2424

2525
In either scenario, you can create a personalized sign-up experience by customizing the look and feel, providing sign-in with social identity providers, and collecting information about the user during the sign-up process.
2626

@@ -64,5 +64,5 @@ User flows for B2B collaboration:
6464

6565
User flows for customer identity and access management (CIAM):
6666

67-
- [Plan a sign-up experience for customers or consumers](concept-planning-your-solution.md)
68-
- [Create a sign-up and sign-in user flow for customers or consumers](how-to-user-flow-sign-up-sign-in-customers.md).
67+
- [Plan a sign-up experience for customers or consumers](customers/concept-planning-your-solution.md)
68+
- [Create a sign-up and sign-in user flow for customers or consumers](customers/how-to-user-flow-sign-up-sign-in-customers.md).

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ ms.collection: engagement-fy23, M365-identity-device-management
2020
# Add a self-service sign-up user flow to an app
2121

2222
> [!TIP]
23-
> This article applies to workforce tenants. For customer tenant information, see [Create a sign-up and sign-in user flow for customers](/customers/how-to-user-flow-sign-up-sign-in-customers.md).
23+
> This article applies to workforce tenants. For customer tenant information, see [Create a sign-up and sign-in user flow for customers](customers/how-to-user-flow-sign-up-sign-in-customers.md).
2424
2525
For applications you build, you can create user flows that allow a user to sign up for an app and create a new guest account. A self-service sign-up user flow defines the series of steps the user will follow during sign-up, the [identity providers](identity-providers.md) you'll allow them to use, and the user attributes you want to collect. You can associate one or more applications with a single user flow.
2626

articles/active-directory/external-identities/user-flow-add-custom-attributes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.collection: M365-identity-device-management
1919
# Define custom attributes for user flows
2020

2121
> [!TIP]
22-
> This article applies to workforce tenants. For customer tenant information, see [Collect user attributes during sign-up](/customers/how-to-define-custom-attributes.md).
22+
> This article applies to workforce tenants. For customer tenant information, see [Collect user attributes during sign-up](customers/how-to-define-custom-attributes.md).
2323
2424
For each application, you might have different requirements for the information you want to collect during sign-up. Azure AD comes with a built-in set of information stored in attributes, such as Given Name, Surname, City, and Postal Code. With Azure AD, you can extend the set of attributes stored on a guest account when the external user signs up through a user flow.
2525

articles/active-directory/external-identities/user-flow-customize-language.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.custom: engagement-fy23
1919
# Language customization in Azure Active Directory
2020

2121
> [!TIP]
22-
> This article applies to workforce tenants. For customer tenant information, see [Customize the language of the authentication experience](/customers/how-to-customize-languages-customers.md).
22+
> This article applies to workforce tenants. For customer tenant information, see [Customize the language of the authentication experience](customers/how-to-customize-languages-customers.md).
2323
2424
Language customization in Azure Active Directory (Azure AD) allows your user flow to accommodate different languages to suit your user's needs. Microsoft provides the translations for [36 languages](#supported-languages). In this article, you'll learn how to customize the attribute names on the [attribute collection page](self-service-sign-up-user-flow.md#select-the-layout-of-the-attribute-collection-form), even if your experience is provided for only a single language.
2525

0 commit comments

Comments
 (0)