Merge pull request #209347 from MicrosoftDocs/repo_sync_working_branch

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

Author: v-alje

articles/active-directory/reports-monitoring/reference-azure-ad-sla-performance.md

@@ -53,13 +53,13 @@ For each month, we truncate the SLA attainment at three places after the decimal
 
 | Month     | 2021    | 2022    |
 | ---       | ---     | ---     |
-| January   |         | 99.999% |
+| January   |         | 99.998% |
 | February  | 99.999% | 99.999% |
-| March     | 99.568% | 99.999% |
+| March     | 99.568% | 99.998% |
 | April     | 99.999% | 99.999% |
 | May       | 99.999% | 99.999% |
 | June      | 99.999% | 99.999% |
-| July      | 99.999% |         |
+| July      | 99.999% | 99.999% |
 | August    | 99.999% |         |
 | September | 99.999% |         |
 | October   | 99.999% |         |

articles/automanage/arm-deploy.md

@@ -28,7 +28,7 @@ The following ARM template will onboard your specified machine onto Azure Automa
         "machineName": {
             "type": "String"
         },
-        "configurationProfile": {
+        "configurationProfileName": {
             "type": "String"
         }
     },
@@ -38,7 +38,7 @@ The following ARM template will onboard your specified machine onto Azure Automa
             "apiVersion": "2021-04-30-preview",
             "name": "[concat(parameters('machineName'), '/Microsoft.Automanage/default')]",
             "properties": {
-                "configurationProfile": "[parameters('configurationProfile')]"
+                "configurationProfile": "[parameters('configurationProfileName')]"
             }
         }
     ]
@@ -51,11 +51,12 @@ This ARM template will create a configuration profile assignment for your specif
 The `configurationProfile` value can be one of the following values:
 * "/providers/Microsoft.Automanage/bestPractices/AzureBestPracticesProduction"
 * "/providers/Microsoft.Automanage/bestPractices/AzureBestPracticesDevTest"
+* "/subscriptions/[sub ID]/resourceGroups/resourceGroupName/providers/Microsoft.Automanage/configurationProfiles/customProfileName (for custom profiles)
 
 Follow these steps to deploy the ARM template:
 1. Save this ARM template as `azuredeploy.json`
 1. Run this ARM template deployment with `az deployment group create --resource-group myResourceGroup --template-file azuredeploy.json`
-1. Provide the values for machineName, and configurationProfileAssignment when prompted
+1. Provide the values for machineName, and configurationProfileName when prompted
 1. You're ready to deploy
 
 As with any ARM template, it's possible to factor out the parameters into a separate `azuredeploy.parameters.json` file and use that as an argument when deploying.

articles/event-hubs/event-hubs-premium-overview.md

@@ -14,7 +14,7 @@ It replicates events to three replicas, distributed across Azure availability zo
 In addition to these storage-related features and all capabilities and protocol support of the standard tier, the isolation model of the premium tier enables features like [dynamic partition scale-up](dynamically-add-partitions.md). You also get far more generous [quota allocations](event-hubs-quotas.md). Event Hubs Capture is included at no extra cost.
 
 > [!NOTE]
-> Event Hubs Premium supports TLS 1.2 or greater . 
+> Event Hubs Premium supports TLS 1.2 or greater. 
 
 ## Why premium?
 The premium tier offers three compelling benefits for customers who require better isolation in a multitenant environment with low latency and high throughput data ingestion needs.
@@ -41,7 +41,7 @@ Therefore, the premium tier is often a more cost effective option for event stre
 
 For the extra robustness gained by availability-zone support, the minimal deployment scale for the dedicated tier is 8 capacity units (CU), but you'll have availability zone support in the premium tier from the first PU in all availability zone regions. 
 
-You can purchase 1, 2, 4, 8 and 16 processing units for each namespace. As the premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle as it's' in the standard tier, but depends on the work you ask Event Hubs to do, similar to the dedicated tier. The effective ingest and stream throughput per PU will depend on various factors, including:
+You can purchase 1, 2, 4, 8 and 16 processing units for each namespace. As the premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle as it is in the standard tier, but depends on the work you ask Event Hubs to do, similar to the dedicated tier. The effective ingest and stream throughput per PU will depend on various factors, including:
 
 * Number of producers and consumers
 * Payload size 

articles/postgresql/flexible-server/overview.md

@@ -100,22 +100,24 @@ One advantage of running your workload in Azure is global reach. The flexible se
 | Canada East | :heavy_check_mark: | :x: | :heavy_check_mark: |
 | Central India | :heavy_check_mark: | :heavy_check_mark: ** | :heavy_check_mark: |
 | Central US | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
+| China East 3 | :heavy_check_mark: | :x: | :x:|
+| China North 3 | :heavy_check_mark: | :x: | :x:|
 | East Asia | :heavy_check_mark: | :heavy_check_mark: ** | :heavy_check_mark: |
 | East US | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | East US 2 | :heavy_check_mark: | :x: $ | :heavy_check_mark: |
 | France Central | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
