Merge pull request #214179 from MicrosoftDocs/main

10/11  3PM Publish

Author: huypub

articles/application-gateway/quick-create-bicep.md

@@ -3,8 +3,8 @@ title: 'Quickstart: Direct web traffic using Bicep'
 titleSuffix: Azure Application Gateway
 description: In this quickstart, you learn how to use Bicep to create an Azure Application Gateway that directs web traffic to virtual machines in a backend pool.
 services: application-gateway
-author: schaffererin
-ms.author: v-eschaffer
+author: KumudD
+ms.author: kumud
 ms.date: 04/14/2022
 ms.topic: quickstart
 ms.service: application-gateway

articles/azure-arc/data/active-directory-introduction.md

@@ -7,16 +7,14 @@ ms.subservice: azure-arc-data-sqlmi
 author: mikhailalmeida
 ms.author: mialmei
 ms.reviewer: mikeray
-ms.date: 04/15/2022
+ms.date: 10/11/2022
 ms.topic: how-to
 ---
 
 # Azure Arc-enabled SQL Managed Instance with Active Directory authentication 
 
 Azure Arc-enabled data services support Active Directory (AD) for Identity and Access Management (IAM). The Arc-enabled SQL Managed Instance uses an existing on-premises Active Directory (AD) domain for authentication. 
 
