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
With guest users, you have auditing capabilities similar to with member users.
21
21
22
22
## Access reviews
23
-
You can use access reviews to periodically verify whether guest users still need access to your resources. The **Access reviews** feature is available in **Azure Active Directory** under **Organizational Relationships** > **Access reviews** (or **External Identities** > **Access reviews** ). You can also search for "access reviews" from **All services** in the Azure portal. To learn how to use access reviews, see [Manage guest access with Azure AD access reviews](../governance/manage-guest-access-with-access-reviews.md).
23
+
You can use access reviews to periodically verify whether guest users still need access to your resources. The **Access reviews** feature is available in **Azure Active Directory** under **External Identities** > **Access reviews**. You can also search for "access reviews" from **All services** in the Azure portal. To learn how to use access reviews, see [Manage guest access with Azure AD access reviews](../governance/manage-guest-access-with-access-reviews.md).
title: Compare B2B collaboration and B2C - Azure Active Directory | Microsoft Docs
4
-
description: What is the difference between Azure Active Directory B2B collaboration and Azure AD B2C?
3
+
title: Compare External Identities - Azure Active Directory | Microsoft Docs
4
+
description: Azure AD External Identities allow people outside your organization to access your apps and resources using their own identity. Compare solutions for External Identities, including Azure Active Directory B2B collaboration and Azure AD B2C.
5
5
6
6
services: active-directory
7
7
ms.service: active-directory
8
8
ms.subservice: B2B
9
9
ms.topic: overview
10
-
ms.date: 07/22/2019
10
+
ms.date: 05/19/2020
11
11
12
12
ms.author: mimart
13
13
author: msmimart
@@ -17,31 +17,37 @@ ms.reviewer: elisolMS
17
17
ms.collection: M365-identity-device-management
18
18
---
19
19
20
-
# Compare B2B collaboration and B2C in Azure Active Directory
20
+
# Compare solutions for External Identities in Azure Active Directory
21
21
22
-
Both Azure Active Directory (Azure AD) B2B collaboration and Azure AD B2C allow you to work with external users in Azure AD. But how do they compare?
22
+
With External Identities in Azure AD, you can allow people outside your organization to access your apps and resources, while letting them sign in using whatever identity they prefer. Your partners, distributors, suppliers, vendors, and other guest users can "bring their own identities." Whether they're part of Azure AD or another IT-managed system, or have an unmanaged social identity like Google or Facebook, they can use their own credentials to sign in. The identity provider manages the external user’s identity, and you manage access to your apps with Azure AD to keep your resources protected.
23
23
24
-
**Azure AD B2B** is for businesses that want to securely share files and resources with external users so they can collaborate. An Azure admin sets up B2B in the Azure portal, and Azure AD takes care of federation between your business and your external partner. Users sign in to the shared resources using a simple invitation and redemption process with their work or school account, or any email account.
25
-
26
-
**Azure AD B2C** is primarily for businesses and developers that create customer-facing apps. With Azure AD B2C, developers can use Azure AD as the full-featured identity system for their application, while letting customers sign in with an identity they already have established (like Facebook or Gmail).
24
+
## External Identities scenarios
27
25
28
-
The table below gives a detailed comparison.
26
+
Azure AD External Identities focuses less on a user's relationship to your organization and more on the way an individual wants to sign in to your apps and resources. Within this framework, Azure AD supports a variety of scenarios from business-to-business (B2B) collaboration to app development for customers and consumers (business-to-consumer, or B2C).
29
27
28
+
-**Share apps with external users (B2B collaboration)**. Invite external users into your own tenant as "guest" users that you can assign permissions to (for authorization) while allowing them to use their existing credentials (for authentication). Users sign in to the shared resources using a simple invitation and redemption process with their work account, school account, or any email account. And now with the availability of Self-service sign-up user flows (Preview), you can also provide a sign-in experience for your external users through the application you want to share. You can configure user flow settings to control how the user signs up for the application and that allows them to use their work account, school account, or any social identity (like Google or Facebook) they want to use. For more information, see the [Azure AD B2B documentation](index.yml).
30
29
31
-
B2B collaboration capabilities | Azure AD B2C stand-alone offering
32
-
-------- | --------
33
-
Intended for: Organizations that want to be able to authenticate users from a partner organization, regardless of identity provider. | Intended for: Inviting customers of your mobile and web apps, whether individuals, institutional or organizational customers into your Azure AD.
34
-
Identities supported: Employees with work or school accounts, partners with work or school accounts, or any email address. Soon to support direct federation. | Identities supported: Consumer users with local application accounts (any email address or user name) or any supported social identity with direct federation.
35
-
External users are managed in the same directory as employees, but annotated specially. They can be managed the same way as employees, they can be added to the same groups, and so on | External users are managed in the application directory. They're managed separately from the organization’s employee and partner directory (if any).
36
-
Single sign-on (SSO) to all Azure AD-connected apps is supported. For example, you can provide access to Office 365 or on-premises apps, and to other SaaS apps such as Salesforce or Workday. | SSO to customer owned apps within the Azure AD B2C tenants is supported. SSO to Office 365 or to other Microsoft SaaS apps is not supported.
37
-
Partner lifecycle: Managed by the host/inviting organization. | Customer lifecycle: Self-serve or managed by the application.
38
-
Security policy and compliance: Managed by the host/inviting organization (for example, with [Conditional Access policies](https://docs.microsoft.com/azure/active-directory/b2b/conditional-access)). | Security policy and compliance: Managed by the application.
39
-
Branding: Host/inviting organization’s brand is used. | Branding: Managed by application. Typically tends to be product branded, with the organization fading into the background.
40
-
More info: [Blog post](https://blogs.technet.microsoft.com/enterprisemobility/2017/02/01/azure-ad-b2b-new-updates-make-cross-business-collab-easy/), [Documentation](what-is-b2b.md) | More info: [Product page](https://azure.microsoft.com/services/active-directory-b2c/), [Documentation](https://docs.microsoft.com/azure/active-directory-b2c/)
30
+
-**Develop apps intended for other Azure AD tenants (single-tenant or multi-tenant)**. When developing applications for Azure AD, you can target users from a single organization (single tenant), or users from any organization that already has an Azure AD tenant (called multi-tenant applications). These multi-tenant applications are registered once by yourself in your own Azure AD, but can then be used by any Azure AD user from any organization without any additional work on your part.
41
31
32
+
-**Develop white-labeled apps for consumers and customers (Azure AD B2C)**. If you're a business or developer creating customer-facing apps, you can scale to consumers, customers, or citizens by using an Azure AD B2C. Developers can use Azure AD as the full-featured identity system for their application, while letting customers sign in with an identity they already have established (like Facebook or Gmail). With Azure AD B2C, you can completely customize and control how customers sign up, sign in, and manage their profiles when using your applications. For more information, see the [Azure AD B2C documentation](https://docs.microsoft.com/azure/active-directory-b2c/).
33
+
34
+
The table below gives a detailed comparison of the various scenarios you can enable with Azure AD External Identities.
35
+
36
+
| Multi-tenant applications | External user collaboration (B2B) | Apps for consumers or customers (B2C) |
37
+
| ---- | --- | --- |
38
+
| Primary scenario: Enterprise Software-as-a-Service (SaaS) | Primary scenario: Collaboration using Microsoft applications (Office 365, Teams, ...) or your own collaboration software. | Primary scenario: Transactional applications using custom developed applications. |
39
+
| Intended for: Organizations that want to provide software to many enterprise customers. | Intended for: Organizations that want to be able to authenticate users from a partner organization, regardless of identity provider. | Intended for: Inviting customers of your mobile and web apps, whether individuals, institutional or organizational customers into an Azure AD directory separate from your own organization's directory. |
40
+
| Identities supported: Employees with Azure AD accounts. | Identities supported: Employees with work or school accounts, partners with work or school accounts, or any email address. Soon to support direct federation. | Identities supported: Consumer users with local application accounts (any email address or user name) or any supported social identity with direct federation. |
41
+
| External users are managed in their own directory, isolated from the directory where the application was registered. | External users are managed in the same directory as employees, but annotated specially. They can be managed the same way as employees, they can be added to the same groups, and so on. | External users are managed in the application directory. They're managed separately from the organization's employee and partner directory (if any). |
42
+
| Single sign-on: SSO to all Azure AD-connected apps is supported. | Single sign-on: SSO to all Azure AD-connected apps is supported. For example, you can provide access to Office 365 or on-premises apps, and to other SaaS apps such as Salesforce or Workday. | Single sign-on: SSO to customer owned apps within the Azure AD B2C tenants is supported. SSO to Office 365 or to other Microsoft SaaS apps is not supported. |
43
+
| Customer lifecycle: Managed by the user's home organization. | Partner lifecycle: Managed by the host/inviting organization. | Customer lifecycle: Self-serve or managed by the application. |
44
+
| Security policy and compliance: Managed by the host/inviting organization (for example, with [Conditional Access policies](https://docs.microsoft.com/azure/active-directory/b2b/conditional-access)). | Security policy and compliance: Managed by the host/inviting organization (for example, with [Conditional Access policies](https://docs.microsoft.com/azure/active-directory/b2b/conditional-access)). | Security policy and compliance: Managed by the application. |
45
+
| Branding: Host/inviting organization's brand is used. | Branding: Host/inviting organization's brand is used. | Branding: Managed by application. Typically tends to be product branded, with the organization fading into the background. |
46
+
| More info: [Manage identity in multi-tenant applications](https://docs.microsoft.com/azure/architecture/multitenant-identity/), [How-to Guide](https://docs.microsoft.com/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant)| More info: [Blog post](https://blogs.technet.microsoft.com/enterprisemobility/2017/02/01/azure-ad-b2b-new-updates-make-cross-business-collab-easy/), [Documentation](what-is-b2b.md)| More info: [Product page](https://azure.microsoft.com/services/active-directory-b2c/), [Documentation](https://docs.microsoft.com/azure/active-directory-b2c/)|
47
+
48
+
Secure and manage customers and partners beyond your organizational boundaries with Azure AD External Identities.
42
49
43
50
### Next steps
44
51
45
52
-[What is Azure AD B2B collaboration?](what-is-b2b.md)
46
-
-[B2B collaboration user properties](user-properties.md)
47
-
53
+
-[About Azure AD B2C](https://docs.microsoft.com/azure/active-directory-b2c/overview)
title: Add Facebook as an identity provider - Azure AD
4
+
description: Federate with Facebook to enable external users (guests) to sign in to your Azure AD apps with their own Facebook accounts.
5
+
6
+
services: active-directory
7
+
ms.service: active-directory
8
+
ms.subservice: B2B
9
+
ms.topic: conceptual
10
+
ms.date: 05/19/2020
11
+
12
+
ms.author: mimart
13
+
author: msmimart
14
+
manager: celestedg
15
+
ms.reviewer: mal
16
+
ms.custom: "it-pro, seo-update-azuread-jan"
17
+
ms.collection: M365-identity-device-management
18
+
---
19
+
20
+
# Add Facebook as an identity provider for External Identities
21
+
22
+
You can add Facebook to your self-service sign-up user flows (Preview) 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.
23
+
24
+
## Create an app in the Facebook developers console
25
+
26
+
To use a Facebook account as an [identity provider](identity-providers.md), you need to create an application in the Facebook developers console. If you don't already have a Facebook account, you can sign up at [https://www.facebook.com/](https://www.facebook.com).
27
+
28
+
> [!NOTE]
29
+
> Use the following URLs in the steps 9 and 16 below.
30
+
> - For **Site URL** enter `https://login.microsoftonline.com`.
31
+
> - For **Valid OAuth redirect URIs**, enter `https://login.microsoftonline.com/te/<tenant-id>/oauth2/authresp`. You can find your `<tenant-ID>` in the Azure Active Directory Overview blade.
32
+
33
+
34
+
1. Sign in to [Facebook for developers](https://developers.facebook.com/) with your Facebook account credentials.
35
+
2. If you have not already done so, you need to register as a Facebook developer. To do this, select **Get Started** on the upper-right corner of the page, accept Facebook's policies, and complete the registration steps.
36
+
3. Select **My Apps** and then **Create App**.
37
+
4. Enter a **Display Name** and a valid **Contact Email**.
38
+
5. Select **Create App ID**. This may require you to accept Facebook platform policies and complete an online security check.
39
+
6. Select **Settings** > **Basic**.
40
+
7. Choose a **Category**, for example Business and Pages. This value is required by Facebook, but not used for Azure AD.
41
+
8. At the bottom of the page, select **Add Platform**, and then select **Website**.
42
+
9. In **Site URL**, enter the appropriate URL (noted above).
43
+
10. In **Privacy Policy URL**, enter the URL for the page where you maintain privacy information for your application, for example `http://www.contoso.com`.
44
+
11. Select **Save Changes**.
45
+
12. At the top of the page, copy the value of **App ID**.
46
+
13. Select **Show** and copy the value of **App Secret**. You use both of them to configure Facebook as an identity provider in your tenant. **App Secret** is an important security credential.
47
+
14. Select the plus sign next to **PRODUCTS**, and then select **Set up** under **Facebook Login**.
48
+
15. Under **Facebook Login**, select **Settings**.
49
+
16. In **Valid OAuth redirect URIs**, enter the appropriate URL (noted above).
50
+
17. Select **Save Changes** at the bottom of the page.
51
+
18. To make your Facebook application available to Azure AD, select the Status selector at the top right of the page and turn it **On** to make the Application public, and then select **Switch Mode**. At this point the Status should change from **Development** to **Live**.
52
+
53
+
## Configure a Facebook account as an identity provider
54
+
55
+
1. Sign in to the [Azure portal](https://portal.azure.com) as the global administrator of your Azure AD tenant.
56
+
2. Under **Azure services**, select **Azure Active Directory**.
57
+
3. In the left menu, select **External Identities**.
58
+
4. Select **All identity providers**, then select **Facebook**.
59
+
5. For the **Client ID**, enter the **App ID** of the Facebook application that you created earlier.
60
+
6. For the **Client secret**, enter the **App Secret** that you recorded.
61
+
62
+
63
+
64
+
7. Select **Save**.
65
+
66
+
## Next steps
67
+
68
+
-[Invite external users for collaboration](add-users-administrator.md)
69
+
-[Add self-service sign-up to an app](self-service-sign-up-user-flow.md)
0 commit comments