Update configure-storage-policy.md

Author: LHL407

articles/azure-vmware/configure-storage-policy.md

@@ -12,11 +12,11 @@ ms.custom: engagement-fy23
 
 # Configure a VMware vSAN storage policy
 
-VMware vSAN storage policies define storage requirements for your virtual machines (VMs). These policies guarantee that your VMs have the required level of service because they determine how storage is allocated to the VM. Each VM deployed to a vSAN datastore is assigned at least one VM storage policy.
+VMware vSAN storage policies define storage requirements for your virtual machines (VMs). These policies guarantee that your VMs have the required level of service because they determine how storage is allocated to the VM. Each VM that's deployed to a vSAN datastore is assigned at least one VM storage policy.
 
-You can assign a VM storage policy in an initial deployment of a VM or when you do other VM operations, such as cloning or migrating. Post-deployment cloudadmin users or equivalent roles can't change the default storage policy for a VM. However, **VM storage policy** per disk changes is permitted.
+You can assign a VM storage policy during a VM's initial deployment or during other VM operations, such as cloning or migrating. Post-deployment users with the **cloudadmin** or equivalent roles can't change the default storage policy for a VM. However, VM storage policy per disk changes is permitted.
 
-Authorized users can use the `Run` command to change the default or existing VM storage policy to an available policy for a VM post-deployment. There are no changes made on the disk-level VM storage policy. You can always change the disk-level VM storage policy according to your requirements.
+Authorized users can use the `Run` command to change the default or existing VM storage policy to an available policy for a VM after deployment. There are no changes made on the disk-level VM storage policy. You can always change the disk-level VM storage policy according to your requirements.
 
 Run commands are executed one at a time in the order submitted.
 
@@ -25,9 +25,9 @@ In this article learn how to:
 > [!div class="checklist"]
 > * List all storage policies
 > * Set the storage policy for a VM
-> * Specify default storage policy for a cluster
-> * Create storage policy
-> * Remove storage policy
+> * Specify the default storage policy for a cluster
+> * Create a storage policy
+> * Remove a storage policy
 
 ## Prerequisites
 
@@ -48,7 +48,7 @@ Run the `Get-StoragePolicy` cmdlet to list the vSAN-based storage policies that
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
    >[!NOTE]
-   >If you need access to the Azure US Government portal, go to https://portal.azure.us/
+   >If you need access to the Azure US Government portal, go to https://portal.azure.us/.
 
 1. Select **Run command** > **Packages** > **Get-StoragePolicies**.
 
@@ -62,7 +62,7 @@ Run the `Get-StoragePolicy` cmdlet to list the vSAN-based storage policies that
    | --- | --- |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *Get-StoragePolicies-Exec1*. |
-   | **Timeout**  |  The period after which a cmdlet exits if taking too long to finish.  |
+   | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |
 
 1. Check **Notifications** to see the progress.
 
@@ -83,7 +83,7 @@ Run the `Set-VMStoragePolicy` cmdlet to modify vSAN-based storage policies on a
    | **StoragePolicyName** | Name of the storage policy that you want to set. For example, *RAID1 FTT-1*. |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *changeVMStoragePolicy*.  |
-   | **Timeout**  |  The period after which a cmdlet exits if taking too long to finish.  |
+   | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |
 
 1. Check **Notifications** to see the progress.
 
@@ -104,7 +104,7 @@ Run the `Set-LocationStoragePolicy` cmdlet to modify vSAN-based storage policies
    | **StoragePolicyName** | Name of the storage policy to set. For example, *RAID1 FTT-1*. |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *changeVMStoragePolicy*.  |
-   | **Timeout**  |  The period after which a cmdlet exits if taking too long to finish.  |
+   | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |
 
 1. Check **Notifications** to see the progress.
 
@@ -122,46 +122,46 @@ Run the `Set-ClusterDefaultStoragePolicy` cmdlet to specify a default storage po
    | **StoragePolicyName** | Name of the storage policy to set. For example, *RAID1 FTT-1*. |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *Set-ClusterDefaultStoragePolicy-Exec1*.  |
-   | **Timeout**  |  The period after which a cmdlet exits if taking too long to finish.  |
+   | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |
 
 1. Check **Notifications** to see the progress.
 
 > [!NOTE]
 > Changing the default cluster policy affects only new VMs. Existing VMs retain the policy they're currently configured/deployed with.
 
-## Create custom Azure VMware Solution storage policy
+## Create a custom Azure VMware Solution storage policy
 
