Merge pull request #157772 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)

Author: john-par

articles/dms/tutorial-sql-server-managed-instance-online.md

@@ -79,6 +79,9 @@ To complete this tutorial, you need to:
 * Make a note of a Windows user (and password) that has full control privilege on the network share that you previously created. Azure Database Migration Service impersonates the user credential to upload the backup files to Azure Storage container for restore operation.
 * Create an Azure Active Directory Application ID that generates the Application ID key that Azure Database Migration Service can use to connect to target Azure Database Managed Instance and Azure Storage Container. For more information, see the article [Use portal to create an Azure Active Directory application and service principal that can access resources](../active-directory/develop/howto-create-service-principal-portal.md).
 
+  > [!NOTE]
+  > The Application ID used by the Azure Database Migration Service supports secret (password-based) authentication for service principals. It does not support certificate-based authentication.
+
   > [!NOTE]
   > Azure Database Migration Service requires the Contributor permission on the subscription for the specified Application ID. Alternatively, you can create custom roles that grant the specific permissions that Azure Database Migration Service requires. For step-by-step guidance about using custom roles, see the article [Custom roles for SQL Server to SQL Managed Instance online migrations](./resource-custom-roles-sql-db-managed-instance.md).
 

articles/frontdoor/standard-premium/concept-private-link.md

@@ -34,7 +34,7 @@ When you enable Private Link to your origin in Azure Front Door Premium configur
 :::image type="content" source="../media/concept-private-link/enable-private-endpoint.png" alt-text="Enable Private Endpoint":::
 
 > [!NOTE]
-> Once you enable a Private Link origin and approve the private endpoint conenction, it takes a few minutes for the connection to be established. During this time, requests to the origin will receive a Front Door error message. The error message will go away once the connection is established.
+> Once you enable a Private Link origin and approve the private endpoint connection, it takes a few minutes for the connection to be established. During this time, requests to the origin will receive a Front Door error message. The error message will go away once the connection is established.
 
 ## Limitations
 

articles/storage/blobs/network-file-system-protocol-support.md

@@ -123,7 +123,7 @@ The status of items that appear in this tables will change over time as support
 
 - NFS 3.0 support can't be enabled on existing storage accounts.
 
-- NFS 3.0 support cant' be disabled in a storage account after you've enabled it.
+- NFS 3.0 support can't be disabled in a storage account after you've enabled it.
 
 -  Files can't be viewed in either the Azure portal or Azure Storage Explorer. To list files and directories, either [mount a Blob Storage container by using the NFS 3.0 protocol](network-file-system-protocol-support-how-to.md), or use the [Blob service REST API](/rest/api/storageservices/blob-service-rest-api).
 

articles/storage/common/storage-auth-aad-msi.md

@@ -67,7 +67,7 @@ To create a service principal with Azure CLI and assign an Azure role, call the
 
 If you do not have sufficient permissions to assign a role to the service principal, you may need to ask the account owner or administrator to perform the role assignment.
 
