Merge pull request #249167 from adarshv98/adarshv98-patch-1-2

Elastic SAN Documentation Updates on PR, PE, and Delete

Author: v-regandowner

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

@@ -20,12 +20,11 @@ This article explains how to deploy and configure an elastic storage area networ
     - Once you've installed the latest version, run `az extension add -n elastic-san` to install the extension for Elastic SAN.
 
 
-## Register for the preview
+## Preview Registration
 Register your subscription with Microsoft.ElasticSAN resource provider and the preview feature using the following command:
 
 # [Portal](#tab/azure-portal)
-
-Use either the Azure PowerShell module or the Azure CLI to register your subscription for the preview.
+If you are using the portal, follow the steps in either the Azure PowerShell module or the Azure CLI to register your subscription for the preview.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -55,6 +54,8 @@ az provider show --namespace Microsoft.ElasticSan
 az feature show --name ElasticSanPreviewAccess --namespace Microsoft.ElasticSan
 ```
 ---
+> [!IMPORTANT]
+> If you are using PowerShell or CLI, you don't need to run this command. Skip this step and proceed to deploy an Elastic SAN.
 
 ## Limitations
 
@@ -212,7 +213,7 @@ The following sample command creates a single volume in the Elastic SAN volume g
 > [!IMPORTANT]
 > The volume name is part of your volume's iSCSI Qualified Name, and can't be changed once created.
 
-Use the same variables you set for , then run the following script:
+Use the same variables, then run the following script:
 
 ```azurepowershell
 # Create the volume, this command only creates one.

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

@@ -11,7 +11,7 @@ ms.custom: ignite-2022, devx-track-azurecli, devx-track-azurepowershell
 
 # Delete an Elastic SAN Preview
 
-To delete an elastic storage area network (SAN), you first need to disconnect every volume in your Elastic SAN Preview from any connected hosts.
+Your Elastic storage area network (SAN) resources can be deleted at different resource levels. This article covers the overall deletion process, starting from disconnecting iSCSI connections to volumes, deleting the volumes themselves, deleting a volume group, and deleting an elastic SAN itself. Before you delete your elastic SAN, make sure it's not being used in any running workloads.
 
 ## Disconnect volumes from clients
 
@@ -62,9 +62,10 @@ iscsiadm --mode node --target **yourStorageTargetIQN** --portal **yourStorageTar
 
 ## Delete a SAN
 
-When your SAN has no active connections to any clients, you may delete it using the Azure portal or Azure PowerShell module.
+When your SAN has no active connections to any clients, you may delete it using the Azure portal or Azure PowerShell module. If you delete a SAN or a volume group, the corresponding child resources will be deleted along with it. The delete commands for each of the resource levels are below.
 
-First, delete each volume.
+
+To delete volumes, run the following commands.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -79,7 +80,7 @@ az elastic-san volume delete -e $sanName -g $resourceGroupName -v $volumeGroupNa
 ```
 ---
 
-Then, delete each volume group.
+To delete volume groups, run the following commands.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -94,7 +95,7 @@ az elastic-san volume-group delete -e $sanName -g $resourceGroupName -n $volumeG
 ```
 ---
 
-Finally, delete the Elastic SAN itself.
+To delete the Elastic SAN itself, run the following commands.
 
 # [PowerShell](#tab/azure-powershell)
 

articles/storage/elastic-san/elastic-san-networking-concepts.md

@@ -40,7 +40,7 @@ After configuring endpoints, you can configure network rules to further control
 ## Private endpoints
 
 > [!IMPORTANT]
-> Private endpoints for Elastic SAN Preview are currently only supported in France Central.
+> Private endpoints for Elastic SAN Preview are supported in all regions that Elastic SAN is available in if you deploy with [locally-redundant storage (LRS)](elastic-san-planning.md#redundancy) as their redundancy option. Private endpoints aren't currently supported Elastic SANs deployed using [zone-redundant storage (ZRS)](elastic-san-planning.md#redundancy) as their redundancy option.
 
 Azure [Private Link](../../private-link/private-link-overview.md) enables you to access an Elastic SAN volume group securely over a [private endpoint](../../private-link/private-endpoint-overview.md) from a virtual network subnet. Traffic between your virtual network and the service traverses the Microsoft backbone network, eliminating the risk of exposing your service to the public internet. An Elastic SAN private endpoint uses a set of IP addresses from the subnet address space for each volume group. The maximum number used per endpoint is 20.
 

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

@@ -99,7 +99,7 @@ az network vnet subnet update --resource-group $RgName --vnet-name $VnetName --n
 ### Configure a private endpoint
 
 > [!IMPORTANT]
-> - Private endpoints for Elastic SAN Preview are currently only supported in France Central.
+> - Private endpoints for Elastic SAN Preview are supported in all regions that Elastic SAN is available in if you deploy with [locally-redundant storage (LRS)](elastic-san-planning.md#redundancy) as their redundancy option. Private endpoints aren't currently supported Elastic SANs deployed using [zone-redundant storage (ZRS)](elastic-san-planning.md#redundancy) as their redundancy option.
 >
 > - Before you can create a private endpoint connection to a volume group, it must contain at least one volume.
 

articles/storage/elastic-san/elastic-san-shared-volumes.md

@@ -26,7 +26,7 @@ See [Support for Azure Storage features](elastic-san-introduction.md#support-for
 
 ## Regional availability
 
-Currently, only Elastic SAN volumes in France Central can be used as shared volumes.
+All regions that Elastic SAN is available in can use shared volumes.
 
 ## How it works
 
@@ -99,4 +99,4 @@ You also need to provide a persistent-reservation-key when using:
 - PR_REGISTER_KEY 
 - PR_PREEMPT_RESERVATION 
 - PR_CLEAR_RESERVATION 
-- PR_RELEASE-RESERVATION.
+- PR_RELEASE-RESERVATION.