Merge pull request #227192 from roygara/premSnap

Staging premium SSD v2 snapshot draft.

Author: v-dirichards

articles/virtual-machines/disks-deploy-premium-v2.md

@@ -3,7 +3,7 @@ title: Deploy a Premium SSD v2 managed disk
 description: Learn how to deploy a Premium SSD v2.
 author: roygara
 ms.author: rogarana
-ms.date: 02/08/2023
+ms.date: 02/22/2023
 ms.topic: how-to
 ms.service: storage
 ms.subservice: disks

articles/virtual-machines/disks-incremental-snapshots.md

@@ -4,7 +4,7 @@ description: Learn about incremental snapshots for managed disks, including how
 author: roygara
 ms.service: storage
 ms.topic: how-to
-ms.date: 01/25/2023
+ms.date: 02/22/2023
 ms.author: rogarana
 ms.subservice: disks
 ms.custom: devx-track-azurepowershell, ignite-fall-2021, devx-track-azurecli, ignite-2022, references_regions
@@ -87,7 +87,7 @@ New-AzSnapshot -ResourceGroupName $resourceGroupName -SnapshotName $snapshotName
 ```
 
 > [!IMPORTANT]
-> After taking a snapshot of an Ultra Disk, you must wait for the snapshot to complete before you can use it.  See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
+> After taking a snapshot of a Premium SSD v2 or an Ultra Disk, you must wait for the snapshot to complete before you can use it.  See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
 
 You can identify incremental snapshots from the same disk with the `SourceResourceId` and the `SourceUniqueId` properties of snapshots. `SourceResourceId` is the Azure Resource Manager resource ID of the parent disk. `SourceUniqueId` is the value inherited from the `UniqueId` property of the disk. If you delete a disk and then create a new disk with the same name, the value of the `UniqueId` property changes.
 
@@ -114,7 +114,7 @@ $incrementalSnapshots
 [!INCLUDE [virtual-machines-disks-incremental-snapshots-portal](../../includes/virtual-machines-disks-incremental-snapshots-portal.md)]
 
 > [!IMPORTANT]
-> After taking a snapshot of an Ultra Disk, you must wait for the snapshot to complete before you can use it.  See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
+> After taking a snapshot of a Premium SSD v2 or an Ultra Disk, you must wait for the snapshot to complete before you can use it.  See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
 
 # [Resource Manager Template](#tab/azure-resource-manager)
 
@@ -152,13 +152,13 @@ You can also use Azure Resource Manager templates to create an incremental snaps
 }
 ```
 > [!IMPORTANT]
-> After taking a snapshot of an Ultra Disk, you must wait for the snapshot to complete before you can use it.  See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
+> After taking a snapshot of a Premium SSD v2 or an Ultra Disk, you must wait for the snapshot to complete before you can use it.  See the [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) section for details.
 
 ---
 
 ## Check status of snapshots or disks
 
