Merge pull request #291898 from roygara/esanSnapPivot

Incorporating snapshot guidance

Author: prmerger-automator[bot]

articles/storage/elastic-san/elastic-san-snapshots.md

@@ -5,7 +5,7 @@ author: roygara
 ms.service: azure-elastic-san-storage
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ms.topic: conceptual
-ms.date: 12/03/2024
+ms.date: 12/12/2024
 ms.author: rogarana
 ---
 
@@ -18,10 +18,16 @@ You can take up to 200 snapshots per volume at a rate of seven snapshots every f
 
 ## Limitations
 
-- If a volume is larger than 4 TiB, export of a volume snapshot to a disk snapshot is not supported.
+- If a volume is larger than 4 TiB, you can't export that volume's snapshots to disk snapshots.
 
 ## General guidance
 
+You should use Elastic SAN volume snapshots when you want to restore volumes quickly, like when you have dev/test workloads. Volumes created from volume snapshots are available instantly for use, while the rehydration happens in the background. Volume snapshots shouldn't be considered when hardening your backups.
+
+You should use managed disk snapshots when you either want to create a managed disk from your Elastic SAN volume, or if you want to keep a long term backup of your Elastic SAN volumes. Managed disk snapshots are useful when you require durable checkpoints or version control for your Elastic SAN volumes, and you don't need to restore a volume backup instantly. Managed disk snapshots aren't ideal for scenarios where you require quick restoration, it takes time to create Elastic SAN volumes from managed disk snapshots.
+
+### Take a stable snapshot
+
 You can take a snapshot anytime, but if you’re taking snapshots while the VM is running, keep these things in mind:
 
 When the VM is running, data is still being streamed to the volumes. As a result, snapshots of a running VM might contain partial operations that were in flight.