-Run the `New-AVSStoragePolicy` cmdlet to create or overwrite an existing policy. This function creates a new or overwrites an existing vSphere storage policy. Non vSAN-based, vSAN-only, VMEncryption-only, Tag-only based or any combination of these policy types are supported.
+Run the `New-AVSStoragePolicy` cmdlet to create or overwrite an existing policy. This function creates a new, or overwrites an existing, vSphere storage policy. Non vSAN-based, vSAN-only, VMEncryption-only, Tag-only based or any combination of these policy types are supported.
 
 Keep the following information in mind:
 
 * You can't modify existing Azure VMware Solution default storage policies.
 * Certain options enabled in storage policies produce warnings to associated risks.
-* Out of compliance: When you modify existing storage policies, existing associated vSAN objects like VMs, VMDK files, and ISO files appear to be "out of compliance." This means that existing objects are running against premodified policy settings. To update to match modified policy settings, reapply the storage policy to objects.
+* Out of compliance: When you modify existing storage policies, existing associated vSAN objects like VMs, VMDK files, and ISO files appear to be "out of compliance." This means that existing objects are running against premodified policy settings. To update to match the modified policy settings, reapply the storage policy to objects.
 
 1. Select **Run command** > **Packages** > **New-AVSStoragePolicy**.
 
 1. Provide the required values or change the default values, and then select **Run**.
 
    | **Field** | **Value** |
    | --- | --- |
-   | **Overwrite** | Overwrite existing storage policy. <br>- The default is  `$false`. <br>- Passing overwrite `true` provided overwrites an existing policy exactly as defined. <br>- Those values not passed are removed or set to default values. |
+   | **Overwrite** | Overwrite existing storage policy. <br>- The default value is  `$false`. <br>- When you pass overwrite `true` provided overwrites an existing policy exactly as defined. <br>- Those values not passed are removed or set to default values. |
    | **NotTags** | Match to datastores that do *not* have these tags. <br>- Tags are case sensitive. <br>- Comma separate multiple tags. <br>- Example: `Tag1,Tag 2,Tag_3` |
    | **Tags** | Match to datastores that do have these tags.  <br>- Tags are case sensitive. <br>- Comma separate multiple tags. <br>- Example: `Tag1,Tag 2,Tag_3` |