-| France South | :heavy_check_mark: | :x: | :x: |
+| France South | :heavy_check_mark: | :x: | :heavy_check_mark: |
 | Germany West Central | :x: $$ | :x: $ | :x: |
 | Japan East | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | Japan West | :heavy_check_mark: | :x: | :heavy_check_mark: |
 | Jio India West | :heavy_check_mark: (v3 only)| :x: | :x: |
-| Korea Central | :heavy_check_mark: | :heavy_check_mark: ** | :x: |
-| Korea South | :heavy_check_mark: | :x: | :x: |
+| Korea Central | :heavy_check_mark: | :heavy_check_mark: ** | :heavy_check_mark: |
+| Korea South | :heavy_check_mark: | :x: | :heavy_check_mark: |
 | North Central US | :heavy_check_mark: | :x: | :heavy_check_mark: |
 | North Europe | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | Norway East | :heavy_check_mark: | :x: | :x: |
 | Qatar Central | :heavy_check_mark: | :x: | :x: |
-| South Africa North | :heavy_check_mark: | :heavy_check_mark: ** | :x: |
+| South Africa North | :heavy_check_mark: | :heavy_check_mark: | :x: |
 | South Central US | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | South India | :x: $$ | :x: | :heavy_check_mark: |
 | Southeast Asia | :heavy_check_mark: | :x: $  | :heavy_check_mark: |
@@ -127,10 +129,10 @@ One advantage of running your workload in Azure is global reach. The flexible se
 | US Gov Virginia | :heavy_check_mark: | :heavy_check_mark: | :x: |
 | UK South | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | UK West | :heavy_check_mark: | :x: | :heavy_check_mark: |
-| West Central US | :heavy_check_mark: | :x: | :x: |
+| West Central US | :heavy_check_mark: | :x: | :heavy_check_mark: |
 | West Europe | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | West US | :heavy_check_mark: | :x: | :heavy_check_mark: |
-| West US 2 | :x: $$ | :x: $ | :x: |
+| West US 2 | :x: $$ | :x: $ | :heavy_check_mark:|
 | West US 3 | :heavy_check_mark: | :heavy_check_mark: ** | :x: |
 
 $ New Zone-redundant high availability deployments are temporarily blocked in these regions. Already provisioned HA servers are fully supported. 

articles/virtual-machines/azure-compute-gallery.md

@@ -17,7 +17,7 @@ ms.reviewer: cynthn
 
 An Azure Compute Gallery helps you build structure and organization around your Azure resources, like images and [applications](vm-applications.md). An Azure Compute Gallery provides:
 
-- Global replication.
+- Global replication.<sup>1</sup>
 - Versioning and grouping of resources for easier management.
 - Highly available resources with Zone Redundant Storage (ZRS) accounts in regions that support Availability Zones. ZRS offers better resilience against zonal failures.
 - Premium storage support (Premium_LRS).
@@ -26,6 +26,7 @@ An Azure Compute Gallery helps you build structure and organization around your
 
 With a gallery, you can share your resources to everyone, or limit sharing to different users, service principals, or AD groups within your organization. Resources can be replicated to multiple regions, for quicker scaling of your deployments.
 
+<sup>1</sup> The Azure Compute Gallery service is not a global resource. For disaster recovery scenarios, it is a best practice is to have at least two galleries, in different regions.
 
 ## Images 
 

includes/virtual-machines-managed-disks-description-customer-managed-keys.md

@@ -24,7 +24,10 @@ Managed Disks and the key vault or managed HSM must be in the same region and in
 
 You must grant access to managed disks in your Key Vault or managed HSM to use your keys for encrypting and decrypting the DEK. This allows you full control of your data and keys. You can disable your keys or revoke access to managed disks at any time. You can also audit the encryption key usage with Azure Key Vault monitoring to ensure that only managed disks or other trusted Azure services are accessing your keys.
 
-When you disable or delete your key, any VMs with disks using that key will automatically shut down. After this, the VMs will not be usable unless the key is enabled again or you assign a new key.	
+When a key is either disabled, deleted, or expired, any VMs with disks using that key will automatically shut down. After this, the VMs will not be usable unless the key is enabled again or you assign a new key.
+
+> [!NOTE]
+> It is generally expected that Disk I/O (read or write operations) will start to fail 1 hour after a key is either disabled, deleted, or expired.
 
 The following diagram shows how managed disks use Azure Active Directory and Azure Key Vault to make requests using the customer-managed key:
 
@@ -46,3 +49,6 @@ To revoke access to customer-managed keys, see [Azure Key Vault PowerShell](/pow
 #### Automatic key rotation of customer-managed keys
 
 You can choose to enable automatic key rotation to the latest key version. A disk references a key via its disk encryption set. When you enable automatic rotation for a disk encryption set, the system will automatically update all managed disks, snapshots, and images referencing the disk encryption set to use the new version of the key within one hour. To learn how to enable customer-managed keys with automatic key rotation, see [Set up an Azure Key Vault and DiskEncryptionSet with automatic key rotation](../articles/virtual-machines/windows/disks-enable-customer-managed-keys-powershell.md#set-up-an-azure-key-vault-and-diskencryptionset-optionally-with-automatic-key-rotation).
+
+> [!NOTE]
+> Virtual Machines will not be rebooted during automatic key rotation.