Merge pull request #270012 from MicrosoftDocs/repo_sync_working_branch

TimShererWithAquent · web-flow · commit 64277c85b04b · 2024-03-25T16:51:47.000Z
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/ai-services/language-service/custom-named-entity-recognition/includes/roles-for-resource-and-storage.md b/articles/ai-services/language-service/custom-named-entity-recognition/includes/roles-for-resource-and-storage.md
@@ -37,5 +37,5 @@ Use the following steps to set the required roles for your Language resource and
 5. Select **Select members**
 6. Select your subscription, and **Language** as the managed identity. You can search for user names in the **Select** field. 
 
-> ![IMPORTANT]
+> [!IMPORTANT]
 > If you have a virtual network or private endpoint, be sure to select **Allow Azure services on the trusted services list to access this storage account** in the Azure portal.
diff --git a/articles/ai-services/language-service/includes/custom/roles-for-resource-and-storage.md b/articles/ai-services/language-service/includes/custom/roles-for-resource-and-storage.md
@@ -37,5 +37,5 @@ Use the following steps to set the required roles for your Language resource and
 5. Select **Select members**
 6. Select your subscription, and **Language** as the managed identity. You can search for user names in the **Select** field. 
 
-> ![IMPORTANT]
+> [!IMPORTANT]
 > If you have a virtual network or private endpoint, be sure to select **Allow Azure services on the trusted services list to access this storage account** in the Azure portal.
diff --git a/articles/ai-services/language-service/question-answering/how-to/encrypt-data-at-rest.md b/articles/ai-services/language-service/question-answering/how-to/encrypt-data-at-rest.md
@@ -21,7 +21,7 @@ By default, your subscription uses Microsoft-managed encryption keys. There is a
 
 Custom question answering uses CMK support from Azure search, and associates the provided CMK to encrypt the data stored in Azure search index. Please follow the steps listed in [this article](../../../../search/search-security-manage-encryption-keys.md) to configure Key Vault access for the Azure search service.
 
-> [NOTE]
+> [!NOTE]
 > Whenever the CMK is being rotated, make sure there is a period of overlap between the old and new versions of the key where both are enabled and not expired.
 
 > [!IMPORTANT]
diff --git a/articles/app-service/configure-authentication-provider-google.md b/articles/app-service/configure-authentication-provider-google.md
@@ -41,8 +41,8 @@ To complete the procedure in this topic, you must have a Google account that has
 
 1. Click **Add**.
 
-> [Note]
-    > For adding scope: You can define what permissions your application has in the provider's registration portal. The app can request scopes at login time which leverage these permissions.
+> [!NOTE]
+> For adding scope: You can define what permissions your application has in the provider's registration portal. The app can request scopes at login time which leverage these permissions.
 
 You are now ready to use Google for authentication in your app. The provider will be listed on the **Authentication** screen. From there, you can edit or delete this provider configuration.
 
diff --git a/articles/backup/backup-azure-dataprotection-use-rest-api-backup-blobs.md b/articles/backup/backup-azure-dataprotection-use-rest-api-backup-blobs.md
@@ -345,8 +345,8 @@ It returns two responses: 201 (Created) when backup instance is created and the
 
 Once you submit the *PUT* request to create a backup instance, the initial response is 201 (Created) with an Azure-asyncOperation header. 
 