-   | **vSANForceProvisioning** | Force provisioning for the policy. <br>- Default is `$false`.<br>- Valid values are `$true` or `$false` <br>- Warning: vSAN force-provisioned objects aren't covered under Microsoft's Service Level Agreement (SLA). Data loss and vSAN instability can occur. <br>- Recommended value is `$false`. |
-   | **vSANChecksumDisabled** | Enable or disable checksum for the policy. <br>- Default is `$false`. <br>- Valid values are `$true` or `$false`. <br>- Warning: Disabling checksum can lead to data loss and/or corruption. <br>- Recommended value is `$false`. |
-   | **vSANCacheReservation** | Percentage of cache reservation for the policy. <br>- Default is `0`. <br>- Valid values are `0` to `100`.|
-   | **vSANIOLimit** | Sets limit on allowed input/output (IO). <br>- Default is unset. <br>- Valid values are `0` to `2147483647`. <br>- Input/output operations per second (IOPS) limit for the policy. |
-   | **vSANDiskStripesPerObject** | The number of hard disk drives (HDDs) across which each replica of a storage object is striped. <br>- Default is `1`. Valid values are `1` to `12`. <br>- A value higher than `1` might result in better performance (for example, when flash read cache misses need to get serviced from HDD), but also results in a higher use of system resources. |
-   | **vSANObjectSpaceReservation** | Object reservation. <br>- Default is `0`.  <br>- Valid values are `0` to `100`. <br>- `0` = thin provision <br>- `100` = thick provision|
-   | **VMEncryption** | Sets VM encryption. <br>- Default is `None`.  <br>- Valid values are `None`, `Pre-IO`, `Post-IO`. <br>- Pre-IO allows virtual IO (VAIO) filtering solutions to capture data before VM encryption. <br>- Post-IO allows VAIO filtering solutions to capture data after VM encryption. |
-   | **vSANFailuresToTolerate** | Number of vSAN hosts' failures to tolerate. <br>- Default is `R1FTT1`. <br>- Valid values are `None`, `R1FTT1`, `R1FTT2`, `R1FTT3`, `R5FTT1`, `R6FTT2`, `R1FTT3` <br>- `None` = No data redundancy<br>- `R1FTT1` = 1 failure - `RAID-1` (mirroring)<br>- `R1FTT2` = 2 failures - `RAID-1` (Mirroring)<br>- `R1FTT3` = 3 failures - `RAID-1` (mirroring)<br>- `R5FTT1` = 1 failure - `RAID-5` (erasure coding),<br>- `R6FTT2` = 2 failures - `RAID-6` (erasure coding) <br>- No data redundancy options aren't covered under Microsoft's SLA.|
-   | **vSANSiteDisasterTolerance** | Valid only for stretch clusters. <br>-  Default is `None`. <br>- Valid values are `None`, `Dual`, `Preferred`, `Secondary`, `NoneStretch`  <br>- `None` = No site redundancy. Recommended option for nonstretch clusters. Not recommended for stretch clusters)  <br>- `Dual` = Dual site redundancy. Recommended option for stretch clusters.  <br>- `Preferred` = No site redundancy - keep data on Preferred (stretched cluster)  <br>- `Secondary` = No site redundancy -  Keep data on Secondary Site (stretched cluster)  <br>- `NoneStretch` = No site redundancy - Not Recommended (https://kb.vmware.com/s/article/88358)|
+   | **vSANForceProvisioning** | Force provisioning for the policy. <br>- The default value is `$false`.<br>- Valid values are `$true` or `$false` <br>- Warning: vSAN force-provisioned objects aren't covered under Microsoft's Service Level Agreement (SLA). Data loss and vSAN instability can occur. <br>- Recommended value is `$false`. |
+   | **vSANChecksumDisabled** | Enable or disable checksum for the policy. <br>- The default value is `$false`. <br>- Valid values are `$true` or `$false`. <br>- Warning: Disabling checksum can lead to data loss and/or corruption. <br>- Recommended value is `$false`. |
+   | **vSANCacheReservation** | Percentage of cache reservation for the policy. <br>- The default value is `0`. <br>- Valid values are `0` to `100`.|
+   | **vSANIOLimit** | Sets limit on allowed input/output (IO). <br>- The default value is unset. <br>- Valid values are `0` to `2147483647`. <br>- Input/output operations per second (IOPS) limit for the policy. |
+   | **vSANDiskStripesPerObject** | The number of hard disk drives (HDDs) across which each replica of a storage object is striped. <br>- The default value is `1`. Valid values are `1` to `12`. <br>- A value higher than `1` might result in better performance (for example, when flash read cache misses need to get serviced from HDD), but also results in a higher use of system resources. |
+   | **vSANObjectSpaceReservation** | Object reservation. <br>- The default value is `0`.  <br>- Valid values are `0` to `100`. <br>- `0` = thin provision <br>- `100` = thick provision|
+   | **VMEncryption** | Sets VM encryption. <br>- The default value is `None`.  <br>- Valid values are `None`, `Pre-IO`, `Post-IO`. <br>- Pre-IO allows virtual IO (VAIO) filtering solutions to capture data before VM encryption. <br>- Post-IO allows VAIO filtering solutions to capture data after VM encryption. |
+   | **vSANFailuresToTolerate** | Number of vSAN hosts' failures to tolerate. <br>- The default value is `R1FTT1`. <br>- Valid values are `None`, `R1FTT1`, `R1FTT2`, `R1FTT3`, `R5FTT1`, `R6FTT2`, `R1FTT3` <br>- `None` = No data redundancy<br>- `R1FTT1` = 1 failure - `RAID-1` (mirroring)<br>- `R1FTT2` = 2 failures - `RAID-1` (Mirroring)<br>- `R1FTT3` = 3 failures - `RAID-1` (mirroring)<br>- `R5FTT1` = 1 failure - `RAID-5` (erasure coding),<br>- `R6FTT2` = 2 failures - `RAID-6` (erasure coding) <br>- No data redundancy options aren't covered under Microsoft's SLA.|
+   | **vSANSiteDisasterTolerance** | Valid only for stretch clusters. <br>-  The default value is `None`. <br>- Valid values are `None`, `Dual`, `Preferred`, `Secondary`, `NoneStretch`  <br>- `None` = No site redundancy. Recommended option for nonstretch clusters. Not recommended for stretch clusters)  <br>- `Dual` = Dual site redundancy. Recommended option for stretch clusters.  <br>- `Preferred` = No site redundancy - keep data on Preferred (stretched cluster)  <br>- `Secondary` = No site redundancy -  Keep data on Secondary Site (stretched cluster)  <br>- `NoneStretch` = No site redundancy - Not Recommended (https://kb.vmware.com/s/article/88358)|
    | **Description** | Description of the storage policy you're creating, free form text. |
    | **Name** | Name of the storage policy to set. For example, *RAID1 FTT-1*. |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *New-AVSStoragePolicy-Exec1*.  |
-   | **Timeout**  |  The period after which a cmdlet exits if taking too long to finish.  |
+   | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |
 
 1. Check **Notifications** to see the progress.
 
@@ -178,7 +178,7 @@ Run the `Remove-AVSStoragePolicy` cmdlet to specify the default storage policy f
    | **Name** | Name of the storage Policy. Wildcards aren't supported and are stripped. |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *Remove-AVSStoragePolicy-Exec1*.  |
-   | **Timeout**  |  The period after which a cmdlet exits if taking too long to finish.  |
+   | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |
 
 1. Check **Notifications** to see the progress.