Reconfiguring article.

Author: roygara

articles/storage/elastic-san/elastic-san-configure-service-endpoints.md

@@ -139,29 +139,23 @@ You can manage virtual network rules for volume groups through the Azure portal,
 ### [PowerShell](#tab/azure-powershell)
 
 - List virtual network rules.
+- Enable service endpoint for Azure Storage on an existing virtual network and subnet.
+- Add a network rule for a virtual network and subnet.
+
+    > [!TIP]
+    > To add a network rule for a subnet in a virtual network belonging to another Microsoft Entra tenant, use a fully qualified **VirtualNetworkResourceId** parameter in the form "/subscriptions/subscription-ID/resourceGroups/resourceGroup-Name/providers/Microsoft.Network/virtualNetworks/vNet-name/subnets/subnet-name".
 
     ```azurepowershell
     $Rules = Get-AzElasticSanVolumeGroup -ResourceGroupName $RgName -ElasticSanName $sanName -Name $volGroupName
     $Rules.NetworkAclsVirtualNetworkRule
-    ```
-
-- Enable service endpoint for Azure Storage on an existing virtual network and subnet.
 
-    ```azurepowershell
     Get-AzVirtualNetwork -ResourceGroupName "myresourcegroup" -Name "myvnet" | Set-AzVirtualNetworkSubnetConfig -Name "mysubnet" -AddressPrefix "10.0.0.0/24" -ServiceEndpoint "Microsoft.Storage.Global" | Set-AzVirtualNetwork
-    ```
-
-- Add a network rule for a virtual network and subnet.
 
-    ```azurepowershell
     $rule = New-AzElasticSanVirtualNetworkRuleObject -VirtualNetworkResourceId $Subnet.Id -Action Allow
     
     Add-AzElasticSanVolumeGroupNetworkRule -ResourceGroupName $RgName -ElasticSanName $EsanName -VolumeGroupName $EsanVgName -NetworkAclsVirtualNetworkRule $rule
     ```
 
-    > [!TIP]
-    > To add a network rule for a subnet in a virtual network belonging to another Microsoft Entra tenant, use a fully qualified **VirtualNetworkResourceId** parameter in the form "/subscriptions/subscription-ID/resourceGroups/resourceGroup-Name/providers/Microsoft.Network/virtualNetworks/vNet-name/subnets/subnet-name".
-
 - Remove a virtual network rule.
 
     ```azurepowershell
@@ -177,17 +171,7 @@ You can manage virtual network rules for volume groups through the Azure portal,
 ### [Azure CLI](#tab/azure-cli)
 
 - List information from a particular volume group, including their virtual network rules.
-
-    ```azurecli
-    az elastic-san volume-group show -e $sanName -g $RgName -n $volumeGroupName
-    ```
-
 - Enable service endpoint for Azure Storage on an existing virtual network and subnet.
-
-    ```azurecli
-    az network vnet subnet update --resource-group "myresourcegroup" --vnet-name "myvnet" --name "mysubnet" --service-endpoints "Microsoft.Storage.Global"
-    ```
-
 - Add a network rule for a virtual network and subnet.
 
     > [!TIP]
@@ -196,13 +180,18 @@ You can manage virtual network rules for volume groups through the Azure portal,
     > You can use the **subscription** parameter to retrieve the subnet ID for a virtual network belonging to another Microsoft Entra tenant.
 
     ```azurecli
-    # First, get the current length of the list of virtual networks. This is needed to ensure you append a new network instead of replacing existing ones.
+    az elastic-san volume-group show -e $sanName -g $RgName -n $volumeGroupName
+
+    az network vnet subnet update --resource-group "myresourcegroup" --vnet-name "myvnet" --name "mysubnet" --service-endpoints "Microsoft.Storage.Global"
+
+    # First, get the current length of the list of virtual networks to ensure you append a new network instead of replacing existing ones.
     virtualNetworkListLength = az elastic-san volume-group show -e $sanName -n $volumeGroupName -g $RgName --query 'length(networkAcls.virtualNetworkRules)'
     
     az elastic-san volume-group update -e $sanName -g $RgName --name $volumeGroupName --network-acls virtual-network-rules[$virtualNetworkListLength] "{virtualNetworkRules:[{id:/subscriptions/subscriptionID/resourceGroups/RGName/providers/Microsoft.Network/virtualNetworks/$VnetName/subnets/default, action:Allow}]}"
     ```
 
-- Remove a network rule. The following command removes the first network rule, modify it to remove the network rule you'd like.
+
+If you need to, you can remove network rules. As an example, the following command removes the first network rule, modify it to remove the network rule you'd like.
     
     ```azurecli
     az elastic-san volume-group update -e $sanName -g $RgName -n $volumeGroupName --network-acls virtual-network-rules[1]=null
@@ -231,21 +220,15 @@ You can manage virtual network rules for volume groups through the Azure portal,
 ### [PowerShell](#tab/azure-powershell)
 
 - List virtual network rules.
+- Enable service endpoint for Azure Storage on an existing virtual network and subnet.
+- Add a network rule for a virtual network and subnet.
 
     ```azurepowershell
     $Rules = Get-AzElasticSanVolumeGroup -ResourceGroupName $RgName -ElasticSanName $sanName -Name $volGroupName
     $Rules.NetworkAclsVirtualNetworkRule
-    ```
 