->[Note]
->The request body contains all the backup instance properties.
+> [!NOTE]
+> The request body contains all the backup instance properties.
 
 ```http
 HTTP/1.1 201 Created
diff --git a/articles/backup/backup-blobs-storage-account-ps.md b/articles/backup/backup-blobs-storage-account-ps.md
@@ -33,7 +33,7 @@ See the [prerequisites](./blob-backup-configure-manage.md#before-you-start) and
 
 ## Create a Backup vault
 
-A Backup vault is a storage entity in Azure that holds backup data for various newer workloads that Azure Backup supports, such as Azure Database for PostgreSQL servers, Azure blobs and Azure blobs. Backup vaults make it easy to organize your backup data, while minimizing management overhead. Backup vaults are based on the Azure Resource Manager model of Azure, which provides enhanced capabilities to help secure backup data.
+A Backup vault is a storage entity in Azure that holds backup data for various newer workloads that Azure Backup supports, such as Azure Database for PostgreSQL servers and Azure blobs. Backup vaults make it easy to organize your backup data, while minimizing management overhead. Backup vaults are based on the Azure Resource Manager model of Azure, which provides enhanced capabilities to help secure backup data.
 
 Before creating a backup vault, choose the storage redundancy of the data within the vault. Then proceed to create the backup vault with that storage redundancy and the location. In this article, we will create a backup vault _TestBkpVault_ in region _westus_, under the resource group _testBkpVaultRG_. Use the [New-AzDataProtectionBackupVault](/powershell/module/az.dataprotection/new-azdataprotectionbackupvault) command to create a backup vault.Learn more about [creating a Backup vault](./create-manage-backup-vault.md#create-a-backup-vault).
 
diff --git a/articles/backup/backup-mabs-whats-new-mabs.md b/articles/backup/backup-mabs-whats-new-mabs.md
@@ -16,8 +16,8 @@ Microsoft Azure Backup Server gives you enhanced backup capabilities to protect
 
 Microsoft Azure Backup Server version 4 (MABS V4) Update *Rollup 1 Refresh* includes critical bug fixes and feature enhancements. For information about the bugs fixed and the installation instructions of MABS V4 UR1 Refresh, see [KB article 5033756](https://support.microsoft.com/home/contact?SourceApp=smcivr2).
  
->[!Important]
->MABS V4 UR1 Refresh supersedes MABS V4 UR1 that has the same feature enhancements, but fixes the known issues in MABS V4 UR1. [Learn more](backup-mabs-release-notes-v3.md).
+> [!IMPORTANT]
+> MABS V4 UR1 Refresh supersedes MABS V4 UR1 that has the same feature enhancements, but fixes the known issues in MABS V4 UR1. [Learn more](backup-mabs-release-notes-v3.md).
 
 The following table lists the new features added in MABS V4 UR1:
 
@@ -34,17 +34,17 @@ The following table lists the new features added in MABS V4 UR1:
 
 **Microsoft Azure Backup Server version 4 (MABS V4) Update Rollup 1** includes critical bug fixes and feature enhancements. To view the list of bugs fixed and the installation instructions for MABS V4 UR1, see [KB article 5032421](https://support.microsoft.com/help/5032421/).
 
->[!Important]
->We're temporarily pausing the release of Update Rollup 1 for Microsoft Azure Backup Server V4 due to the known issue - **Hyper-V scheduled backups take a long time to complete because each backup job triggers a consistency check.**
+> [!IMPORTANT]
+> We're temporarily pausing the release of Update Rollup 1 for Microsoft Azure Backup Server V4 due to the known issue - **Hyper-V scheduled backups take a long time to complete because each backup job triggers a consistency check.**
 >
->Error message: The replica of Microsoft Hyper-V RCT on `<Machine Name>` is not consistent with the protected data source. DPM has detected changes in file locations or volume configurations of protected objects since the data source was configured for protection. (ID 30135).
+> Error message: The replica of Microsoft Hyper-V RCT on `<Machine Name>` is not consistent with the protected data source. DPM has detected changes in file locations or volume configurations of protected objects since the data source was configured for protection. (ID 30135).
 >
->Resolution: This will be resolved in the new version planned to be released soon.
+> Resolution: This will be resolved in the new version planned to be released soon.
 >
->- If you haven't installed UR1 for MABS V4 already, wait for the new release.
->- If you have already installed UR1 for MABS V4, this new build will install on top of UR1 for MABS V4 to fix the known issues.
+> - If you haven't installed UR1 for MABS V4 already, wait for the new release.
+> - If you have already installed UR1 for MABS V4, this new build will install on top of UR1 for MABS V4 to fix the known issues.
 >
->For additional information, reach out to Microsoft Support.
+> For additional information, reach out to Microsoft Support.
 
 The following table lists the new features added in MABS V4 UR1:
 
@@ -87,8 +87,8 @@ This update contains the following enhancement to improve the backup time. For m
 - - Item-level recovery errors due to inconsistent file catalog metadata are avoided because *iSCSI mounts* are used.
 - - After the recovery point is mounted, file browsing during item-level recovery is faster for recovery points with many files and folders.
 
->[!Note]
->We recommend that you update your MABS V3 installation to Hotfix for Update Rollup 2 to benefit from the enhancement. Ensure that you also update your MARS Agent to the latest version (2.0.9262.0 or higher).
+> [!NOTE]
+> We recommend that you update your MABS V3 installation to Hotfix for Update Rollup 2 to benefit from the enhancement. Ensure that you also update your MARS Agent to the latest version (2.0.9262.0 or higher).
 
 ## What’s new in MABS v3 UR2?
 
@@ -120,8 +120,8 @@ MABS v3 UR2 supports Offline backup using Azure Data Box. With Microsoft Azure D
 
 Microsoft Azure Backup Server (MABS) version 3 UR1 is the latest update, and includes critical bug fixes and other features and enhancements. To view the list of bugs fixed and the installation instructions for MABS V3 UR1, see KB article [4534062](https://support.microsoft.com/help/4534062).
 
->[!NOTE]
->Support for the 32 bit protection agent is deprecated with MABS v3 UR1. See [32 Bit protection agent deprecation](#32-bit-protection-agent-deprecation).
+> [!NOTE]
+> Support for the 32 bit protection agent is deprecated with MABS v3 UR1. See [32 Bit protection agent deprecation](#32-bit-protection-agent-deprecation).
 
 ### Faster backups with tiered storage using SSDs
 
@@ -138,11 +138,11 @@ With MABS V3 UR1, you can back up the ReFS volumes and workloads deployed on the
 * Exchange: Exchange 2019, 2016.
 * SharePoint: SharePoint 2019, 2016 with latest SP.
 
->[!NOTE]
+> [!NOTE]
 > Backup of Hyper-V VMs stored on an ReFS volume is supported with MABS V3
 
->[IMPORTANT]
->We've identified a few issues with backup of deduplicated ReFS volumes. We're working on fixing these, and will update this section as soon as we have a fix available. Until then, we're removing the support for backup of deduplicated ReFS volumes from MABSv3 UR1.
+> [!IMPORTANT]
+> We've identified a few issues with backup of deduplicated ReFS volumes. We're working on fixing these, and will update this section as soon as we have a fix available. Until then, we're removing the support for backup of deduplicated ReFS volumes from MABSv3 UR1.
 
 ### Azure VMware Solution protection support
 
@@ -165,8 +165,8 @@ With MABS V3 UR1, an additional a layer of authentication is added for critical
 
 MABS v3 UR1 improves the experience of offline backup with Azure Import/Export Service. For more information, see the updated steps [here](./backup-azure-backup-server-import-export.md).
 
->[!NOTE]
->From MABS v3 UR2, MABS can perform offline backup using Azure Data Box. [Learn more](./offline-backup-azure-data-box-dpm-mabs.md).
+> [!NOTE]
+> From MABS v3 UR2, MABS can perform offline backup using Azure Data Box. [Learn more](./offline-backup-azure-data-box-dpm-mabs.md).
 
 ### New cmdlet parameter
 
@@ -176,8 +176,8 @@ MABS V3 UR1 includes a new parameter **[-CheckReplicaFragmentation]**. The new p
 
 With MABS v3 UR1, support for 32-bit protection agent is no longer supported. You won't be able to protect 32-bit workloads after upgrading the MABS v3 server to UR1. Any existing 32-bit protection agents will be in a disabled state and scheduled backups will fail with the **agent is disabled** error. If you want to retain the backup data for these agents, you can stop the protection with the retained data option. Otherwise, the protection agent can be removed.
 
->[!NOTE]
->Review the [updated protection matrix](./backup-mabs-protection-matrix.md) to learn the supported workloads for protection with MABS UR 1.
+> [!NOTE]
+> Review the [updated protection matrix](./backup-mabs-protection-matrix.md) to learn the supported workloads for protection with MABS UR 1.
 
 ## What's new in MABS V3 RTM?
 
diff --git a/articles/cloud-services-extended-support/enable-rdp.md b/articles/cloud-services-extended-support/enable-rdp.md
@@ -22,7 +22,7 @@ The Azure portal uses the remote desktop extension to enable remote desktop even
 3. Choose the roles to enable remote desktop for.
 4. Fill in the required fields for user name, password and expiration.
 
-> [Note] 
+> [!NOTE]
 > The password for remote desktop must be between 8-123 characters long and must satisfy at least 3 of password complexity requirements from the following: 1) Contains an uppercase character 2) Contains a lowercase character 3) Contains a numeric digit 4) Contains a special character 5) Control characters are not allowed
 
    :::image type="content" source="media/remote-desktop-2.png" alt-text="Image shows inputting the information required to connect to remote desktop.":::
diff --git a/articles/cosmos-db/nosql/query/computed-properties.md b/articles/cosmos-db/nosql/query/computed-properties.md
@@ -310,7 +310,7 @@ There are a few considerations for indexing computed properties, including:
 > [!TIP]
 > Every time you update container properties, the old values are overwritten. If you have existing computed properties and want to add new ones, be sure that you add both new and existing computed properties to the collection.
 
->![NOTE]
+> [!NOTE]
 > When the definition of an indexed computed property is modified, it's not automatically reindexed. To index the modified computed property, you'll first need to drop the computed property from the index. Then after the reindexing is completed, add the computed property back to the index policy.
 >
 > If you want to delete a computed property, you'll first need to remove it from the index policy.
diff --git a/articles/cost-management-billing/savings-plan/scope-savings-plan.md b/articles/cost-management-billing/savings-plan/scope-savings-plan.md
@@ -19,12 +19,13 @@ You have the following options to scope a savings plan, depending on your needs:
 
 ## Scope options
 
-- **Single resource group scope** - Applies the savings plan benefit to the eligible resources in the selected resource group only.
-- **Single subscription scope** - Applies the savings plan benefit to the eligible resources in the selected subscription.
+- **Single resource group scope** - Applies the savings plan benefit to eligible resources in the selected resource group only.
+- **Single subscription scope** - Applies the savings plan benefit to eligible resources in the selected subscription.
+- **Management group** - Applies the savings plan benefit to eligible resources within all subscriptions contained in both the management group and billing scope.
 - **Shared scope** - Applies the savings plan benefit to eligible resources within subscriptions that are in the billing context. If a subscription was moved to different billing context, the benefit will no longer be applied to this subscription and will continue to apply to other subscriptions in the billing context.
   - For Enterprise Agreement customers, the billing context is the enrollment. The savings plan shared scope would include multiple Microsoft Entra tenants in an enrollment.
   - For Microsoft Customer Agreement customers, the billing scope is the billing profile. Usage from all billing subscriptions under the billing profile, is eligible to receive benefits for a Shared scoped savings plan.
-- **Management group** - Applies the savings plan benefit to eligible resources in the list of subscriptions that are a part of both the management group and billing scope. To buy a savings plan for a management group, you must have at least read permission on the management group and be a savings plan owner on the billing subscription.
+
 
 ## Scope processing order
 
@@ -33,7 +34,7 @@ While applying savings plan benefits to your usage, Azure processes savings plan
 1. Savings plans with a single resource group scope.
 2. Savings plans with a single subscription scope.
 3. Savings plans scoped to a management group.
-4. Savings plans with a shared scope (multiple subscriptions), described previously.
+4. Savings plans with a shared scope.
 
 You can always update the scope after you buy a savings plan. To do so, go to the savings plan, select **Configuration**, and rescope the savings plan. Rescoping a savings plan isn't a commercial transaction, so your savings plan term isn't changed. For more information about updating the scope, see [Update the scope](manage-savings-plan.md#change-the-savings-plan-scope) after you purchase a savings plan.
 
diff --git a/articles/hpc-cache/hpc-region-recovery.md b/articles/hpc-cache/hpc-region-recovery.md
@@ -38,7 +38,7 @@ To set up a cache that is prepared for possible failover, follow these steps:
    1. Details about client machines, if they are located in the same region as the cache
    1. Mount command for use by cache clients
 
-   > [NOTE]
+   > [!NOTE]
    > Azure HPC Cache can be created programmatically, either through an [Azure Resource Manager template](../azure-resource-manager/templates/overview.md) or by directly accessing its API. Contact the Azure HPC Cache team for details.
 
 ## Failover example
diff --git a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md
@@ -23,7 +23,7 @@ Scale set orchestration modes allow you to have greater control over how virtual
 
 Optimized for large-scale stateless workloads with identical instances.
 
-Virtual Machine Scale Sets with Uniform orchestration use a virtual machine profile or template to scale up to desired capacity. While there is some ability to manage or customize individual virtual machine instances, Uniform uses identical VM instances. Individual Uniform VM instances are exposed via the Virtual Machine Scale Set VM API commands. Individual instances aren't compatible with the standard Azure IaaS VM API commands, Azure management features such as Azure Resource Manager resource tagging RBAC permissions, Azure Backup, or Azure Site Recovery. Uniform orchestration provides fault domain high availability guarantees when configured with fewer than 100 instances. Uniform orchestration is generally available and supports a full range of scale set management and orchestration, including metrics-based autoscaling, instance protection, and automatic OS upgrades.
+Virtual Machine Scale Sets with Uniform orchestration use a virtual machine profile or template to scale up to desired capacity. While there is some ability to manage or customize individual virtual machine instances, Uniform uses identical VM instances. Individual Uniform VM instances are exposed via the Virtual Machine Scale Set VM API commands. Individual instances aren't compatible with the standard Azure IaaS VM API commands, Azure management features such as Azure Resource Manager resource tagging, RBAC permissions, Azure Backup, or Azure Site Recovery. Uniform orchestration provides fault domain high availability guarantees when configured with fewer than 100 instances. Uniform orchestration is generally available and supports a full range of scale set management and orchestration, including metrics-based autoscaling, instance protection, and automatic OS upgrades.
 
 
 ## Scale sets with Flexible orchestration
diff --git a/articles/virtual-machines/disks-metrics.md b/articles/virtual-machines/disks-metrics.md
@@ -45,6 +45,9 @@ The following metrics are available to get insight on VM and disk IO, throughput
 - **Temp Disk Write Bytes/Sec**: The number of bytes that are written in a second from the temporary disk.
 - **Temp Disk Write Operations/Sec**: The number of output operations that are written in a second from the temporary disk.
 
+> [!NOTE]
+> Disk metrics can't log CRUD (Create, Read, Update, Delete) operations inside managed disks.
+
 ## Bursting metrics
 The following metrics help with observability into our [bursting](disk-bursting.md) feature on our premium disks:
 
diff --git a/articles/virtual-machines/extensions/key-vault-linux.md b/articles/virtual-machines/extensions/key-vault-linux.md
@@ -179,7 +179,8 @@ To turn on extension dependency, set the following:
     ...
 }
 ```
