Skip to content

Commit 45e380c

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into updateFileLin
2 parents 7fc976a + b3b6d7c commit 45e380c

File tree

660 files changed

+10303
-5624
lines changed

Some content is hidden

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

660 files changed

+10303
-5624
lines changed

.openpublishing.redirection.json

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16444,6 +16444,71 @@
1644416444
"redirect_url": "/azure/service-fabric/service-fabric-tutorial-deploy-app-to-party-cluster",
1644516445
"redirect_document_id": false
1644616446
},
16447+
{
16448+
"source_path": "articles/migrate/contoso-migration-infrastructure.md",
16449+
"redirect_url": "contoso-migration-overview",
16450+
"redirect_document_id": false
16451+
},
16452+
{
16453+
"source_path": "articles/migrate/contoso-migration-assessment.md",
16454+
"redirect_url": "contoso-migration-overview",
16455+
"redirect_document_id": false
16456+
},
16457+
{
16458+
"source_path": "articles/migrate/contoso-migration-rehost-vm-sql-managed-instance.md",
16459+
"redirect_url": "contoso-migration-overview",
16460+
"redirect_document_id": false
16461+
},
16462+
{
16463+
"source_path": "articles/migrate/contoso-migration-rehost-vm.md",
16464+
"redirect_url": "contoso-migration-overview",
16465+
"redirect_document_id": false
16466+
},
16467+
{
16468+
"source_path": "articles/migrate/contoso-migration-rehost-vm-sql-ag.md",
16469+
"redirect_url": "contoso-migration-overview",
16470+
"redirect_document_id": false
16471+
},
16472+
{
16473+
"source_path": "articles/migrate/contoso-migration-rehost-linux-vm.md",
16474+
"redirect_url": "contoso-migration-overview",
16475+
"redirect_document_id": false
16476+
},
16477+
{
16478+
"source_path": "articles/migrate/contoso-migration-rehost-linux-vm-mysql.md",
16479+
"redirect_url": "contoso-migration-overview",
16480+
"redirect_document_id": false
16481+
},
16482+
{
16483+
"source_path": "articles/migrate/contoso-migration-refactor-web-app-sql.md",
16484+
"redirect_url": "contoso-migration-overview",
16485+
"redirect_document_id": false
16486+
},
16487+
{
16488+
"source_path": "articles/migrate/contoso-migration-refactor-linux-app-service-mysql.md",
16489+
"redirect_url": "contoso-migration-overview",
16490+
"redirect_document_id": false
16491+
},
16492+
{
16493+
"source_path": "articles/migrate/contoso-migration-tfs-vsts.md",
16494+
"redirect_url": "contoso-migration-overview",
16495+
"redirect_document_id": false
16496+
},
16497+
{
16498+
"source_path": "articles/migrate/contoso-migration-rearchitect-container-sql.md",
16499+
"redirect_url": "contoso-migration-overview",
16500+
"redirect_document_id": false
16501+
},
16502+
{
16503+
"source_path": "articles/migrate/contoso-migration-rebuild.md",
16504+
"redirect_url": "contoso-migration-overview",
16505+
"redirect_document_id": false
16506+
},
16507+
{
16508+
"source_path": "articles/migrate/contoso-migration-scale.md",
16509+
"redirect_url": "contoso-migration-overview",
16510+
"redirect_document_id": false
16511+
},
1644716512
{
1644816513
"source_path": "articles/migrate/migrate-best-practices-costs.md",
1644916514
"redirect_url": "https://docs.microsoft.com/azure/architecture/cloud-adoption/migrate/azure-best-practices/migrate-best-practices-costs",
@@ -37193,6 +37258,16 @@
3719337258
"redirect_url": "/azure/azure-monitor/platform/activity-log-collect-tenants",
3719437259
"redirect_document_id": false
3719537260
},
37261+
{
37262+
"source_path": "articles/azure-monitor/platform/oms-portal-transition.md",
37263+
"redirect_url": "/azure/azure-monitor/overview",
37264+
"redirect_document_id": false
37265+
},
37266+
{
37267+
"source_path": "articles/azure-monitor/platform/oms-portal-faq.md",
37268+
"redirect_url": "/azure/azure-monitor/overview",
37269+
"redirect_document_id": false
37270+
},
3719637271
{
3719737272
"source_path": "articles/analysis-services/analysis-services-import-pbix.md",
3719837273
"redirect_url": "/azure/analysis-services/analysis-services-overview",
Lines changed: 23 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Set up sign-up and sign-in with a Microsoft account - Azure Active Directory B2C | Microsoft Docs
2+
title: Set up sign-up and sign-in with a Microsoft account - Azure Active Directory B2C
33
description: Provide sign-up and sign-in to customers with Microsoft accounts in your applications using Azure Active Directory B2C.
44
services: active-directory-b2c
55
author: mmacy
@@ -8,7 +8,7 @@ manager: celestedg
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 09/21/2018
11+
ms.date: 06/11/2019
1212
ms.author: marsma
1313
ms.subservice: B2C
1414
---
@@ -19,22 +19,28 @@ ms.subservice: B2C
1919

2020
To use a Microsoft account as an [identity provider](active-directory-b2c-reference-oidc.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 Microsoft account, you can get it at [https://www.live.com/](https://www.live.com/).
2121

22-
1. Sign in to the [Microsoft Application Registration Portal](https://apps.dev.microsoft.com/?referrer=https://azure.microsoft.com/documentation/articles&deeplink=/appList) with your Microsoft account credentials.
23-
2. In the upper-right corner, select **Add an app**.
24-
3. Enter a **Name** for your application. For example, *MSAapp1*.
25-
4. Select **Generate New Password** and make sure that you copy the password to use when you configure the identity provider. Also copy the **Application Id**.
26-
5. Select **Add platform**, and then and choose **Web**.
27-
4. Enter `https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com/oauth2/authresp` in **Redirect URLs**. Replace `your-tenant-name` with the name of your tenant.
28-
5. Select **Save**.
22+
1. Sign in to the [Azure portal](https://portal.azure.com/).
23+
1. Select **All services** in the top-left corner of the Azure portal, and then search for and select **App registrations**.
24+
1. Select **New registration**
25+
1. Enter a **Name** for your application. For example, *MSAapp1*.
26+
1. Under **Supported account types**, select **Accounts in any organizational directory and personal Microsoft accounts (e.g. Skype, Xbox, Outlook.com)**. This option targets the widest set of Microsoft identities.
27+
28+
For more information on the different account type selections, see [Quickstart: Register an application with the Microsoft identity platform](../active-directory/develop/quickstart-register-app.md).
29+
1. Under **Redirect URI (optional)**, select **Web** and enter `https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com/oauth2/authresp` in the text box. Replace `your-tenant-name` with your Azure AD B2C tenant name.
30+
1. Select **Register**
31+
1. Record the **Application (client) ID** shown on the application Overview page. You need this when you configure the identity provider in the next section.
32+
1. Select **Certificates & secrets**
33+
1. Click **New client secret**
34+
1. Enter a **Description** for the secret, for example *Application password 1*, and then click **Add**.
35+
1. Record the application password shown in the **VALUE** column. You need this when you configure the identity provider in the next section.
2936

3037
## Configure a Microsoft account as an identity provider
3138

3239
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 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. Provide a **Name**. For example, enter *MSA*.
37-
6. Select **Identity provider type**, select **Microsoft Account**, and click **OK**.
38-
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.
39-
8. Click **OK** and then click **Create** to save your Microsoft account configuration.
40-
40+
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.
41+
1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
42+
1. Select **Identity providers**, and then select **Add**.
43+
1. Provide a **Name**. For example, enter *MSA*.
44+
1. Select **Identity provider type**, select **Microsoft Account**, and click **OK**.
45+
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.
46+
1. Click **OK** and then click **Create** to save your Microsoft account configuration.
50.6 KB
Loading
23.8 KB
Loading
15.4 KB
Loading
9.67 KB
Loading

articles/active-directory-b2c/tutorial-add-identity-providers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ After you create the application for the identity provider that you want to add,
102102
For example, `https://login.microsoftonline.com/contoso.onmicrosoft.com/.well-known/openid-configuration`.
103103
104104
8. For **Client ID**, enter the application ID that you previously recorded and for **Client secret**, enter the key value that you previously recorded.
105-
9. Optionally, enter a value for **Domain_hint**. For example, `ContosoAD`.
105+
9. Optionally, enter a value for **Domain_hint**. For example, `ContosoAD`. Domain hints(https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-authentication-for-federated-users-portal) are directives that are included in the authentication request from an application. They can be used to accelerate the user to their federated IdP sign-in page. Or they can be used by a multi-tenant application to accelerate the user straight to the branded Azure AD sign-in page for their tenant.
106106
10. Click **OK**.
107107
11. Select **Map this identity provider's claims** and set the following claims:
108108

articles/active-directory-b2c/tutorial-create-tenant.md

Lines changed: 19 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Tutorial - Create an Azure Active Directory B2C tenant | Microsoft Docs
2+
title: Tutorial - Create an Azure Active Directory B2C tenant
33
description: Learn how to prepare for registering your applications by creating an Azure Active Directory B2C tenant using the Azure portal.
44
services: B2C
55
author: mmacy
@@ -8,7 +8,7 @@ manager: celestedg
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 01/11/2019
11+
ms.date: 06/07/2019
1212
ms.author: marsma
1313
ms.subservice: B2C
1414
---
@@ -30,23 +30,28 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
3030
## Create an Azure AD B2C tenant
3131

3232
1. Sign in to the [Azure portal](https://portal.azure.com/).
33-
2. Make sure that you are using the directory that contains your subscription by clicking the **Directory and subscription filter** in the top menu and choosing the directory that contains it. This directory is different from the one that will contain your Azure AD B2C tenant.
33+
2. Make sure you're using the directory that contains your subscription. Click the **Directory and subscription filter** in the top menu, then select the directory that contains your subscription. This directory is different from the one that will contain your Azure AD B2C tenant.
3434

35-
![Switch to subscription directory](./media/tutorial-create-tenant/switch-directory-subscription.png)
35+
![Switch to subscription directory](./media/tutorial-create-tenant/switch-directory-subscription.PNG)
3636

3737
3. Choose **Create a resource** in the top-left corner of the Azure portal.
3838
4. Search for and select **Active Directory B2C**, and then click **Create**.
39-
5. Choose **Create a new Azure AD B2C Tenant**, enter an organization name and initial domain name, which is used in the tenant name, select the country/region (it can't be changed later), and then click **Create**.
39+
5. Choose **Create a new Azure AD B2C Tenant** and enter an organization name and initial domain name. Select the country/region (it can't be changed later), and then click **Create**.
4040

41-
![Create a tenant](./media/tutorial-create-tenant/create-tenant.png)
41+
The initial domain name is used as part of your tenant name. In this example, the tenant name is *contoso0926Tenant.onmicrosoft.com*:
4242

43-
In this example, the tenant name is contoso0926Tenant.onmicrosoft.com
43+
![Create a tenant](./media/tutorial-create-tenant/create-tenant.PNG)
4444

45-
6. On the **Create new B2C Tenant or Link to an exiting Tenant** page, choose **Link an existing Azure AD B2C Tenant to my Azure subscription**, select the tenant that you created, select your subscription, and then click **Create new**.
46-
7. Enter a name for the resource group that will contain the tenant, select the location, and then click **Create**.
47-
8. To start using your new tenant, make sure you are 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 it.
45+
6. On the **Create new B2C Tenant or Link to existing Tenant** page, choose **Link an existing Azure AD B2C Tenant to my Azure subscription**.
4846

49-
![Switch to tenant directory](./media/tutorial-create-tenant/switch-directories.png)
47+
Select the tenant that you created, and select your subscription.
48+
49+
For resource group, select **Create new**. Enter a name for the resource group that will contain the tenant, select the location, and then click **Create**.
50+
1. To start using your new tenant, 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 it.
51+
52+
If at first you don't see your new Azure B2C tenant in the list, refresh your browser window, then select the **Directory and subscription filter** again in the top menu.
53+
54+
![Switch to tenant directory](./media/tutorial-create-tenant/switch-directories.PNG)
5055

5156
## Next steps
5257

@@ -56,5 +61,7 @@ In this article, you learned how to:
5661
> * Create an Azure AD B2C tenant
5762
> * Link your tenant to your subscription
5863
64+
Next, learn how to register a web application in your new tenant.
65+
5966
> [!div class="nextstepaction"]
60-
> [Register your applications](tutorial-register-applications.md)
67+
> [Register your applications >](tutorial-register-applications.md)

0 commit comments

Comments
 (0)