-- Enable service endpoint for Azure Storage on an existing virtual network and subnet.
-
-    ```azurepowershell
     Get-AzVirtualNetwork -ResourceGroupName "myresourcegroup" -Name "myvnet" | Set-AzVirtualNetworkSubnetConfig -Name "mysubnet" -AddressPrefix "10.0.0.0/24" -ServiceEndpoint "Microsoft.Storage.Global" | Set-AzVirtualNetwork
-    ```
 
-- Add a network rule for a virtual network and subnet.
-
-    ```azurepowershell
     $rule = New-AzElasticSanVirtualNetworkRuleObject -VirtualNetworkResourceId $Subnet.Id -Action Allow
     
     Add-AzElasticSanVolumeGroupNetworkRule -ResourceGroupName $RgName -ElasticSanName $EsanName -VolumeGroupName $EsanVgName -NetworkAclsVirtualNetworkRule $rule
@@ -269,17 +252,7 @@ You can manage virtual network rules for volume groups through the Azure portal,
 ### [Azure CLI](#tab/azure-cli)
 
 - List information from a particular volume group, including their virtual network rules.
-
-    ```azurecli
-    az elastic-san volume-group show -e $sanName -g $RgName -n $volumeGroupName
-    ```
-
 - Enable service endpoint for Azure Storage on an existing virtual network and subnet.
-
-    ```azurecli
-    az network vnet subnet update --resource-group "myresourcegroup" --vnet-name "myvnet" --name "mysubnet" --service-endpoints "Microsoft.Storage.Global"
-    ```
-
 - Add a network rule for a virtual network and subnet.
 
     > [!TIP]
@@ -288,6 +261,10 @@ You can manage virtual network rules for volume groups through the Azure portal,
     > You can use the **subscription** parameter to retrieve the subnet ID for a virtual network belonging to another Microsoft Entra tenant.
 
     ```azurecli
+    az elastic-san volume-group show -e $sanName -g $RgName -n $volumeGroupName
+
+    az network vnet subnet update --resource-group "myresourcegroup" --vnet-name "myvnet" --name "mysubnet" --service-endpoints "Microsoft.Storage.Global"
+
     # First, get the current length of the list of virtual networks. This is needed to ensure you append a new network instead of replacing existing ones.
     virtualNetworkListLength = az elastic-san volume-group show -e $sanName -n $volumeGroupName -g $RgName --query 'length(networkAcls.virtualNetworkRules)'
     
@@ -308,7 +285,7 @@ You can manage virtual network rules for volume groups through the Azure portal,
 After you have enabled the desired endpoints and granted access in your network rules, you're ready to configure your clients to connect to the appropriate Elastic SAN volumes.
 
 > [!NOTE]
-> If a connection between a virtual machine (VM) and an Elastic SAN volume is lost, the connection will retry for 90 seconds until terminating. Losing a connection to an Elastic SAN volume won't cause the VM to restart.
+> If a connection between a virtual machine (VM) and an Elastic SAN volume is lost, the connection retries for 90 seconds until terminating. Losing a connection to an Elastic SAN volume won't cause the VM to restart.
 
 ## Next steps
 

articles/storage/elastic-san/elastic-san-connect-windows.md

@@ -70,17 +70,12 @@ Use the following script to create your connections. To execute it, collect or d
 and other volume names that you might require
 - 32: Number of sessions to each volume
 
-Copy the script from [here](https://github.com/Azure-Samples/azure-elastic-san/blob/main/PSH%20(Windows)%20Multi-Session%20Connect%20Scripts/ElasticSanDocScripts0523/connect.ps1) and save it as a .ps1 file, for example, connect.ps1. Then execute it with the required parameters. The following is an example of how to run the script: 
+Copy the script from [here](https://github.com/Azure-Samples/azure-elastic-san/blob/main/PSH%20(Windows)%20Multi-Session%20Connect%20Scripts/ElasticSanDocScripts0523/connect.ps1) and save it as a .ps1 file, for example, connect.ps1.
 
-```bash
-./connect.ps1 $rgname $esanname $vgname $vol1,$vol2,$vol3 32
-```
-
-Verify the number of sessions your volume has with either `iscsicli SessionList` or `mpclaim -s -d`
 
 ### Set session number
 
-You need to use 32 sessions to each target volume to achieve its maximum IOPS and/or throughput limits. Windows iSCSI initiator has a limit of maximum 256 sessions. If you need to connect more than 8 volumes to a Windows client, reduce the number of sessions to each volume. 
+Before you run the script, determine how many sessions your volume needs. To be able to reach a volume's highest IOPS and throughput capacities, you'll need 32 sessions. But, because Windows iSCSI initatior has a maximum of 256 sessions, you may need to use less than 32 sessions if you're connecting more than eight volumes to a Windows client.
 
 > [!NOTE]
 > Use the `-NumSession` parameter to set the number of sessions. The parameter accepts values from 1 to 32, and has a default value of 32.
@@ -100,6 +95,8 @@ You need to use 32 sessions to each target volume to achieve its maximum IOPS an
   -NumSession “<value>”
 ```
 
+Verify the number of sessions your volume has with either `iscsicli SessionList` or `mpclaim -s -d`
+
 ## Next steps
 
 [Configure Elastic SAN networking](elastic-san-networking.md)