-The following example uses the Azure CLI to create a new service principal and assign the **Storage Blob Data Reader** role to it with account scope
+The following example uses the Azure CLI to create a new service principal and assign the **Storage Blob Data Contributor** role to it with account scope
 
 ```azurecli-interactive
 az ad sp create-for-rbac \
@@ -167,4 +167,4 @@ async static Task CreateBlockBlobAsync(string accountName, string containerName,
 - [Manage access rights to storage data with Azure RBAC](./storage-auth-aad-rbac-portal.md).
 - [Use Azure AD with storage applications](storage-auth-aad-app.md).
 - [Run PowerShell commands with Azure AD credentials to access blob data](../blobs/authorize-data-operations-powershell.md)
-- [Tutorial: Access storage from App Service using managed identities](../../app-service/scenario-secure-app-access-storage.md)
+- [Tutorial: Access storage from App Service using managed identities](../../app-service/scenario-secure-app-access-storage.md)

articles/virtual-machines/linux/disk-encryption-sample-scripts.md

@@ -263,7 +263,7 @@ To configure encryption during the distribution installation, do the following s
 
    ![openSUSE 13.2 Setup - Provide passphrase on boot](./media/disk-encryption/opensuse-encrypt-fig2.png)
 
-3. Prepare the VM for uploading to Azure by following the instructions in [Prepare a SLES or openSUSE virtual machine for Azure](./suse-create-upload-vhd.md?toc=/azure/virtual-machines/linux/toc.json#prepare-opensuse-131). Don't run the last step (deprovisioning the VM) yet.
+3. Prepare the VM for uploading to Azure by following the instructions in [Prepare a SLES or openSUSE virtual machine for Azure](./suse-create-upload-vhd.md?toc=/azure/virtual-machines/linux/toc.json#prepare-opensuse-152). Don't run the last step (deprovisioning the VM) yet.
 
 To configure encryption to work with Azure, do the following steps:
 1. Edit the /etc/dracut.conf, and add the following line:

articles/virtual-machines/linux/suse-create-upload-vhd.md

@@ -11,20 +11,20 @@ ms.date: 12/01/2020
 ms.author: danis
 
 ---
-# Prepare a SLES or openSUSE virtual machine for Azure
+# Prepare a SLES or openSUSE Leap virtual machine for Azure
 
 
-This article assumes that you have already installed a SUSE or openSUSE Linux operating system to a virtual hard disk. Multiple tools exist to create .vhd files, for example a virtualization solution such as Hyper-V. For instructions, see [Install the Hyper-V Role and Configure a Virtual Machine](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh846766(v=ws.11)).
+This article assumes that you have already installed a SUSE or openSUSE Leap Linux operating system to a virtual hard disk. Multiple tools exist to create .vhd files, for example a virtualization solution such as Hyper-V. For instructions, see [Install the Hyper-V Role and Configure a Virtual Machine](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh846766(v=ws.11)).
 
-## SLES / openSUSE installation notes
+## SLES / openSUSE Leap installation notes
 * Please see also [General Linux Installation Notes](create-upload-generic.md#general-linux-installation-notes) for more tips on preparing Linux for Azure.
 * The VHDX format is not supported in Azure, only **fixed VHD**.  You can convert the disk to VHD format using Hyper-V Manager or the convert-vhd cmdlet.
 * When installing the Linux system it is recommended that you use standard partitions rather than LVM (often the default for many installations). This will avoid LVM name conflicts with cloned VMs, particularly if an OS disk ever needs to be attached to another VM for troubleshooting. [LVM](/previous-versions/azure/virtual-machines/linux/configure-lvm) or [RAID](/previous-versions/azure/virtual-machines/linux/configure-raid) may be used on data disks if preferred.
 * Do not configure a swap partition on the OS disk. The Linux agent can be configured to create a swap file on the temporary resource disk.  More information about this can be found in the steps below.
 * All VHDs on Azure must have a virtual size aligned to 1MB. When converting from a raw disk to VHD you must ensure that the raw disk size is a multiple of 1MB before conversion. See [Linux Installation Notes](create-upload-generic.md#general-linux-installation-notes) for more information.
 
 ## Use SUSE Studio
-[SUSE Studio](https://studioexpress.opensuse.org/) can easily create and manage your SLES and openSUSE images for Azure and Hyper-V. This is the recommended approach for customizing your own SLES and openSUSE images.
+[SUSE Studio](https://studioexpress.opensuse.org/) can easily create and manage your SLES and openSUSE Leap images for Azure and Hyper-V. This is the recommended approach for customizing your own SLES and openSUSE Leap images.
 
 As an alternative to building your own VHD, SUSE also publishes BYOS (Bring Your Own Subscription) images for SLES at [VM Depot](https://www.microsoft.com/research/wp-content/uploads/2016/04/using-and-contributing-vms-to-vm-depot.pdf).
 
@@ -152,23 +152,23 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (Bring Your
 16. Click **Action -> Shut Down** in Hyper-V Manager. Your Linux VHD is now ready to be uploaded to Azure.
 
 ---
-## Prepare openSUSE 13.1+
+## Prepare openSUSE 15.2+
 1. In the center pane of Hyper-V Manager, select the virtual machine.
 2. Click **Connect** to open the window for the virtual machine.
 3. On the shell, run the command '`zypper lr`'. If this command returns output similar to the following, then the repositories are configured as expected--no adjustments are necessary (note that version numbers may vary):
 
    | # | Alias                 | Name                  | Enabled | Refresh
    | - | :-------------------- | :-------------------- | :------ | :------
-   | 1 | Cloud:Tools_13.1      | Cloud:Tools_13.1      | Yes     | Yes
-   | 2 | openSUSE_13.1_OSS     | openSUSE_13.1_OSS     | Yes     | Yes
-   | 3 | openSUSE_13.1_Updates | openSUSE_13.1_Updates | Yes     | Yes
+   | 1 | Cloud:Tools_15.2      | Cloud:Tools_15.2      | Yes     | Yes
+   | 2 | openSUSE_15.2_OSS     | openSUSE_15.2_OSS     | Yes     | Yes
+   | 3 | openSUSE_15.2_Updates | openSUSE_15.2_Updates | Yes     | Yes
 
     If the command returns "No repositories defined..." then use the following commands to add these repos:
 
     ```console