-[!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
-
 This article describes how to enable Azure Arc-enabled SQL Managed Instance with Active Directory (AD) Authentication. The article demonstrates two possible AD integration modes: 
 -  Customer-managed keytab (CMK) 
 -  System-managed keytab (SMK)  
@@ -55,14 +53,14 @@ To enable Active Directory authentication for Arc-enabled SQL Managed Instance,
 
 The following section compares these modes.
 
-|                  |Customer-managed keytab​|System-managed keytab -  Preview​|
+|                  |Customer-managed keytab​|System-managed keytab|
 |------------------|---------|--------|
 |**Use cases**|Small and medium size businesses who are familiar with managing Active Directory objects and want flexibility in their automation process |All sizes of businesses - seeking to highly automated Active Directory management experience|
 |**User provides**|An Active Directory account and SPNs under that account, and a [keytab file](/sql/linux/sql-server-linux-ad-auth-understanding#what-is-a-keytab-file) for Active Directory authentication |An [Organizational Unit (OU)](../../active-directory-domain-services/create-ou.md) and a domain service account has [sufficient permissions](deploy-system-managed-keytab-active-directory-connector.md?#prerequisites) on that OU in Active Directory.|
 |**Characteristics**|User managed. Users bring the Active Directory account, which impersonates the identity of the managed instance and the keytab file. |System managed. The system creates a domain service account for each managed instance and sets SPNs automatically on that account. It also, creates and delivers a keytab file to the managed instance. |
 |**Deployment process**| 1. Deploy data controller <br/> 2. Create keytab file <br/>3. Set up keytab information to Kubernetes secret<br/> 4. Deploy AD connector, deploy SQL managed instance<br/><br/>For more information, see [Deploy a customer-managed keytab Active Directory connector](deploy-customer-managed-keytab-active-directory-connector.md)  | 1. Deploy data controller, deploy AD connector<br/>2. Deploy SQL managed instance<br/><br/>For more information, see [Deploy a system-managed keytab Active Directory connector](deploy-system-managed-keytab-active-directory-connector.md) |
 |**Manageability**|You can create the keytab file by following the instructions from [Active Directory utility (`adutil`)](/sql/linux/sql-server-linux-ad-auth-adutil-introduction). Manual keytab rotation. |Managed keytab rotation.|
-|**Limitations**|We do not recommend sharing keytab files among services. Each service should have a specific keytab file. As the number of keytab files increases the level of effort and complexity increases. |Managed keytab generation and rotation. The service account will require sufficient permissions in Active Directory to manage the credentials. |
+|**Limitations**|We do not recommend sharing keytab files among services. Each service should have a specific keytab file. As the number of keytab files increases the level of effort and complexity increases. |Managed keytab generation and rotation. The service account will require sufficient permissions in Active Directory to manage the credentials. <br/> <br/> Distributed Availability Group is not supported.|
 
 For either mode, you need a specific Active Directory account, keytab, and Kubernetes secret for each SQL managed instance.
 

articles/azure-arc/data/active-directory-prerequisites.md

@@ -7,16 +7,14 @@ ms.subservice: azure-arc-data-sqlmi
 author: mikhailalmeida
 ms.author: mialmei
 ms.reviewer: mikeray
-ms.date: 04/21/2022
+ms.date: 10/11/2022
 ms.topic: how-to
 ---
 
 # Azure Arc-enabled SQL Managed Instance in Active Directory authentication with system-managed keytab - prerequisites
 
 This document explains how to prepare to deploy Azure Arc-enabled data services with Active Directory (AD) authentication. Specifically the article describes Active Directory objects you need to configure before the deployment of Kubernetes resources.
 
-[!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
-
 [The introduction](active-directory-introduction.md#compare-ad-integration-modes) describes two different integration modes:
 - *System-managed keytab* mode allows the system to create and manage the AD accounts for each SQL Managed Instance.
 - *Customer-managed keytab* mode allows you to create and manage the AD accounts for each SQL Managed Instance.

articles/azure-arc/data/connect-active-directory-sql-managed-instance.md

@@ -7,16 +7,14 @@ ms.subservice: azure-arc-data-sqlmi
 author: mikhailalmeida
 ms.author: mialmei
 ms.reviewer: mikeray
-ms.date: 12/15/2021
+ms.date: 10/11/2022
 ms.topic: how-to
 ---
 
 # Connect to AD-integrated Azure Arc-enabled SQL Managed Instance
 
 This article describes how to connect to SQL Managed Instance endpoint using Active Directory (AD) authentication. Before you proceed, make sure you have an AD-integrated Azure Arc-enabled SQL Managed Instance deployed already.
 
-[!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
-
 See [Tutorial – Deploy AD-integrated SQL Managed Instance](deploy-active-directory-sql-managed-instance.md) to deploy Azure Arc-enabled SQL Managed Instance with Active Directory authentication enabled.
 
 > [!NOTE]

articles/azure-arc/data/deploy-active-directory-connector-cli.md

@@ -7,7 +7,7 @@ ms.subservice: azure-arc-data-sqlmi
 author: mikhailalmeida
 ms.author: mialmei
 ms.reviewer: mikeray
-ms.date: 08/16/2022
+ms.date: 10/11/2022
 ms.topic: how-to
 ---
 
@@ -16,8 +16,6 @@ ms.topic: how-to
 
 This article explains how to deploy an Active Directory (AD) connector using Azure CLI. The AD connector is a key component to enable Active Directory authentication on Azure Arc-enabled SQL Managed Instance.
 
-[!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
-
 ## Prerequisites
 
 ### Install tools

articles/azure-arc/data/deploy-active-directory-connector-portal.md

@@ -7,16 +7,14 @@ ms.subservice: azure-arc-data-sqlmi
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: dinethi
-ms.date: 05/24/2022
+ms.date: 10/11/2022
 ms.topic: how-to
 ---
 
 # Tutorial – Deploy Active Directory connector using Azure portal
 
 Active Directory (AD) connector is a key component to enable Active Directory authentication on Azure Arc-enabled SQL Managed Instances.
 
-[!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
-
 This article explains how to deploy, manage, and delete an Active Directory (AD) connector in directly connected mode from the Azure portal. 
 
 ## Prerequisites

articles/azure-arc/data/deploy-active-directory-sql-managed-instance-cli.md

@@ -7,16 +7,14 @@ ms.subservice: azure-arc-data-sqlmi
 author: mikhailalmeida
 ms.author: mialmei
 ms.reviewer: mikeray
-ms.date: 04/28/2022
+ms.date: 10/11/2022
 ms.topic: how-to
 ---
 
 # Deploy Active Directory integrated Azure Arc-enabled SQL Managed Instance using Azure CLI
 
 This article explains how to deploy Azure Arc-enabled SQL Managed Instance with Active Directory (AD) authentication using Azure CLI.
 
-[!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
-
 See these articles for specific instructions:
 
 - [Tutorial – Deploy AD connector in customer-managed keytab mode](deploy-customer-managed-keytab-active-directory-connector.md)
@@ -56,8 +54,10 @@ az sql mi-arc create
 --ad-connector-name < your AD connector name > 
 --keytab-secret < SQL MI keytab secret name >  
 --ad-account-name < SQL MI AD user account >  
---primary-dns-name < SQL MI DNS endpoint > 
---primary-port-number < SQL MI port number > 
+--primary-dns-name < SQL MI primary endpoint DNS name > 
+--primary-port-number < SQL MI primary endpoint port number > 
+--secondary-dns-name < SQL MI secondary endpoint DNS name > 
+--secondary-port-number < SQL MI secondary endpoint port number > 
 --use-k8s
 ```
 
@@ -72,6 +72,8 @@ az sql mi-arc create
 --ad-account-name arcuser 
 --primary-dns-name arcsqlmi.contoso.local
 --primary-port-number 31433 
+--secondary-dns-name arcsqlmi-2.contoso.local
+--secondary-port-number 31434
 --use-k8s
 ```
 
@@ -82,10 +84,11 @@ az sql mi-arc create
 --name < SQL MI name >  
 --ad-connector-name < your AD connector name > 
 --keytab-secret < SQL MI keytab secret name >  
---ad-account-name < SQL MI AD user account >  
---primary-dns-name < SQL MI DNS endpoint > 
---primary-port-number < SQL MI port number > 
---location < your cloud region >
+--ad-account-name < SQL MI AD user account > 
+--primary-dns-name < SQL MI primary endpoint DNS name > 
+--primary-port-number < SQL MI primary endpoint port number > 
+--secondary-dns-name < SQL MI secondary endpoint DNS name > 
+--secondary-port-number < SQL MI secondary endpoint port number >
 --custom-location < your custom location > 
 --resource-group < resource-group >
 ```
@@ -100,7 +103,8 @@ az sql mi-arc create
 --ad-account-name arcuser 
 --primary-dns-name arcsqlmi.contoso.local
 --primary-port-number 31433 
---location westeurope
+--secondary-dns-name arcsqlmi-2.contoso.local
+--secondary-port-number 31434
 --custom-location private-location
 --resource-group arc-rg
 ```
@@ -172,8 +176,10 @@ az sql mi-arc create
 --k8s-namespace < namespace > 
 --ad-connector-name < your AD connector name > 
 --ad-account-name < SQL MI AD user account >  
---primary-dns-name < SQL MI DNS endpoint > 
---primary-port-number < SQL MI port number > 
+--primary-dns-name < SQL MI primary endpoint DNS name > 
+--primary-port-number < SQL MI primary endpoint port number > 
+--secondary-dns-name < SQL MI secondary endpoint DNS name > 
+--secondary-port-number < SQL MI secondary endpoint port number >
 --use-k8s
 ```
 
@@ -187,6 +193,8 @@ az sql mi-arc create
 --ad-account-name arcuser 
 --primary-dns-name arcsqlmi.contoso.local
 --primary-port-number 31433 
+--secondary-dns-name arcsqlmi-2.contoso.local
+--secondary-port-number 31434
 --use-k8s
 ```
 
@@ -197,9 +205,10 @@ az sql mi-arc create
 --name < SQL MI name >  
 --ad-connector-name < your AD connector name >  
 --ad-account-name < SQL MI AD user account >  
---primary-dns-name < SQL MI DNS endpoint > 
---primary-port-number < SQL MI port number > 
---location < your cloud region >
+--primary-dns-name < SQL MI primary endpoint DNS name > 
+--primary-port-number < SQL MI primary endpoint port number > 
+--secondary-dns-name < SQL MI secondary endpoint DNS name > 
+--secondary-port-number < SQL MI secondary endpoint port number >
 --custom-location < your custom location > 
 --resource-group <resource-group>
 ```
@@ -213,7 +222,8 @@ az sql mi-arc create
 --ad-account-name arcuser 
 --primary-dns-name arcsqlmi.contoso.local
 --primary-port-number 31433 
---location westeurope
+--secondary-dns-name arcsqlmi-2.contoso.local
+--secondary-port-number 31434
 --custom-location private-location
 --resource-group arc-rg
 ```