-Incremental snapshots of Ultra Disks (preview) can't be used to create new disks until the background process copying the data into the snapshot has completed. Similarly, Ultra Disks created from incremental snapshots can't be attached to a VM until the background process copying the data into the disk has completed.
+Incremental snapshots of Premium SSD v2 or Ultra Disks (preview) can't be used to create new disks until the background process copying the data into the snapshot has completed. Similarly, Premium SSD v2 or Ultra Disks created from incremental snapshots can't be attached to a VM until the background process copying the data into the disk has completed.
 
 You can use either the [CLI](#cli) or [PowerShell](#powershell) sections to check the status of the background copy from a disk to a snapshot and you can use the [Check disk creation status](#check-disk-creation-status) section to check the status of a background copy from a snapshot to a disk.
 
@@ -240,7 +240,7 @@ $targetSnapshot.CompletionPercent
 
 ### Check disk creation status
 
-When creating a disk from an Ultra Disk snapshot, you must wait for the background copy process to complete before you can attach it. Currently, you must use the Azure CLI to check the progress of the copy process.
+When creating a disk from either a Premium SSD v2 or an Ultra Disk snapshot, you must wait for the background copy process to complete before you can attach it. Currently, you must use the Azure CLI to check the progress of the copy process.
 
 The following script gives you the status of an individual disk's copy process. The value of `completionPercent` must be 100 before the disk can be attached.
 
@@ -256,9 +256,9 @@ az disk show -n $diskName -g $resourceGroupName --query [completionPercent] -o t
 
 ## Check sector size
 
-Snapshots with a 4096 logical sector size can only be used to create Ultra Disks. They can't be used to create other disk types. Snapshots of disks with 4096 logical sector size are stored as VHDX, whereas snapshots of disks with 512 logical sector size are stored as VHD. Snapshots inherit the logical sector size from the parent disk.
+Snapshots with a 4096 logical sector size can only be used to create Premium SSD v2 or Ultra Disks. They can't be used to create other disk types. Snapshots of disks with 4096 logical sector size are stored as VHDX, whereas snapshots of disks with 512 logical sector size are stored as VHD. Snapshots inherit the logical sector size from the parent disk.
 
-To determine whether or your Ultra Disk snapshot is a VHDX or a VHD, get the `LogicalSectorSize` property of the snapshot. 
+To determine whether or your Premium SSD v2 or Ultra Disk snapshot is a VHDX or a VHD, get the `LogicalSectorSize` property of the snapshot. 
 
 The following command displays the logical sector size of a snapshot:
 

includes/disks-prem-v2-limitations.md

@@ -5,14 +5,14 @@
  author: roygara
  ms.service: storage
  ms.topic: include
- ms.date: 07/15/2022
+ ms.date: 02/13/2023
  ms.author: rogarana
  ms.custom: include file
 ---
 - Premium SSD v2 disks can't be used as an OS disk.
 - Currently, Premium SSD v2 disks can only be attached to zonal VMs.
-- Currently, taking snapshots aren't supported, and you can't create a Premium SSD v2 from the snapshot of another disk type.
-- Currently, encryption at host is not supported for Premium SSD v2 disks. You can still attach Premium SSD v2 disks to VMs where you have enabled encryption at host for disk types.
+- A Premium SSD v2 disk can't be created from the snapshot of a different disk type.
+- Currently, encryption at host isn't supported for Premium SSD v2 disks. You can still attach Premium SSD v2 disks to VMs where you have enabled encryption at host for disk types.
 - 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.
 - Azure Backup and Azure Site Recovery aren't supported for VMs with Premium SSD v2 disks. 

includes/virtual-machines-disks-incremental-snapshots-restrictions.md

@@ -5,12 +5,11 @@
  author: roygara
  ms.service: virtual-machines
  ms.topic: include
- ms.date: 01/25/2023
+ ms.date: 02/17/2023
  ms.author: rogarana
  ms.custom: include file
 ---
 
-- Not currently available for Premium SSD v2 managed disks.
 - Incremental snapshots currently can't be moved between subscriptions.
 - You can currently only generate SAS URIs of up to five snapshots of a particular snapshot family at any given time.
 - You can't create an incremental snapshot for a particular disk outside of that disk's subscription.
@@ -19,13 +18,13 @@
 - A total of 500 incremental snapshots can be created for a single disk.
 - You can't get the changes between snapshots taken before and after you changed the size of the parent disk across 4 TB boundary. For example, You took an incremental snapshot `snapshot-a` when the size of a disk was 2 TB. Now you increased the size of the disk to 6 TB and then took another incremental snapshot `snapshot-b`. You can't get the changes between `snapshot-a` and `snapshot-b`. You have to download the full copy of `snapshot-b` created after the resize. Subsequently, you can get the changes between `snapshot-b` and snapshots created after `snapshot-b`.
 
-### Incremental snapshots of Ultra Disks (preview)
+### Incremental snapshots of Premium SSD v2 and Ultra Disks (preview)
 
-Incremental snapshots of Ultra Disks have the following extra restrictions:
+Incremental snapshots of Premium SSD v2 and Ultra Disks have the following extra restrictions:
 
 - You must request and receive access to the preview from the following link: [https://aka.ms/UltraPremiumv2SnapshotPreview](https://aka.ms/UltraPremiumv2SnapshotPreview)
 - Currently only available in Sweden Central and US West 3.
 - Snapshots with a 512 logical sector size are stored as VHD, and can be used to create any disk type. Snapshots with a 4096 logical sector size are stored as VHDX and can only be used to create Ultra Disks, they can't be used to create other disk types. To determine which sector size your snapshot is, see [check sector size](#check-sector-size).
-- When an incremental snapshot of an Ultra Disk is created, a background copy process for that disk is started. While a background copy is ongoing, you can have up to three total snapshots pending. The process must complete before any more snapshots of that disk can be created.
-- Incremental snapshots of an Ultra disk can't be used immediately after they're created. The background copy must complete before you can create a disk from the snapshot. See [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) for details.
-- Disks created from an incremental snapshot of an Ultra Disk can't be immediately attached to a VM once it's created. The background copy must complete before it can be attached. See [Check disk creation status](#check-disk-creation-status) for details.
+- When an incremental snapshot of either a Premium SSD v2 or an Ultra Disk is created, a background copy process for that disk is started. While a background copy is ongoing, you can have up to three total snapshots pending. The process must complete before any more snapshots of that disk can be created.
+- Incremental snapshots of a Premium SSD v2 or an Ultra disk can't be used immediately after they're created. The background copy must complete before you can create a disk from the snapshot. See [Check status of snapshots or disks](#check-status-of-snapshots-or-disks) for details.
+- Disks created from an incremental snapshot of a Premium SSD v2 or an Ultra Disk can't be immediately attached to a VM once it's created. The background copy must complete before it can be attached. See [Check disk creation status](#check-disk-creation-status) for details.

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

@@ -5,15 +5,15 @@
  author: roygara
  ms.service: virtual-machines
  ms.topic: include
- ms.date: 02/21/2023
+ ms.date: 02/22/2023
  ms.author: rogarana
  ms.custom: include file
 ---
 - If this feature is enabled for a disk with incremental snapshots, it can't be disabled on that disk or its snapshots.
     To work around this, copy all the data to an entirely different managed disk that isn't using customer-managed keys. You can do that with either the [Azure CLI](../articles/virtual-machines/linux/disks-upload-vhd-to-managed-disk-cli.md#copy-a-managed-disk) or the [Azure PowerShell module](../articles/virtual-machines/windows/disks-upload-vhd-to-managed-disk-powershell.md#copy-a-managed-disk).
 - Only [software and HSM RSA keys](../articles/key-vault/keys/about-keys.md) of sizes 2,048-bit, 3,072-bit and 4,096-bit are supported, no other keys or sizes.
     - [HSM](../articles/key-vault/keys/hsm-protected-keys.md) keys require the **premium** tier of Azure Key vaults.
-- For Ultra 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.
+- 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.
 - 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 Azure Active Directory 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.