Skip to content

Commit 4ef54c5

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into freshness68
2 parents d8930dd + 0dd00a6 commit 4ef54c5

File tree

1,186 files changed

+18645
-9402
lines changed

Some content is hidden

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

1,186 files changed

+18645
-9402
lines changed

.openpublishing.redirection.json

Lines changed: 76 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/sql-database/sql-database-feature-restrictions.md",
5+
"redirect_url": "/azure/sql-database",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path": "articles/digital-twins/how-to-use-legacy-aad.md",
510
"redirect_url": "/azure/digital-twins/quickstart-view-occupancy-dotnet#set-permissions-for-your-app",
@@ -40,6 +45,26 @@
4045
"redirect_url": "/azure//virtual-machines/windows/sql/virtual-machines-windows-portal-sql-create-failover-cluster-premium-file-share",
4146
"redirect_document_id": false
4247
},
48+
{
49+
"source_path": "articles/virtual-machines/windows/maintenance-and-updates.md",
50+
"redirect_url": "/azure/virtual-machines/maintenance-and-updates?toc=/azure/virtual-machines/windows/toc.json&bc=/azure/virtual-machines/windows/breadcrumb/toc.json",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "articles/virtual-machines/linux/maintenance-and-updates.md",
55+
"redirect_url": "/azure/virtual-machines/maintenance-and-updates?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "articles/virtual-machines/windows/maintenance-notifications.md",
60+
"redirect_url": "/azure/virtual-machines/maintenance-notifications?toc=/azure/virtual-machines/windows/toc.json&bc=/azure/virtual-machines/windows/breadcrumb/toc.json",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path": "articles/virtual-machines/linux/maintenance-notifications.md",
65+
"redirect_url": "/azure/virtual-machines/maintenance-notifications?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json",
66+
"redirect_document_id": false
67+
},
4368
{
4469
"source_path": "articles/machine-learning/service/how-to-load-data.md",
4570
"redirect_url": "/azure/machine-learning/service/how-to-create-register-datasets",
@@ -532,11 +557,21 @@
532557
"redirect_url": "/azure/machine-learning",
533558
"redirect_document_id": false
534559
},
560+
{
561+
"source_path": "articles/cognitive-services/QnAMaker/Quickstarts/get-answer-from-kb-using-postman.md",
562+
"redirect_url": "/azure/cognitive-services//QnAMaker/Quickstarts/get-answer-from-knowledge-base-using-url-tool",
563+
"redirect_document_id": false
564+
},
565+
{
566+
"source_path": "articles/cognitive-services/QnAMaker/Quickstarts/get-answer-from-kb-using-curl.md",
567+
"redirect_url": "/azure/cognitive-services//QnAMaker/Quickstarts/get-answer-from-knowledge-base-using-url-tool",
568+
"redirect_document_id": false
569+
},
535570
{
536571
"source_path": "articles/cognitive-services/LUIS/luis-how-to-add-example-utterances.md",
537572
"redirect_url": "/azure/cognitive-services/LUIS/luis-how-to-add-entities",
538573
"redirect_document_id": false
539-
},
574+
},
540575
{
541576
"source_path": "articles/cognitive-services/LUIS/luis-tutorial-prebuilt-intents-entities.md",
542577
"redirect_url": "/azure/cognitive-services/LUIS/tutorial-machine-learned-entity",
@@ -43766,6 +43801,46 @@
4376643801
"source_path": "articles/healthcare-apis/configure-cosmos-db.md",
4376743802
"redirect_url": "/azure/healthcare-apis/configure-database",
4376843803
"redirect_document_id": false
43804+
},
43805+
{
43806+
"source_path": "articles/media-services/previous/media-services-azure-media-clipper-portal.md",
43807+
"redirect_url": "/azure/media-services/latest",
43808+
"redirect_document_id": false
43809+
},
43810+
{
43811+
"source_path": "articles/media-services/previous/media-services-azure-media-clipper-getting-started.md",
43812+
"redirect_url": "/azure/media-services/latest",
43813+
"redirect_document_id": false
43814+
},
43815+
{
43816+
"source_path": "articles/media-services/previous/media-services-azure-media-clipper-load-assets.md",
43817+
"redirect_url": "/azure/media-services/latest",
43818+
"redirect_document_id": false
43819+
},
43820+
{
43821+
"source_path": "articles/media-services/previous/media-services-azure-media-clipper-keyboard-shortcuts.md",
43822+
"redirect_url": "/azure/media-services/latest",
43823+
"redirect_document_id": false
43824+
},
43825+
{
43826+
"source_path": "articles/media-services/previous/media-services-azure-media-clipper-localization.md",
43827+
"redirect_url": "/azure/media-services/latest",
43828+
"redirect_document_id": false
43829+
},
43830+
{
43831+
"source_path": "articles/media-services/previous/media-services-azure-media-clipper-submit-job.md",
43832+
"redirect_url": "/azure/media-services/latest",
43833+
"redirect_document_id": false
43834+
},
43835+
{
43836+
"source_path": "articles/media-services/previous/media-services-azure-media-clipper-overview.md",
43837+
"redirect_url": "/azure/media-services/latest",
43838+
"redirect_document_id": false
43839+
},
43840+
{
43841+
"source_path": "articles/lab-services/classroom-labs/how-to-enable-multi-vm-environment.md",
43842+
"redirect_url": "/azure/lab-services/classroom-labs/how-to-enable-nested-virtualization-template-vm",
43843+
"redirect_document_id": false
4376943844
}
4377043845
]
4377143846
}