-> [Note] Using this feature is not compatible with an ARM template that creates a system assigned identity and updates a Key Vault access policy with that identity. Doing so will result in a deadlock as the vault access policy cannot be updated until all extensions have started. You should instead use a *single user assigned MSI identity* and pre-ACL your vaults with that identity before deploying.
+> [!NOTE]
+> Using this feature is not compatible with an ARM template that creates a system assigned identity and updates a Key Vault access policy with that identity. Doing so will result in a deadlock as the vault access policy cannot be updated until all extensions have started. You should instead use a *single user assigned MSI identity* and pre-ACL your vaults with that identity before deploying.
 
 ## Azure PowerShell deployment
 > [!WARNING]

Original file line number	Diff line number	Diff line change
`@@ -310,7 +310,7 @@ There are a few considerations for indexing computed properties, including:`
`310`	`310`	`> [!TIP]`
`311`	`311`	`> Every time you update container properties, the old values are overwritten. If you have existing computed properties and want to add new ones, be sure that you add both new and existing computed properties to the collection.`
`312`	`312`
`313`		`->![NOTE]`
	`313`	`+> [!NOTE]`
`314`	`314`	`> When the definition of an indexed computed property is modified, it's not automatically reindexed. To index the modified computed property, you'll first need to drop the computed property from the index. Then after the reindexing is completed, add the computed property back to the index policy.`
`315`	`315`	`>`
`316`	`316`	`> If you want to delete a computed property, you'll first need to remove it from the index policy.`