Merge pull request #277220 from roygara/cmkPV2

Updating limitations.

Author: prmerger-automator[bot]

includes/disks-prem-v2-limitations.md

@@ -4,7 +4,7 @@
  author: roygara
  ms.service: azure-disk-storage
  ms.topic: include
- ms.date: 03/04/2024
+ ms.date: 06/04/2024
  ms.author: rogarana
 ms.custom:
   - include file
@@ -13,6 +13,7 @@ ms.custom:
 - Premium SSD v2 disks can't be used as an OS disk.
 - Currently, Premium SSD v2 disks are only available in [select regions](/azure/virtual-machines/disks-deploy-premium-v2#regional-availability).
 - Currently, Premium SSD v2 disks can only be attached to zonal VMs.
+- Currently, Azure Government and Azure China don't support [customer-managed keys](../articles/virtual-machines/disk-encryption.md#customer-managed-keys) for Premium SSD v2 disks.
 - Encryption at host is supported on Premium SSD v2 disks with some limitations and in select regions. For more information, see [Encryption at host](/azure/virtual-machines/disk-encryption#restrictions-1).
 - Azure Disk Encryption (guest VM encryption via Bitlocker/DM-Crypt) isn't supported for VMs with Premium SSD v2 disks. We recommend you to use encryption at rest with platform-managed or customer-managed keys, which is supported for Premium SSD v2. 
 - Currently, Premium SSD v2 disks can't be attached to VMs in Availability Sets. 

includes/managed-disks-ultra-disks-GA-scope-and-limitations.md

@@ -4,7 +4,7 @@ description: include file
 author: roygara
 ms.service: azure-disk-storage
 ms.topic: include
-ms.date: 05/23/2024
+ms.date: 06/04/2024
 ms.author: rogarana
 ms.custom: include file
 ---
@@ -15,6 +15,7 @@ The following list contains Ultra Disk's limitations:
 - Ultra Disks don't support availability sets.
 - The size of an Ultra Disk can't be expanded without either deallocating the VM or detaching the Ultra Disk.
 - Existing disks currently can't change their type to an Ultra Disk. They must be [migrated](../articles/virtual-machines/disks-convert-types.md#migrate-to-premium-ssd-v2-or-ultra-disk).
+- Currently, Azure Government and Azure China don't support [customer-managed keys](../articles/virtual-machines/disk-encryption.md#customer-managed-keys) for Ultra disks.
 - Azure Disk Encryption isn't supported for VMs with Ultra Disks. Instead, you should use encryption at rest with platform-managed or customer-managed keys.
 - Azure Site Recovery isn't supported for VMs with Ultra Disks.
 - Ultra Disks don't support disk caching.

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

@@ -4,7 +4,7 @@
  author: roygara
  ms.service: azure-disk-storage
  ms.topic: include
- ms.date: 02/28/2024
+ ms.date: 06/04/2024
  ms.author: rogarana
  ms.custom: include file
 ---
@@ -15,6 +15,7 @@
 - For Ultra Disks and Premium SSD v2 disks only:
     - Snapshots created from disks that are encrypted with server-side encryption and customer-managed keys must be encrypted with the same customer-managed keys.
     - User-assigned managed identities aren't supported for Ultra Disks and Premium SSD v2 disks encrypted with customer-managed keys.
+    - Not currently supported in Azure Government or Azure China.
 - Most resources related to your customer-managed keys (disk encryption sets, VMs, disks, and snapshots) must be in the same subscription and region.
     - Azure Key Vaults may be used from a different subscription but must be in the same region as your disk encryption set. As a preview, you can use Azure Key Vaults from [different Microsoft Entra tenants](../articles/virtual-machines/disks-cross-tenant-customer-managed-keys.md).
 - Disks encrypted with customer-managed keys can only move to another resource group if the VM they are attached to is deallocated.