articles/active-directory-b2c/active-directory-b2c-apps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ To set up client credential flow, see [Azure Active Directory v2.0 and the OAuth
120120

121121
#### Web API chains (on-behalf-of flow)
122122

123-
Many architectures include a web API that needs to call another downstream web API, where both are secured by Azure AD B2C. This scenario is common in native clients that have a Web API back-end and calls a Microsoft online service such as the Azure AD Graph API.
123+
Many architectures include a web API that needs to call another downstream web API, where both are secured by Azure AD B2C. This scenario is common in native clients that have a Web API back-end and calls a Microsoft online service such as the Microsoft Graph API or Azure AD Graph API.
124124

125125
This chained web API scenario can be supported by using the OAuth 2.0 JWT bearer credential grant, also known as the on-behalf-of flow. However, the on-behalf-of flow is not currently implemented in the Azure AD B2C.
126126

articles/active-directory-b2c/active-directory-b2c-quickstarts-desktop-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Quickstart - Set up sign-in for a desktop app using Azure Active Directory B2C
3-
description: Run a sample WPF desktop application that uses Azure Active Directory B2C to provide account sign-in.
3+
description: In this Quickstart, run a sample WPF desktop application that uses Azure Active Directory B2C to provide account sign-in.
44
services: active-directory-b2c
55
author: mmacy
66
manager: celestedg

articles/active-directory-b2c/active-directory-b2c-quickstarts-spa.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Quickstart - Set up sign-in for a single-page app using Azure Active Directory B2C
3-
description: Run a sample single-page application that uses Azure Active Directory B2C to provide account sign-in.
3+
description: In this Quickstart, run a sample single-page application that uses Azure Active Directory B2C to provide account sign-in.
44
services: active-directory-b2c
55
author: mmacy
66
manager: celestedg

articles/active-directory-b2c/active-directory-b2c-quickstarts-web-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Quickstart - Set up sign in for an ASP.NET application using Azure Active Directory B2C
3-
description: Run a sample ASP.NET web app that uses Azure Active Directory B2C to provide account sign-in.
3+
description: In this Quickstart, run a sample ASP.NET web app that uses Azure Active Directory B2C to provide account sign-in.
44
services: active-directory-b2c
55
author: mmacy
66
manager: celestedg

articles/active-directory-b2c/active-directory-b2c-tutorials-desktop-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Record the **Application (client) ID** for use in a later step.
3939

4040
## Configure the sample
4141

42-
In this tutorial, you configure a sample that you can download from GitHub. The sample WPF desktop application demonstrates sign-up, sign-in, and can call a protected web API in Azure AD B2C. [Download a zip file](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop/archive/master.zip), [browse the repo](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop), or clone the sample from GitHub.
42+
In this tutorial, you configure a sample that you can download from GitHub. The sample WPF desktop application demonstrates sign-up, sign-in, and can call a protected web API in Azure AD B2C. [Download a zip file](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop/archive/msalv3.zip), [browse the repo](https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop), or clone the sample from GitHub.
4343

4444
```
4545
git clone https://github.com/Azure-Samples/active-directory-b2c-dotnet-desktop.git

articles/active-directory-b2c/active-directory-b2c-tutorials-spa-webapi.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Tutorial - Grant access to an ASP.NET Core web API from a single-page application - Azure Active Directory B2C
3-
description: Learn how to use Active Directory B2C to protect a .NET Core web API and call the API from a single-page Node.js application.
3+
description: In this tutorial, learn how to use Active Directory B2C to protect a .NET Core web API and call the API from a single-page Node.js application.
44
services: active-directory-b2c
55
author: mmacy
66
manager: celestedg

articles/active-directory-b2c/active-directory-b2c-tutorials-spa.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: 'Tutorial: Enable authentication in a single-page application - Azure Active Directory B2C'
3-
description: Learn how to use Azure Active Directory B2C to provide user login for a single page application (JavaScript).
2+
title: 'Tutorial - Enable authentication in a single-page application - Azure Active Directory B2C'
3+
description: In this tutorial, learn how to use Azure Active Directory B2C to provide user login for a single page application (JavaScript).
44
services: active-directory-b2c
55
author: mmacy
66
manager: celestedg

articles/active-directory-domain-services/administration-concepts.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,9 @@ For users synchronized from an on-premises AD DS environment using Azure AD Conn
5656
5757
Once appropriately configured, the usable password hashes are stored in the Azure AD DS managed domain. If you delete the Azure AD DS managed domain, any password hashes stored at that point are also deleted. Synchronized credential information in Azure AD can't be reused if you later create an Azure AD DS managed domain - you must reconfigure the password hash synchronization to store the password hashes again. Previously domain-joined VMs or users won't be able to immediately authenticate - Azure AD needs to generate and store the password hashes in the new Azure AD DS managed domain. For more information, see [Password hash sync process for Azure AD DS and Azure AD Connect][azure-ad-password-sync].
5858

59+
> [!IMPORTANT]
60+
> Azure AD Connect should only be installed and configured for synchronization with on-premises AD DS environments. It's not supported to install Azure AD Connect in an Azure AD DS managed domain to synchronize objects back to Azure AD.
61+
5962
## Forests and trusts
6063

6164
A *forest* is a logical construct used by Active Directory Domain Services (AD DS) to group one or more *domains*. The domains then store objects for user or groups, and provide authentication services.

articles/active-directory-domain-services/create-gmsa.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,17 @@ ms.service: active-directory
1010
ms.subservice: domain-services
1111
ms.workload: identity
1212
ms.topic: conceptual
13-
ms.date: 09/09/2019
13+
ms.date: 11/26/2019
1414
ms.author: iainfou
1515

1616
---
1717
# Create a group managed service account (gMSA) in Azure AD Domain Services
1818

19-
Applications and services often need an identity to authenticate themselves with other resources. For example, a web service may need to authenticate with a database service. If an application or service has multiple instances, such as a web server farm, manually creating and configuring the identities for those resources gets time consuming. Instead, a group managed service account (gMSA) can be created in the Azure Active Directory Domain Services (Azure AD DS) managed domain. The Windows OS automatically manages the credentials for a gMSA, which simplifies the management of large groups of resources.
19+
Applications and services often need an identity to authenticate themselves with other resources. For example, a web service may need to authenticate with a database service. If an application or service has multiple instances, such as a web server farm, manually creating and configuring the identities for those resources gets time consuming.
2020

21-
This article shows you how to create a gMSA in an Azure AD DS managed domain.
21+
Instead, a group managed service account (gMSA) can be created in the Azure Active Directory Domain Services (Azure AD DS) managed domain. The Windows OS automatically manages the credentials for a gMSA, which simplifies the management of large groups of resources.
22+
23+
This article shows you how to create a gMSA in an Azure AD DS managed domain using Azure PowerShell.
2224

2325
## Before you begin
2426

@@ -56,6 +58,9 @@ As Azure AD DS managed domains are locked down and managed by Microsoft, there a
5658

5759
First, create a custom OU using the [New-ADOrganizationalUnit][New-AdOrganizationalUnit] cmdlet. For more information on creating and managing custom OUs, see [Custom OUs in Azure AD DS][create-custom-ou].
5860

61+
> [!TIP]
62+
> To complete these steps to create a gMSA, [use your management VM][tutorial-create-management-vm]. This management VM should already have the required AD PowerShell cmdlets and connection to the managed domain.
63+
5964
The following example creates a custom OU named *myNewOU* in the Azure AD DS managed domain named *contoso.com*. Use your own OU and managed domain name:
6065

6166
```powershell

0 commit comments

Comments
 (0)