-    # sudo zypper ar -f http://download.opensuse.org/repositories/Cloud:Tools/openSUSE_13.1 Cloud:Tools_13.1
-    # sudo zypper ar -f https://download.opensuse.org/distribution/13.1/repo/oss openSUSE_13.1_OSS
-    # sudo zypper ar -f http://download.opensuse.org/update/13.1 openSUSE_13.1_Updates
+    # sudo zypper ar -f http://download.opensuse.org/repositories/Cloud:Tools/openSUSE_15.2 Cloud:Tools_15.2
+    # sudo zypper ar -f https://download.opensuse.org/distribution/15.2/repo/oss openSUSE_15.2_OSS
+    # sudo zypper ar -f http://download.opensuse.org/update/15.2 openSUSE_15.2_Updates
     ```
 
     You can then verify the repositories have been added by running the command '`zypper lr`' again. In case one of the relevant update repositories is not enabled, enable it with following command:
@@ -250,4 +250,4 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (Bring Your
 13. Click **Action -> Shut Down** in Hyper-V Manager. Your Linux VHD is now ready to be uploaded to Azure.
 
 ## Next steps
-You're now ready to use your SUSE Linux virtual hard disk to create new virtual machines in Azure. If this is the first time that you're uploading the .vhd file to Azure, see [Create a Linux VM from a custom disk](upload-vhd.md#option-1-upload-a-vhd).
+You're now ready to use your SUSE Linux virtual hard disk to create new virtual machines in Azure. If this is the first time that you're uploading the .vhd file to Azure, see [Create a Linux VM from a custom disk](upload-vhd.md#option-1-upload-a-vhd).

includes/event-grid-service-bus.md

@@ -17,15 +17,15 @@ Service Bus emits the following event types:
 | Event type | Description |
 | ---------- | ----------- |
 | Microsoft.ServiceBus.ActiveMessagesAvailableWithNoListeners | Raised when there are active messages in a Queue or Subscription and no receivers listening. |
-| Microsoft.ServiceBus.DeadletterMessagesAvailableWithNoListener | Raised when there are active messages in a Dead Letter Queue and no active listeners. |
+| Microsoft.ServiceBus.DeadletterMessagesAvailableWithNoListeners | Raised when there are active messages in a Dead Letter Queue and no active listeners. |
 | Microsoft.ServiceBus.ActiveMessagesAvailablePeriodicNotifications | Raised periodically if there are active messages in a Queue or Subscription, even if there are active listeners on that specific Queue or Subscription. |
 | Microsoft.ServiceBus.DeadletterMessagesAvailablePeriodicNotifications | Raised periodically if there are messages in the dead-letter entity of a Queue or Subscription, even if there are active listeners on the dead-letter entity of that specific Queue or Subscription. | 
 
 ## Example event
 
 # [Event Grid event schema](#tab/event-grid-event-schema)
 
-### Active messages available with no listeners
+### Active Messages Available With No Listeners
 This event is generated if you have active messages in a queue or a subscription and there are no receivers listening.
 
 ```json
@@ -48,15 +48,15 @@ This event is generated if you have active messages in a queue or a subscription
 }]
 ```
 
-#### Deadletter Messages Available With No Listener
+#### Deadletter Messages Available With No Listeners
 
 The schema for a dead letter queue event is similar. You get at least one event per dead-letter queue that has messages and no active receivers.
 
 ```json
 [{
   "topic": "/subscriptions/{subscription-id}/resourcegroups/{your-rg}/providers/Microsoft.ServiceBus/namespaces/{your-service-bus-namespace}",
   "subject": "topics/{your-service-bus-topic}/subscriptions/{your-service-bus-subscription}",
-  "eventType": "Microsoft.ServiceBus.DeadletterMessagesAvailableWithNoListener",
+  "eventType": "Microsoft.ServiceBus.DeadletterMessagesAvailableWithNoListeners",
   "eventTime": "2018-02-14T05:12:53.4133526Z",
   "id": "dede87b0-3656-419c-acaf-70c95ddc60f5",
   "data": {
@@ -120,7 +120,7 @@ This event is generated periodically if you have deadletter messages on the spec
 
 # [Cloud event schema](#tab/cloud-event-schema)
 
-### Active messages available with no listeners
+### Active Messages Available With No Listeners
 This event is generated if you have active messages in a queue or a subscription and there are no receivers listening.
 
 ```json
@@ -142,15 +142,15 @@ This event is generated if you have active messages in a queue or a subscription
 }]
 ```
 
-#### Deadletter Messages Available With No Listener
+#### Deadletter Messages Available With No Listeners
 
 The schema for a dead letter queue event is similar. You get at least one event per dead-letter queue that has messages and no active receivers.
 
 ```json
 [{
   "source": "/subscriptions/{subscription-id}/resourcegroups/{your-rg}/providers/Microsoft.ServiceBus/namespaces/{your-service-bus-namespace}",
   "subject": "topics/{your-service-bus-topic}/subscriptions/{your-service-bus-subscription}",
-  "type": "Microsoft.ServiceBus.DeadletterMessagesAvailableWithNoListener",
+  "type": "Microsoft.ServiceBus.DeadletterMessagesAvailableWithNoListeners",
   "time": "2018-02-14T05:12:53.4133526Z",
   "id": "dede87b0-3656-419c-acaf-70c95ddc60f5",
   "data": {
@@ -254,4 +254,4 @@ The data object has the following properties:
 | `entityType` | string | The type of Service Bus entity emitting events (queue or subscription). |
 | `queueName` | string | The queue with active messages if subscribing to a queue. Value null if using topics / subscriptions. |
 | `topicName` | string | The topic the Service Bus subscription with active messages belongs to. Value null if using a queue. |
-| `subscriptionName` | string | The Service Bus subscription with active messages. Value null if using a queue. |
+| `subscriptionName` | string | The Service Bus subscription with active messages. Value null if using a queue. |