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
Copy file name to clipboardExpand all lines: articles/active-directory/external-identities/azure-ad-account.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,36 +7,37 @@ services: active-directory
7
7
ms.service: active-directory
8
8
ms.subservice: B2B
9
9
ms.topic: how-to
10
-
ms.date: 10/06/2022
10
+
ms.date: 11/11/2022
11
11
12
12
ms.author: mimart
13
13
author: msmimart
14
14
manager: celestedg
15
15
ms.collection: M365-identity-device-management
16
16
ms.custom: engagement-fy23
17
+
# Customer intent: As a tenant administrator, I want to add Azure AD as an identity provider for external guest users.
17
18
---
18
19
19
20
# Add Azure Active Directory (Azure AD) as an identity provider for External Identities
20
21
21
-
Azure Active Directory is available as an identity provider option for B2B collaboration by default. If an external guest user has an Azure AD account through work or school, they can redeem your B2B collaboration invitations or complete your sign-up user flows using their Azure AD account.
22
+
Azure Active Directory is available as an identity provider option for [B2B collaboration](what-is-b2b.md) by default. If an external guest user has an Azure AD account through work or school, they can redeem your B2B collaboration invitations or complete your sign-up user flows using their Azure AD account.
22
23
23
24
## Guest sign-in using Azure Active Directory accounts
24
25
25
-
Azure Active Directory is available in the list of External Identities identity providers by default. No further configuration is needed to allow guest users to sign in with their Azure AD account using either the invitation flow or a [self-service sign-up user flow](self-service-sign-up-overview.md).
26
+
Azure Active Directory is available in the list of External Identities identity providers by default. No further configuration is needed to allow guest users to sign in with their Azure AD account using either the [invitation flow](redemption-experience.md#invitation-redemption-flow) or a [self-service sign-up user flow](self-service-sign-up-overview.md).
26
27
27
-

28
+
:::image type="content" source="media/azure-ad-account/azure-ad-account-identity-provider.png" alt-text="Screenshot of Azure AD account in the identity provider list." lightbox="media/azure-ad-account/azure-ad-account-identity-provider.png":::
28
29
29
30
### Azure AD account in the invitation flow
30
31
31
32
When you [invite a guest user](add-users-administrator.md) to B2B collaboration, you can specify their Azure AD account as the email address they'll use to sign in.
32
33
33
-

34
+
:::image type="content" source="media/azure-ad-account/azure-ad-account-invite.png" alt-text="Screenshot of inviting a guest user using the Azure AD account." lightbox="media/azure-ad-account/azure-ad-account-invite.png":::
34
35
35
36
### Azure AD account in self-service sign-up user flows
36
37
37
38
Azure AD account is an identity provider option for your self-service sign-up user flows. Users can sign up for your applications using their own Azure AD accounts. First, you'll need to [enable self-service sign-up](self-service-sign-up-user-flow.md) for your tenant. Then you can set up a user flow for the application and select Azure Active Directory as one of the sign-in options.
38
39
39
-

40
+
:::image type="content" source="media/azure-ad-account/azure-ad-account-user-flow.png" alt-text="Screenshot of Azure Ad account in a self-service sign-up user flow." lightbox="media/azure-ad-account/azure-ad-account-user-flow.png":::
40
41
41
42
## Verifying the application's publisher domain
42
43
As of November 2020, new application registrations show up as unverified in the user consent prompt unless [the application's publisher domain is verified](../develop/howto-configure-publisher-domain.md), ***and*** the company’s identity has been verified with the Microsoft Partner Network and associated with the application. ([Learn more](../develop/publisher-verification-overview.md) about this change.) For Azure AD user flows, the publisher’s domain appears only when using a [Microsoft account](microsoft-account.md) or other Azure AD tenant as the identity provider. To meet these new requirements, follow these steps:
@@ -48,5 +49,6 @@ As of November 2020, new application registrations show up as unverified in the
48
49
49
50
## Next steps
50
51
52
+
-[Microsoft account](microsoft-account.md)
51
53
-[Add Azure Active Directory B2B collaboration users](add-users-administrator.md)
52
54
-[Add self-service sign-up to an app](self-service-sign-up-user-flow.md)
0 commit comments