Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-mto-configuration-delete-steps

rolyon · rolyon · commit 54c81d495e63 · 2023-02-03T10:07:30.000-08:00
diff --git a/articles/aks/api-server-vnet-integration.md b/articles/aks/api-server-vnet-integration.md
@@ -23,9 +23,7 @@ API Server VNet Integration is supported for public or private clusters, and pub
 
 ## Region availability
 
-API Server VNet Integration is available in all global Azure regions except the following:
-
-- Southcentralus
+API Server VNet Integration is available in all global Azure regions.
 
 ## Prerequisites
 
@@ -248,4 +246,4 @@ For associated best practices, see [Best practices for network connectivity and
 [command-invoke]: command-invoke.md
 [container-registry-private-link]: ../container-registry/container-registry-private-link.md
 [virtual-networks-name-resolution]: ../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md#name-resolution-that-uses-your-own-dns-server
-[operator-best-practices-network]: operator-best-practices-network.md
+[operator-best-practices-network]: operator-best-practices-network.md
diff --git a/articles/app-service/manage-custom-dns-buy-domain.md b/articles/app-service/manage-custom-dns-buy-domain.md
@@ -7,7 +7,7 @@ ms.date: 01/31/2023
 ms.custom: seodec18
 
 ---
-# By an App Service domain and configure an app with it
+# Buy an App Service domain and configure an app with it
 
 App Service domains are custom domains that are managed directly in Azure. They make it easy to manage custom domains for [Azure App Service](overview.md). This article shows you how to buy an App Service domain and configure an App Service app with it.
 
diff --git a/articles/azure-netapp-files/faq-smb.md b/articles/azure-netapp-files/faq-smb.md
@@ -28,7 +28,7 @@ However, you can map multiple NetApp accounts that are under the same subscripti
 
 ## Does Azure NetApp Files support Azure Active Directory? 
 
-Both [Azure Active Directory (AD) Domain Services](../active-directory-domain-services/overview.md) and [Active Directory Domain Services (AD DS)](/windows-server/identity/ad-ds/get-started/virtual-dc/active-directory-domain-services-overview) are supported. You can use existing Active Directory domain controllers with Azure NetApp Files. Domain controllers can reside in Azure as virtual machines, or on premises via ExpressRoute or S2S VPN. Azure NetApp Files doesn't support AD join for [Azure Active Directory](https://azure.microsoft.com/resources/videos/azure-active-directory-overview/) at this time.
+Both [Azure Active Directory Domain Services (Azure AD DS)](../active-directory-domain-services/overview.md) and [Active Directory Domain Services (AD DS)](/windows-server/identity/ad-ds/get-started/virtual-dc/active-directory-domain-services-overview) are supported. You can use existing Active Directory domain controllers with Azure NetApp Files. Domain controllers can reside in Azure as virtual machines, or on premises via ExpressRoute or S2S VPN. Azure NetApp Files doesn't support AD join for [Azure Active Directory (Azure AD)](../active-directory/fundamentals/index.yml) at this time.
 
 If you're using Azure NetApp Files with Azure Active Directory Domain Services, the organizational unit path is `OU=AADDC Computers` when you configure Active Directory for your NetApp account.
 
diff --git a/articles/azure-resource-manager/management/delete-resource-group.md b/articles/azure-resource-manager/management/delete-resource-group.md
@@ -119,7 +119,7 @@ az resource delete \
 To delete a resource group, you need access to the delete action for the **Microsoft.Resources/subscriptions/resourceGroups** resource.
 
 > [!IMPORTANT]
-> The only permission required to delete a resource group is permission to the delete action for deleting resource groups.  You do **not** need permission to delete individual resources within that resource group.  Addtionally, delete actions that are specified in **notActions** for a roleAssignment are superseded by the resource group delete action.  This is consistent with the scope heirarchy in the Azure role-based access control model.
+> The only permission required to delete a resource group is permission to the delete action for deleting resource groups.  You do **not** need permission to delete individual resources within that resource group.  Additionally, delete actions that are specified in **notActions** for a roleAssignment are superseded by the resource group delete action.  This is consistent with the scope heirarchy in the Azure role-based access control model.
 
 For a list of operations, see [Azure resource provider operations](../../role-based-access-control/resource-provider-operations.md). For a list of built-in roles, see [Azure built-in roles](../../role-based-access-control/built-in-roles.md).
 
diff --git a/articles/bastion/vm-upload-download-native.md b/articles/bastion/vm-upload-download-native.md
@@ -54,7 +54,7 @@ The steps in this section apply when connecting to a target VM from a Windows lo
 ## <a name="tunnel-command"></a>Upload files - SSH and RDP
 
 The steps in this section apply to native clients other than Windows, as well as Windows native clients that want to connect over SSH to upload files.
-This section helps you upload files from your local computer to your target VM over SSH or RDP using the **az network bastion tunnel** command. This command doesn't support file download from the target VM to your local computer. To learn more about the tunnel command and how to connect, see [Connect to a VM using a native client](connect-native-client-windows.md).
+This section helps you upload files from your local computer to your target VM over SSH or RDP using the **az network bastion tunnel** command. To learn more about the tunnel command and how to connect, see [Connect to a VM using a native client](connect-native-client-windows.md).
 
 > [!NOTE]
 > This command can be used to upload files from your local computer to the target VM. File download is not supported.
diff --git a/articles/cosmos-db/mongodb/how-to-dotnet-manage-databases.md b/articles/cosmos-db/mongodb/how-to-dotnet-manage-databases.md
@@ -78,4 +78,4 @@ A database is removed from the server using the `DropDatabase` method on the DB
 ## See also
 
 - [Get started with Azure Cosmos DB for MongoDB and .NET](how-to-dotnet-get-started.md)
-- Work with a collection](how-to-dotnet-manage-collections.md)
+- [Work with a collection](how-to-dotnet-manage-collections.md)
diff --git a/articles/cosmos-db/nosql/quickstart-java.md b/articles/cosmos-db/nosql/quickstart-java.md
@@ -9,7 +9,7 @@ ms.topic: quickstart
 ms.date: 08/26/2021
 ms.author: sidandrews
 ms.reviewer: mjbrown
