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-b2c/active-directory-b2c-faqs.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Azure AD B2C can't be used to authenticate users for Microsoft Office 365. Azure
33
33
34
34
In an Azure AD tenant, users that belong to the tenant sign-in with an email address of the form `<xyz>@<tenant domain>`. The `<tenant domain>` is one of the verified domains in the tenant or the initial `<...>.onmicrosoft.com` domain. This type of account is a work or school account.
35
35
36
-
In an Azure AD B2C tenant, most apps want the user to sign-in with any arbitrary email address (for example, [email protected], [email protected], [email protected], or [email protected]). This type of account is a local account. We also support arbitrary user names as local accounts (for example, joe, bob, sarah, or jim). You can choose one of these two local account types when configuring identity providers for Azure AD B2C in the Azure portal. In your Azure AD B2C tenant, select**Identity providers**, select **Local account**, and then select **Username**.
36
+
In an Azure AD B2C tenant, most apps want the user to sign-in with any arbitrary email address (for example, [email protected], [email protected], [email protected], or [email protected]). This type of account is a local account. We also support arbitrary user names as local accounts (for example, joe, bob, sarah, or jim). You can choose one of these two local account types when configuring identity providers for Azure AD B2C in the Azure portal. In your Azure AD B2C tenant, click**Identity providers**and then select **Username** under Local accounts.
37
37
38
38
User accounts for applications must always be created through a sign-up user flow, sign-up or sign-in user flow, or by using the Azure AD Graph API. User accounts created in the Azure portal are only used for administering the tenant.
title: Set up sign-up and sign-in with an Amazon account - Azure Active Directory B2C
2
+
title: Set up sign-up and sign-in with an Amazon account - Azure Active Directory B2C | Microsoft Docs
3
3
description: Provide sign-up and sign-in to customers with Amazon accounts in your applications using Azure Active Directory B2C.
4
4
services: active-directory-b2c
5
5
author: mmacy
@@ -8,7 +8,7 @@ manager: celestedg
8
8
ms.service: active-directory
9
9
ms.workload: identity
10
10
ms.topic: conceptual
11
-
ms.date: 08/05/2019
11
+
ms.date: 09/21/2018
12
12
ms.author: marsma
13
13
ms.subservice: B2C
14
14
---
@@ -20,20 +20,21 @@ ms.subservice: B2C
20
20
To use an Amazon account as an [identity provider](active-directory-b2c-reference-oauth-code.md) in Azure Active Directory (Azure AD) B2C, you need to create an application in your tenant that represents it. If you don’t already have an Amazon account you can get it at [https://www.amazon.com/](https://www.amazon.com/).
21
21
22
22
1. Sign in to the [Amazon Developer Center](https://login.amazon.com/) with your Amazon account credentials.
23
-
1. If you have not already done so, click **Sign Up**, follow the developer registration steps, and accept the policy.
24
-
1. Select **Register new application**.
25
-
1. Enter a **Name**, **Description**, and **Privacy Notice URL**, and then click **Save**. The privacy notice is a page that you manage that provides privacy information to users.
26
-
1. In the **Web Settings** section, copy the values of **Client ID**. Select **Show Secret** to get the client secret and then copy it. You need both of them to configure an Amazon account as an identity provider in your tenant. **Client Secret** is an important security credential.
27
-
1. In the **Web Settings** section, select **Edit**, and then enter `https://your-tenant-name.b2clogin.com` in **Allowed JavaScript Origins** and `https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com/oauth2/authresp` in **Allowed Return URLs**. Replace `your-tenant-name` with the name of your tenant. You need to use all lowercase letters when entering your tenant name even if the tenant is defined with uppercase letters in Azure AD B2C.
28
-
1. Click **Save**.
23
+
2. If you have not already done so, click **Sign Up**, follow the developer registration steps, and accept the policy.
24
+
3. Select **Register new application**.
25
+
4. Enter a **Name**, **Description**, and **Privacy Notice URL**, and then click **Save**. The privacy notice is a page that you manage that provides privacy information to users.
26
+
5. In the **Web Settings** section, copy the values of **Client ID**. Select **Show Secret** to get the client secret and then copy it. You need both of them to configure an Amazon account as an identity provider in your tenant. **Client Secret** is an important security credential.
27
+
6. In the **Web Settings** section, select **Edit**, and then enter `https://your-tenant-name.b2clogin.com` in **Allowed JavaScript Origins** and `https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com/oauth2/authresp` in **Allowed Return URLs**. Replace `your-tenant-name` with the name of your tenant. You need to use all lowercase letters when entering your tenant name even if the tenant is defined with uppercase letters in Azure AD B2C.
28
+
7. Click **Save**.
29
29
30
30
## Configure an Amazon account as an identity provider
31
31
32
32
1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
33
-
1. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory + subscription filter** in the top menu and choosing the directory that contains your tenant.
34
-
1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
35
-
1. Select **Identity providers**, then select **Amazon**.
36
-
1. Enter a **Name**. For example, *Amazon*.
37
-
1. For the **Client ID**, enter the Client ID of the Amazon application that you created earlier.
38
-
1. For the **Client secret**, enter the Client Secret that you recorded.
39
-
1. Select **Save**.
33
+
2. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
34
+
3. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
35
+
4. Select **Identity providers**, and then select **Add**.
36
+
5. Enter a **Name**. For example, enter *Amazon*.
37
+
6. Select **Identity provider type**, select **Amazon**, and click **OK**.
38
+
7. Select **Set up this identity provider** and enter the Client ID that you recorded earlier as the **Client ID** and enter the Client Secret that you recorded as the **Client secret** of the Amazon application that you created earlier.
39
+
8. Click **OK** and then click **Create** to save your Amazon configuration.
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/active-directory-b2c-setup-fb-app.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Set up sign-up and sign-in with a Facebook account - Azure Active Directory B2C
2
+
title: Set up sign-up and sign-in with a Facebook account - Azure Active Directory B2C | Microsoft Docs
3
3
description: Provide sign-up and sign-in to customers with Facebook accounts in your applications using Azure Active Directory B2C.
4
4
services: active-directory-b2c
5
5
author: mmacy
@@ -8,7 +8,7 @@ manager: celestedg
8
8
ms.service: active-directory
9
9
ms.workload: identity
10
10
ms.topic: conceptual
11
-
ms.date: 08/05/2019
11
+
ms.date: 06/05/2019
12
12
ms.author: marsma
13
13
ms.subservice: B2C
14
14
---
@@ -39,10 +39,10 @@ To use a Facebook account as an [identity provider](active-directory-b2c-referen
39
39
## Configure a Facebook account as an identity provider
40
40
41
41
1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
42
-
1. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
43
-
1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
44
-
1. Select **Identity providers**, then select **Facebook**.
45
-
1. Enter a **Name**. For example, *Facebook*.
46
-
1. For the **Client ID**, enter the App ID of the Facebook application that you created earlier.
47
-
1. For the **Client secret**, enter the App Secret that you recorded.
48
-
1. Select**Save**.
42
+
2. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
43
+
3. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
44
+
4. Select **Identity providers**, and then select **Add**.
45
+
5. Enter a **Name**. For example, enter*Facebook*.
46
+
6. Select **Identity provider type**, select **Facebook**, and click **OK**.
47
+
7. Select **Set up this identity provider** and enter the App ID that you recorded earlier as the **Client ID** and enter the App Secret that you recorded as the **Client secret** of the Facebook application that you created earlier.
48
+
8. Click**OK** and then click **Create** to save your Facebook configuration.
title: Set up sign-up and sign-in with a GitHub account - Azure Active Directory B2C
2
+
title: Set up sign-up and sign-in with a GitHub account - Azure Active Directory B2C | Microsoft Docs
3
3
description: Provide sign-up and sign-in to customers with GitHub accounts in your applications using Azure Active Directory B2C.
4
4
services: active-directory-b2c
5
5
author: mmacy
@@ -8,17 +8,18 @@ manager: celestedg
8
8
ms.service: active-directory
9
9
ms.workload: identity
10
10
ms.topic: conceptual
11
-
ms.date: 08/05/2019
11
+
ms.date: 12/07/2018
12
12
ms.author: marsma
13
13
ms.subservice: B2C
14
14
---
15
15
16
16
# Set up sign-up and sign-in with a GitHub account using Azure Active Directory B2C
17
17
18
-
To use a GitHub account as an [identity provider](active-directory-b2c-reference-oauth-code.md) in Azure Active Directory (Azure AD) B2C, you need to create an application in your tenant that represents it. If you don’t already have a GitHub account, you can get it at [https://www.github.com/](https://www.github.com/).
18
+
> [!NOTE]
19
+
> This feature is in preview.
20
+
>
19
21
20
-
> [!IMPORTANT]
21
-
> This feature is currently in **preview**. Previews are made available to you on the condition that you agree to the [supplemental terms of use](https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms/). Some aspects of this feature may change prior to general availability (GA).
22
+
To use a GitHub account as an [identity provider](active-directory-b2c-reference-oauth-code.md) in Azure Active Directory (Azure AD) B2C, you need to create an application in your tenant that represents it. If you don’t already have a GitHub account, you can get it at [https://www.github.com/](https://www.github.com/).
22
23
23
24
## Create a GitHub OAuth application
24
25
@@ -32,10 +33,10 @@ To use a GitHub account as an [identity provider](active-directory-b2c-reference
32
33
## Configure a GitHub account as an identity provider
33
34
34
35
1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
35
-
1. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
36
-
1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
37
-
1. Select **Identity providers**, then select **GitHub (Preview)**.
38
-
1. Enter a **Name**. For example, *GitHub*.
39
-
1. For the **Client ID**, enter the Client ID of the GitHub application that you created earlier.
40
-
1. For the **Client secret**, enter the Client Secret that you recorded.
41
-
1. Select**Save**.
36
+
2. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
37
+
3. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
38
+
4. Select **Identity providers**, and then select **Add**.
39
+
5. Provide a **Name**. For example, enter*GitHub*.
7. Select **Set up this identity provider** and enter the Client Id that you recorded earlier as the **Client ID** and enter the Client Secret that you recorded as the **Client secret** of the GitHub account application that you created earlier.
42
+
8. Click**OK** and then click **Create** to save your GitHub account configuration.
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/active-directory-b2c-setup-goog-app.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,10 +31,11 @@ To use a Google account as an [identity provider](active-directory-b2c-reference
31
31
## Configure a Google account as an identity provider
32
32
33
33
1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
34
-
1. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
35
-
1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
36
-
1. Select **Identity providers**, then select **Google**.
37
-
1. Enter a **Name**. For example, *Google*.
38
-
1. For the **Client ID**, enter the Client ID of the Google application that you created earlier.
39
-
1. For the **Client secret**, enter the Client Secret that you recorded.
40
-
1. Select **Save**.
34
+
2. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
35
+
3. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
36
+
4. Select **Identity providers**, and then select **Add**.
37
+
5. Enter a **Name**. For example, enter *Google*.
38
+
6. Select **Identity provider type**, select **Google**, and click **OK**.
39
+
7. Select **Set up this identity provider** and enter the Client ID that you recorded earlier as the **Client ID** and enter the Client Secret that you recorded as the **Client secret** of the Google application that you created earlier.
40
+
8. Click **OK** and then click **Create** to save your Google configuration.
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/active-directory-b2c-setup-li-app.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Set up sign-up and sign-in with a LinkedIn account - Azure Active Directory B2C
2
+
title: Set up sign-up and sign-in with a LinkedIn account - Azure Active Directory B2C | Microsoft Docs
3
3
description: Provide sign-up and sign-in to customers with LinkedIn accounts in your applications using Azure Active Directory B2C.
4
4
services: active-directory-b2c
5
5
author: mmacy
@@ -8,7 +8,7 @@ manager: celestedg
8
8
ms.service: active-directory
9
9
ms.workload: identity
10
10
ms.topic: conceptual
11
-
ms.date: 08/05/2019
11
+
ms.date: 04/01/2019
12
12
ms.author: marsma
13
13
ms.subservice: B2C
14
14
---
@@ -29,14 +29,14 @@ To use a LinkedIn account as an [identity provider](active-directory-b2c-referen
29
29
## Configure a LinkedIn account as an identity provider
30
30
31
31
1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
32
-
1. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
33
-
1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
34
-
1. Select **Identity providers**, then select **LinkedIn**.
35
-
1. Enter a **Name**. For example, *LinkedIn*.
36
-
1. For the **Client ID**, enter the Client ID of the LinkedIn application that you created earlier.
37
-
1. For the **Client secret**, enter the Client Secret that you recorded.
38
-
1. Select**Save**.
32
+
2. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
33
+
3. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
34
+
4. Select **Identity providers**, and then select **Add**.
35
+
5. Provide a **Name**. For example, enter*LinkedIn*.
36
+
6. Select **Identity provider type**, select **LinkedIn**, and click **OK**.
37
+
7. Select **Set up this identity provider** and enter the Client Id that you recorded earlier as the **Client ID** and enter the Client Secret that you recorded as the **Client secret** of the LinkedIn account application that you created earlier.
38
+
8. Click**OK** and then click **Create** to save your LinkedIn account configuration.
39
39
40
40
## Migration from v1.0 to v2.0
41
41
42
-
LinkedIn recently [updated their APIs from v1.0 to v2.0](https://engineering.linkedin.com/blog/2018/12/developer-program-updates). As part of the migration, Azure AD B2C is only able to obtain the full name of the LinkedIn user during the sign-up. If an email address is one of the attributes that is collected during sign-up, the user must manually enter the email address and validate it.
42
+
LinkedIn recently [updated their API's from v1.0 to v2.0](https://engineering.linkedin.com/blog/2018/12/developer-program-updates). As part of the migration, Azure AD B2C is only able to obtain the full name of the LinkedIn user during the sign-up. If an email address is one of the attributes that is collected during sign-up, the user must manually enter the email address and validate it.
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/active-directory-b2c-setup-msa-app.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,8 +40,8 @@ To use a Microsoft account as an [identity provider](active-directory-b2c-refere
40
40
1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
41
41
1. Make sure you're using the directory that contains your Azure AD B2C tenant by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains your tenant.
42
42
1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
43
-
1. Select **Identity providers**, then select **Microsoft Account**.
44
-
1.Enter a **Name**. For example, *MSA*.
45
-
1.For the **Client ID**, enter the Application (client) ID of the application that you created earlier.
46
-
1.For the **Client secret**, enter the client secret that you recorded.
47
-
1.Select**Save**.
43
+
1. Select **Identity providers**, and then select **Add**.
44
+
1.Provide a **Name**. For example, enter*MSA*.
45
+
1.Select **Identity provider type**, select **Microsoft Account**, and click **OK**.
46
+
1.Select **Set up this identity provider** and enter the Application (client) ID that you recorded earlier in the **Client ID** text box, and enter the client secret that you recorded in the **Client secret** text box.
47
+
1.Click**OK** and then click **Create** to save your Microsoft account configuration.
0 commit comments