Skip to content

Commit d551ddf

Browse files
authored
Merge pull request #46040 from MicrosoftDocs/master
7/6 PM Publish
2 parents 11321f2 + 2f4fba2 commit d551ddf

File tree

329 files changed

+3897
-5270
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

329 files changed

+3897
-5270
lines changed

.openpublishing.redirection.json

Lines changed: 82 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11504,6 +11504,11 @@
1150411504
"redirect_url": "/azure/vpn-gateway/vpn-gateway-howto-vnet-vnet-portal-classic",
1150511505
"redirect_document_id": false
1150611506
},
11507+
{
11508+
"source_path": "articles/virtual-network/virtual-networks-create-nsg-arm-pportal.md",
11509+
"redirect_url": "/azure/virtual-network/tutorial-filter-network-traffic",
11510+
"redirect_document_id": true
11511+
},
1150711512
{
1150811513
"source_path": "articles/virtual-network/virtual-network-routes-troubleshoot-portal.md",
1150911514
"redirect_url": "/azure/virtual-network/diagnose-network-routing-problem",
@@ -24395,6 +24400,81 @@
2439524400
"redirect_url": "/azure/security/blueprints/fedramp-iaaswa-overview#compliance-documentation",
2439624401
"redirect_document_id": false
2439724402
},
24403+
{
24404+
"source_path": "articles/security/blueprints/financial-services-regulated-workloads.md",
24405+
"redirect_url": "/azure/security/blueprints/ffiec-paaswa-overview",
24406+
"redirect_document_id": true
24407+
},
24408+
{
24409+
"source_path": "articles/security/blueprints/payment-processing-blueprint.md",
24410+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview",
24411+
"redirect_document_id": true
24412+
},
24413+
{
24414+
"source_path": "articles/security/blueprints/pci-dss-requirements-overview.md",
24415+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24416+
"redirect_document_id": true
24417+
},
24418+
{
24419+
"source_path": "articles/security/blueprints/pci-dss-requirement-1-firewall.md",
24420+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24421+
"redirect_document_id": true
24422+
},
24423+
{
24424+
"source_path": "articles/security/blueprints/pci-dss-requirement-2-password.md",
24425+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24426+
"redirect_document_id": true
24427+
},
24428+
{
24429+
"source_path": "articles/security/blueprints/pci-dss-requirement-3-chd.md",
24430+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24431+
"redirect_document_id": true
24432+
},
24433+
{
24434+
"source_path": "articles/security/blueprints/pci-dss-requirement-4-encryption.md",
24435+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24436+
"redirect_document_id": true
24437+
},
24438+
{
24439+
"source_path": "articles/security/blueprints/pci-dss-requirement-5-malware.md",
24440+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24441+
"redirect_document_id": true
24442+
},
24443+
{
24444+
"source_path": "articles/security/blueprints/pci-dss-requirement-6-secure-system.md",
24445+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24446+
"redirect_document_id": true
24447+
},
24448+
{
24449+
"source_path": "articles/security/blueprints/pci-dss-requirement-7-access.md",
24450+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24451+
"redirect_document_id": true
24452+
},
24453+
{
24454+
"source_path": "articles/security/blueprints/pci-dss-requirement-8-identity.md",
24455+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24456+
"redirect_document_id": true
24457+
},
24458+
{
24459+
"source_path": "articles/security/blueprints/pci-dss-requirement-9-physical-access.md",
24460+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24461+
"redirect_document_id": true
24462+
},
24463+
{
24464+
"source_path": "articles/security/blueprints/pci-dss-requirement-10-monitoring.md",
24465+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24466+
"redirect_document_id": true
24467+
},
24468+
{
24469+
"source_path": "articles/security/blueprints/pci-dss-requirement-11-testing.md",
24470+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24471+
"redirect_document_id": true
24472+
},
24473+
{
24474+
"source_path": "articles/security/blueprints/pci-dss-requirement-12-policy.md",
24475+
"redirect_url": "/azure/security/blueprints/pcidss-paaswa-overview#compliance-documentation",
24476+
"redirect_document_id": true
24477+
},
2439824478
{
2439924479
"source_path": "articles/active-directory/active-directory-cloudappdiscovery-registry-settings-for-proxy-services.md",
2440024480
"redirect_url": "/azure/active-directory/cloudappdiscovery-get-started",
@@ -25945,7 +26025,7 @@
2594526025
"redirect_url": "/azure/cognitive-services/LUIS/luis-how-to-cortana-prebuilt-app",
2594626026
"redirect_document_id": true
2594726027
},
25948-
{
26028+
{
2594926029
"source_path": "articles/cloud-shell/features-powershell.md",
2595026030
"redirect_url": "/azure/cloud-shell/features",
2595126031
"redirect_document_id": false
@@ -25961,4 +26041,4 @@
2596126041
"redirect_document_id": true
2596226042
}
2596326043
]
25964-
}
26044+
}
Lines changed: 39 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -1,63 +1,54 @@
11
---
2-
title: Facebook configuration in Azure Active Directory B2C | Microsoft Docs
3-
description: Provide sign-up and sign-in to consumers with Facebook accounts in your applications that are secured by Azure Active Directory B2C.
2+
title: Set up sign-up and sign-in with a Facebook account using Azure Active Directory B2C | Microsoft Docs
3+
description: Provide sign-up and sign-in to customers with Facebook accounts in your applications using Azure Active Directory B2C.
44
services: active-directory-b2c
55
author: davidmu1
66
manager: mtillman
77