-ms.custom: seo-java-august2019, seo-java-september2019, devx-track-java, mode-api, ignite-2022
+ms.custom: seo-java-august2019, seo-java-september2019, devx-track-java, mode-api, ignite-2022, passwordless-java
 ---
 
 # Quickstart: Build a Java app to manage Azure Cosmos DB for NoSQL data
diff --git a/articles/mysql/flexible-server/concepts-networking-vnet.md b/articles/mysql/flexible-server/concepts-networking-vnet.md
@@ -76,7 +76,7 @@ Here are some concepts to be familiar with when using virtual networks with MySQ
 - If you use Azure API, an Azure Resource Manager template (ARM template), or Terraform, create private DNS zones that end with `mysql.database.azure.com` and use them while configuring flexible servers with private access. For more information, see the [private DNS zone overview](../../dns/private-dns-overview.md).
 
    > [!IMPORTANT]  
-   > Private DNS zone names must end with `mysql.database.azure.com`. If you are connecting to an Azure Database for MySQL flexible sever with SSL and you're using an option to perform full verification (sslmode=VERTIFY_IDENTITY) with certificate subject name, use \<servername\>.mysql.database.azure.com in your connection string.
+   > Private DNS zone names must end with `mysql.database.azure.com`. If you are connecting to an Azure Database for MySQL flexible server with SSL and you're using an option to perform full verification (sslmode=VERTIFY_IDENTITY) with certificate subject name, use \<servername\>.mysql.database.azure.com in your connection string.
 
 Learn how to create a flexible server with private access (VNet integration) in [the Azure portal](how-to-manage-virtual-network-portal.md) or [the Azure CLI](how-to-manage-virtual-network-cli.md).
 
diff --git a/articles/mysql/flexible-server/how-to-azure-ad.md b/articles/mysql/flexible-server/how-to-azure-ad.md
@@ -160,7 +160,7 @@ mysql -h mydb.mysql.database.azure.com \
 
 - Launch MySQL Workbench and Select the Database option, then select **Connect to database**.
 - In the hostname field, enter the MySQL FQDN for example, mysql.database.azure.com.
-- In the username field, enter the MySQL Azure Active Directory administrator name and append this with the MySQL server name, not the FQDN for example, user@tenant.onmicrosoft.com.
+- In the username field, enter the MySQL Azure Active Directory administrator name. For example, user@tenant.onmicrosoft.com.
 - In the password field, select **Store in Vault** and paste in the access token from the file for example, C:\temp\MySQLAccessToken.txt.
 - Select the advanced tab and ensure that you check **Enable Cleartext Authentication Plugin**.
 - Select OK to connect to the database.
diff --git a/articles/postgresql/flexible-server/how-to-configure-sign-in-azure-ad-authentication.md b/articles/postgresql/flexible-server/how-to-configure-sign-in-azure-ad-authentication.md
@@ -62,11 +62,11 @@ ObjectId                             AppId                                Displa
 ```
 
 > [!IMPORTANT]  
-> If you are not a **Global Administrator**, **Privileged Role Administrator**, **Tenant Creator**,**Application Owner** you can't proceed past this step.
+> If you are not a **Global Administrator**, **Tenant Creator**, or **Application Owner**, you can't proceed past this step.
 
-### Grant read access
+### Create Azure Database for PostgreSQL Flexible Server service principal and grant read access
 
-Grant Azure Database for PostgreSQL - Flexible Server Service Principal read access to a customer tenant to request Graph API tokens for Azure AD validation tasks:
+If the Azure Database for PostgreSQL Flexible Server service principal doesn't exist, the following command creates it and grants it read access to your customer tenant to request Graph API tokens for Azure AD validation tasks:
 
 ```powershell
 New-AzureADServicePrincipal -AppId 5657e26c-cc92-45d9-bc47-9da6cfdb4ed9
