Skip to content

Commit 1da95f3

Browse files
authored
Merge pull request #218070 from csmulligan/csm-exid-ad-account
[EXID] Content engagement update for azure-ad-account (ADO-2161200)
2 parents f4ece7b + 243e50e commit 1da95f3

File tree

4 files changed

+8
-6
lines changed

4 files changed

+8
-6
lines changed

articles/active-directory/external-identities/azure-ad-account.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,36 +7,37 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: how-to
10-
ms.date: 10/06/2022
10+
ms.date: 11/11/2022
1111

1212
ms.author: mimart
1313
author: msmimart
1414
manager: celestedg
1515
ms.collection: M365-identity-device-management
1616
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.
1718
---
1819

1920
# Add Azure Active Directory (Azure AD) as an identity provider for External Identities
2021

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.
2223

2324
## Guest sign-in using Azure Active Directory accounts
2425

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).
2627

27-
![Azure AD account in the identity providers list](media/azure-ad-account/azure-ad-account-identity-provider.png)
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":::
2829

2930
### Azure AD account in the invitation flow
3031

3132
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.
3233

33-
![Invite using a Azure AD account](media/azure-ad-account/azure-ad-account-invite.png)
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":::
3435

3536
### Azure AD account in self-service sign-up user flows
3637

3738
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.
3839

39-
![Azure AD account in a self-service sign-up user flow](media/azure-ad-account/azure-ad-account-user-flow.png)
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":::
4041

4142
## Verifying the application's publisher domain
4243
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
4849

4950
## Next steps
5051

52+
- [Microsoft account](microsoft-account.md)
5153
- [Add Azure Active Directory B2B collaboration users](add-users-administrator.md)
5254
- [Add self-service sign-up to an app](self-service-sign-up-user-flow.md)
101 KB
Loading
73.8 KB
Loading
93.6 KB
Loading

0 commit comments

Comments
 (0)