Update virtual-machines-disks-incremental-snapshots-restrictions.md

snapshot + resize limitation

Author: AdamZLi

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

@@ -28,6 +28,7 @@ Incremental snapshots of Premium SSD v2 and Ultra Disks have the following extra
 - 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 snapshot status](#check-snapshot-status) for details.
 - Taking increment snapshots of a Premium SSD v2 or an Ultra disk while the CompletionPercent property of the disk hasn't reached 100 isn't supported.
+- When you increase the size of a Premium SSD v2 or an Ultra disk, any incremental snapshots that are underoing background copy will fail. 
 - When you attach a Premium SSD v2 or Ultra disk created from snapshot to a running Virtual Machine while CompletionPercent property hasn't reached 100, the disk suffers performance impact. Specifically, if the disk has a 4k sector size, it may experience slower read. If the disk has a 512e sector size, it may experience slower read and write. To track the progress of this background copy process, see the the check disk status section of either the Azure [PowerShell sample](../articles/virtual-machines/scripts/virtual-machines-powershell-sample-create-managed-disk-from-snapshot.md#performance-impact---background-copy-process) or the [Azure CLI](../articles/virtual-machines/scripts/create-managed-disk-from-snapshot.md#performance-impact---background-copy-process).
 
 > [!NOTE]