diff --git a/articles/storage/blobs/storage-blob-block-blob-premium.md b/articles/storage/blobs/storage-blob-block-blob-premium.md
@@ -28,7 +28,7 @@ Premium block blob storage accounts are ideal for workloads that require fast an
 
 ## Cost effectiveness
 
-Premium block blob storage accounts have a higher storage cost but a lower transaction cost as compared to standard general-purpose v2 accounts. If your applications and workloads execute a large number of transactions, premium blob blob storage can be cost-effective, especially if the workload is write-heavy.
+Premium block blob storage accounts have a higher storage cost but a lower transaction cost as compared to standard general-purpose v2 accounts. If your applications and workloads execute a large number of transactions, premium block blob storage can be cost-effective, especially if the workload is write-heavy.
 
 In most cases, workloads executing more than 35 to 40 transactions per second per terabyte (TPS/TB) are good candidates for this type of account. For example, if your workload executes 500 million read operations and 100 million write operations in a month, then you can calculate the TPS/TB as follows:
 
diff --git a/articles/virtual-desktop/autoscale-scaling-plan.md b/articles/virtual-desktop/autoscale-scaling-plan.md
@@ -3,7 +3,7 @@ title: Create an autoscale scaling plan for Azure Virtual Desktop
 description: How to create an autoscale scaling plan to optimize deployment costs.
 author: Heidilohr
 ms.topic: how-to
-ms.date: 01/28/2023
+ms.date: 02/03/2023
 ms.author: helohr
 manager: femila
 ms.custom: references_regions
@@ -22,7 +22,7 @@ To learn more about autoscale, see [Autoscale scaling plans and example scenario
 > - Azure Virtual Desktop (classic) doesn't support autoscale. 
 > - Autoscale doesn't support Azure Virtual Desktop for Azure Stack HCI.
 > - Autoscale doesn't support scaling of ephemeral disks.
-> - Autoscale doesn't support scaling of generalized VMs.
+> - Autoscale doesn't support scaling of generalized or sysprepped VMs with machine-specific information removed. For more information, see [Remove machine-specific information by generalizing a VM before creating an image](../virtual-machines/generalize.md).
 > - You can't use autoscale and [scale session hosts using Azure Automation and Azure Logic Apps](scaling-automation-logic-apps.md) on the same host pool. You must use one or the other.
 > - Autoscale is available in Azure and Azure Government.
 
diff --git a/articles/virtual-desktop/autoscale-scenarios.md b/articles/virtual-desktop/autoscale-scenarios.md
@@ -3,7 +3,7 @@ title: Autoscale scaling plans and example scenarios in Azure Virtual Desktop
 description: Information about autoscale and a collection of four example scenarios that illustrate how various parts of autoscale for Azure Virtual Desktop work.
 author: Heidilohr
 ms.topic: conceptual
-ms.date: 08/15/2022
+ms.date: 02/03/2023
 ms.author: helohr
 manager: femila
 ms.custom: references_regions
@@ -20,7 +20,7 @@ Autoscale lets you scale your session host virtual machines (VMs) in a host pool
 > - Azure Virtual Desktop (classic) doesn't support autoscale. 
 > - Autoscale doesn't support Azure Virtual Desktop for Azure Stack HCI.
 > - Autoscale doesn't support scaling of ephemeral disks.
-> - Autoscale doesn't support scaling of generalized VMs.
+> - Autoscale doesn't support scaling of generalized or sysprepped VMs with machine-specific information removed. For more information, see [Remove machine-specific information by generalizing a VM before creating an image](../virtual-machines/generalize.md).
 > - You can't use autoscale and [scale session hosts using Azure Automation](set-up-scaling-script.md) on the same host pool. You must use one or the other.
 > - Autoscale is available in Azure and Azure Government.
 
diff --git a/articles/virtual-wan/how-to-virtual-hub-routing-powershell.md b/articles/virtual-wan/how-to-virtual-hub-routing-powershell.md
@@ -89,10 +89,10 @@ The steps in this section help you set up routing configuration for a virtual ne
 1. Verify static route on the virtual network connection.
 
    ```azurepowershell-interactive
-   Get-AzVirtualHubVnetConnection -ResourceGroupName "[Resource group]" -VirtualHubName "[virtual hub name]" -Name "[Virtual hub connection name]"
+   Get-AzVirtualHubVnetConnection -ResourceGroupName "[Resource group name]" -VirtualHubName "[virtual hub name]" -Name "[Virtual hub connection name]"
    ```
 
 ## Next steps
 
 * For more information about virtual hub routing, see [About virtual hub routing](about-virtual-hub-routing.md).
-* For more information about Virtual WAN, see the [Virtual WAN FAQ](virtual-wan-faq.md).
+* For more information about Virtual WAN, see the [Virtual WAN FAQ](virtual-wan-faq.md).