88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 8/7/2017
11+
ms.date: 07/06/2018
1212
ms.author: davidmu
1313
ms.component: B2C
1414
---
1515

16-
# Azure Active Directory B2C: Provide sign-up and sign-in to consumers with Facebook accounts
16+
# Set up sign-up and sign-in with a Facebook account using Azure Active Directory B2C
17+
1718
## Create a Facebook application
18-
To use Facebook as an identity provider in Azure Active Directory (Azure AD) B2C, you need to create a Facebook application and supply it with the right parameters. You need a Facebook account to do this. If you don’t have one, you can get it at [https://www.facebook.com/](https://www.facebook.com/).
1919

20-
1. Go to the [Facebook for developers](https://developers.facebook.com/) website and sign in with your Facebook account credentials.
21-
2. If you have not already done so, you need to register as a Facebook developer. To do this, click **Register** (on the upper-right corner of the page), accept Facebook's policies, and complete the registration steps.
22-
3. Click **My Apps** and then click **Add a New App**.
23-
4. In the form, provide a **Display Name** and a valid **Contact Email**.
20+
To use a Facebook account as an identity provider 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 Facebook account, you can get it at [https://www.facebook.com/](https://www.facebook.com/).
21+
22+
1. Sign in to [Facebook for developers](https://developers.facebook.com/) with your Facebook account credentials.
23+
2. If you have not already done so, you need to register as a Facebook developer. To do this, select **Register** on the upper-right corner of the page, accept Facebook's policies, and complete the registration steps.
24+
3. Select **My Apps** and then click **Add New App**.
25+
4. Enter a **Display Name** and a valid **Contact Email**.
2426
5. Click **Create App ID**. This may require you to accept Facebook platform policies and complete an online security check.
25-
6. In the left column, click **Settings** and then select **Basic** if not selected already.
26-
7. Select a **Category**.
27-
8. Click **+ Add Platform** and select **Website**.
28-
29-
![Facebook - Settings](./media/active-directory-b2c-setup-fb-app/fb-settings.png)
30-
31-
![Facebook - Settings - Website](./media/active-directory-b2c-setup-fb-app/fb-website.png)
32-
9. Enter `https://login.microsoftonline.com/` in the **Site URL** field and then click **Save Changes** at the bottom of the page.
33-
34-
![Facebook - Site URL](./media/active-directory-b2c-setup-fb-app/fb-site-url.png)
35-
36-
10. Copy the value of **App ID**. Click **Show** and copy the value of **App Secret**. You will need both of them to configure Facebook as an identity provider in your tenant. **App Secret** is an important security credential.
37-
38-
![Facebook - App ID & App Secret](./media/active-directory-b2c-setup-fb-app/fb-app-id-app-secret.png)
39-
11. Click **+ Add Product** on the left navigation and then the **Set Up** button for **Facebook Login**.
40-
41-
![Facebook - Facebook Login](./media/active-directory-b2c-setup-fb-app/fb-login.png)
42-
12. Click **Settings** on the right nav under **Facebook Login**
43-
44-
![Facebook - Facebook Login settings](./media/active-directory-b2c-setup-fb-app/fb-login-settings.png)
45-
13. Enter `https://login.microsoftonline.com/te/{tenant}/oauth2/authresp` in the **Valid OAuth redirect URIs** field in the **Client OAuth Settings** section. Replace **{tenant}** with your tenant's name (for example, contosob2c.onmicrosoft.com). Click **Save Changes** at the bottom of the page.
46-
47-
![Facebook - OAuth Redirect URI](./media/active-directory-b2c-setup-fb-app/fb-oauth-redirect-uri.png)
48-
14. To make your Facebook application usable by Azure AD B2C, you need to make it publicly available. You can do this by clicking **App Review** on the left navigation and by turning the switch at the top of the page to **YES** and clicking **Confirm**.
49-
50-
![Facebook - App public](./media/active-directory-b2c-setup-fb-app/fb-app-public.png)
51-
52-
## Configure Facebook as an identity provider in your tenant
53-
1. Follow these steps to [navigate to the B2C features blade](active-directory-b2c-app-registration.md#navigate-to-b2c-settings) on the Azure portal.
54-
2. On the B2C features blade, click **Identity providers**.
55-
3. Click **+Add** at the top of the blade.
56-
4. Provide a friendly **Name** for the identity provider configuration. For example, enter "Facebook".
57-
5. Click **Identity provider type**, select **Facebook**, and click **OK**.
58-
6. Click **Set up this identity provider** and enter the app ID and app secret (of the Facebook application that you created earlier) in the **Client ID** and **Client secret** fields respectively.
59-
7. Click **OK**, and then click **Create** to save your Facebook configuration.
60-
61-
> [!NOTE]
62-
> Adding an **Identity provider** to your tenant does not modify your existing policies. Remember to update your policies by including the identity provider you just created.
63-
>
27+
6. Select **Settings** > **Basic**.
28+
7. At the bottom of the page, select **Add Platform**, and then select **Website**.
29+
8. Enter `https://login.microsoftonline.com/` in **Site URL**. Enter a URL for the **Privacy Policy URL**, for example `http://www.contoso.com`.
30+
9. Select **Save Changes**.
31+
11. At the top of the page, copy the value of **App ID**.
32+
12. Click **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.
33+
13. Select **Products**, and then select **Set up** under **Facebook Login**.
34+
14. Select **Settings** under **Facebook Login**.
35+
15. Enter `https://login.microsoftonline.com/te/{tenant}/oauth2/authresp` in **Valid OAuth redirect URIs** . Replace **{tenant}** with your tenant's name (for example, contosob2c.onmicrosoft.com). Click **Save Changes** at the bottom of the page.
36+
16. To make your Facebook application available to Azure AD B2C, select **App Review**, set **Make My Application public?** to **YES**, choose a category, for example `Business and Pages` and then click **Confirm**.
37+
38+
## Configure a Facebook account as an identity provider
39+
40+
1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
41+
2. Make sure you're using the directory that contains your Azure AD B2C tenant by switching to it in the top-right corner of the Azure portal. Select your subscription information, and then select **Switch Directory**.
42+
43+
![Switch to your Azure AD B2C tenant](./media/active-directory-b2c-setup-fb-app/switch-directories.png)
44+
45+
Choose the directory that contains your tenant.
46+
47+
![Select directory](./media/active-directory-b2c-setup-fb-app/select-directory.png)
48+
49+
3. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
50+
4. Select **Identity providers**, and then select **Add**.
51+
5. Enter a **Name**. For example, enter *Facebook*.
52+
6. Select **Identity provider type**, select **Facebook**, and click **OK**.
53+
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).
54+
8. Click **OK** and then click **Create** to save your Facebook configuration.

articles/active-directory-b2c/active-directory-b2c-setup-msa-app.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -30,13 +30,18 @@ To use a Microsoft account as an identity provider in Azure Active Directory (Az
3030
## Configure a Microsoft account as an identity provider
3131

3232
1. Sign in to the [Azure portal](https://portal.azure.com/) as the global administrator of your Azure AD B2C tenant.
33+
2. Make sure you're using the directory that contains your Azure AD B2C tenant by switching to it in the top-right corner of the Azure portal. Select your subscription information, and then select **Switch Directory**.
3334

34-
[!INCLUDE [active-directory-b2c-switch-b2c-tenant](../../includes/active-directory-b2c-switch-b2c-tenant.md)]
35+
![Switch to your Azure AD B2C tenant](./media/active-directory-b2c-setup-msa-app/switch-directories.png)
3536

36-
2. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
37-
2. Select **Identity providers**, and then select **Add**.
38-
4. Provide a **Name**. For example, enter *MSA*.
39-
5. Select **Identity provider type**, select **Microsoft Account**, and click **OK**.
40-
6. Select **Set up this identity provider** and enter the Application Id that you recorded earlier as the **Client ID** and enter the password that you recorded as the **Client secret** of the Microsoft account application that you created earlier.
41-
7. Click **OK** and then click **Create** to save your Microsoft account configuration.
37+
Choose the directory that contains your tenant.
38+
39+
![Select directory](./media/active-directory-b2c-setup-msa-app/select-directory.png)
40+
41+
3. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
42+
4. Select **Identity providers**, and then select **Add**.
43+
5. Provide a **Name**. For example, enter *MSA*.
44+
6. Select **Identity provider type**, select **Microsoft Account**, and click **OK**.
45+
7. Select **Set up this identity provider** and enter the Application Id that you recorded earlier as the **Client ID** and enter the password that you recorded as the **Client secret** of the Microsoft account application that you created earlier.
46+
8. Click **OK** and then click **Create** to save your Microsoft account configuration.
4247

Binary file not shown.

0 commit comments

Comments
 (0)