Merge pull request #262653 from rvandenbedem/patch-1

Update create-placement-policy.md

Author: prmerger-automator[bot]

articles/azure-vmware/create-placement-policy.md

@@ -3,7 +3,7 @@ title: Create placement policy
 description: Learn how to create a placement policy in Azure VMware Solution to control the placement of virtual machines (VMs) on hosts within a cluster through the Azure portal.
 ms.topic: how-to 
 ms.service: azure-vmware
-ms.date: 12/07/2023
+ms.date: 1/8/2024
 ms.custom: engagement-fy23
 
 #Customer intent: As an Azure service administrator, I want to control the placement of virtual machines on hosts within a cluster in my private cloud. 
@@ -14,10 +14,7 @@ ms.custom: engagement-fy23
 
 In Azure VMware Solution, clusters in a private cloud are a managed resource. As a result, the CloudAdmin role can't make certain changes to the cluster from the vSphere Client, including the management of Distributed Resource Scheduler (DRS) rules.
 
-The placement policy feature is available in all Azure VMware Solution regions. 
-Placement policies let you control the placement of virtual machines (VMs) on hosts within a cluster through the Azure portal. 
-When you create a placement policy, it includes a DRS rule in the specified vSphere cluster. 
-It also includes other logic for interoperability with Azure VMware Solution operations.
+The placement policy feature is available in all Azure VMware Solution regions. Placement policies let you control the placement of virtual machines (VMs) on hosts within a cluster through the Azure portal. When you create a placement policy, it includes a DRS rule in the specified vSphere cluster. It also includes other logic for interoperability with Azure VMware Solution operations.
 
 A placement policy has at least five required components: 
 
@@ -31,12 +28,10 @@ A placement policy has at least five required components:
 
 - **Virtual machine** - Defines the VMs and hosts for the policy. Depending on the type of rule you create, your policy might require you to specify some number of VMs and hosts. For more information, see [Placement policy types](#placement-policy-types).
 
-
 ## Prerequisite
 
 You must have _Contributor_ level access to the private cloud to manage placement policies.
 
-
 ## Placement policy types
 
 ### VM-VM policies
@@ -49,7 +44,6 @@ The assignment of hosts isn't required or permitted for this policy type.
 
 - **VM-VM Anti-Affinity** policies instruct DRS to try keeping the specified VMs apart from each other on separate hosts. It's useful in availability scenarios where a problem with one host doesn't affect multiple VMs within the same policy.
 
-
 ### VM-Host policies
 
 **VM-Host** policies specify if selected VMs can run on selected hosts.  To avoid interference with platform-managed operations such as host maintenance mode and host replacement, **VM-Host** policies in Azure VMware Solution are always preferential (also known as "should" rules). Accordingly, **VM-Host** policies [may not be honored in certain scenarios](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-793013E2-0976-43B7-9A00-340FA76859D0.html). For more information, see [Monitor the operation of a policy](#monitor-the-operation-of-a-policy).
@@ -62,24 +56,20 @@ In addition to choosing a name and cluster for the policy, a **VM-Host** policy
 
 - **VM-Host Anti-Affinity** policies instruct DRS to try running the specified VMs on hosts other than the ones defined.
 
-
 ## Considerations
 
-### Cluster scale in
+### Cluster scale-in
 
 Azure VMware Solution attempts to prevent certain DRS rule violations from occurring when performing cluster scale-in operations.
 
 You can't remove the last host from a VM-Host policy. However, if you need to remove the last host from the policy, you can remediate it by adding another host to the policy before removing the host from the cluster. Alternatively, you can delete the placement policy before removing the host.
 
 You can't have a VM-VM Anti Affinity policy with more VMs than the number of hosts in a cluster. If removing a host results in fewer hosts in the cluster than VMs, you receive an error preventing the operation. You can remediate it by first removing VMs from the rule and then removing the host from the cluster.
 
-
 ### Rule conflicts
 
 If DRS rule conflicts are detected when you create a VM-VM policy, it results in that policy being created in a disabled state following standard [VMware DRS Rule behavior](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-69C738B6-5FC8-4189-9CB5-DD90A5A05979.html). For more information on viewing rule conflicts, see [Monitor the operation of a policy](#monitor-the-operation-of-a-policy).
 
-
-
 ## Create a placement policy
 
 There's no defined limit to the number of policies that you create. However, the more placement constraints you create, the more challenging it is for vSphere DRS to effectively move virtual machines within the cluster and provide the resources needed by the workloads.      
@@ -92,23 +82,19 @@ Make sure to review the requirements for the [policy type](#placement-policy-typ
    >You may also select the Cluster from the Placement Policy overview pane and then select **Create**.
    >
 
-
-
 1. Provide a descriptive name, select the policy type, and select the cluster where the policy is created. Then select **Enabled**.
 
    >[!WARNING]
    >If you disable the policy, then the policy and the underlying DRS rule are created, but the policy actions are ignored until you enable the policy. 
 
-
 1. If you selected **VM-Host affinity** or **VM-Host anti-affinity** as the type, select **+ Add hosts** and the hosts to include in the policy. You can select multiple hosts.
 
    >[!NOTE]
    >The select hosts pane shows how many VM-Host policies are associated with the host and the total number of VMs contained in those associated policies.
    >
 
 1. Select **+ Add virtual machine** and the VMs to include in the policy. You can select multiple VMs.
-
-   
+ 
    >[!NOTE]
    >The select hosts pane shows how many VM-Host policies are associated with the host and the total number of VMs contained in those associated policies. 
 
@@ -122,7 +108,6 @@ Make sure to review the requirements for the [policy type](#placement-policy-typ
 
 :::image type="content" source="media/placement-policies/create-placement-policy-8.png" alt-text="Screenshot showing the placement policy as Enabled after it gets created." lightbox="media/placement-policies/create-placement-policy-8.png":::
 
-
 ## Edit a placement policy
 
 You can change the state of a policy, add a new resource, or unassign an existing resource.
@@ -144,7 +129,6 @@ You can change the state of a policy to **Enabled** or **Disabled**.
 
 1.	Review the changes and select **Update policy**. If you want to make changes, select **Back: Basics**.
 
-
 ### Update the resources in a policy
 
 You can add new resources, such as a VM or a host, to a policy or remove existing ones. 
@@ -159,7 +143,6 @@ To add a new resource, select **Edit virtual machine** or **Edit host**, select
 
 1. Review the changes and select **Update policy**.  If you want to make changes, select **Back : Basics**.
 
-
 ## Delete a policy
 
 You can delete a placement policy and its corresponding DRS rule. 
@@ -198,12 +181,11 @@ Manual vMotion of the VM and automatic initial placement of the VM continues to
 ### Are placement policies the same as DRS affinity rules?
 Yes, and no. While vSphere DRS implements the current set of policies, we simplified the experience. Modifying VM groups and Host groups are a cumbersome operation, especially as hosts are ephemeral in nature and could be replaced in a cloud environment. As hosts are replaced in the vSphere inventory in an on-premises environment, the vSphere admin must modify the host group to ensure that the desired VM-Host placement constraints remain in effect. Placement policies in Azure VMware Solution update the Host groups when a host is rotated or changed. Similarly, if you scale in a cluster, the Host Group is automatically updated, as applicable. The automatic update eliminates the overhead of managing the Host Groups for the customer.
 
+### As this is an existing functionality available in vCenter Server, why can't I use it directly? 
 
-### As this is an existing functionality available in vCenter, why can't I use it directly? 
+Azure VMware Solution provides a private cloud in Azure. In this managed VMware solution infrastructure, Microsoft manages the clusters, hosts, datastores, and distributed virtual switches in the private cloud. At the same time, the tenant is responsible for managing the workloads deployed on the private cloud. As a result, the tenant administering the private cloud doesn't have the [same set of privileges](concepts-identity.md) as available to the VMware solution administrator in an on-premises deployment. 
 
-Azure VMware Solution provides a VMware private cloud in Azure. In this managed VMware infrastructure, Microsoft manages the clusters, hosts, datastores, and distributed virtual switches in the private cloud. At the same time, the tenant is responsible for managing the workloads deployed on the private cloud. As a result, the tenant administering the private cloud doesn't have the [same set of privileges](concepts-identity.md) as available to the VMware administrator in an on-premises deployment. 
-
-Further, the lack of the desired granularity in the vSphere privileges presents some challenges when managing the placement of the workloads on the private cloud. For example, vSphere DRS rules commonly used on-premises to define affinity and anti-affinity rules can't be used as-is in an Azure VMware Solution environment, as some of those rules can block day-to-day operation the private cloud. Placement Policies provides a way to define those rules using the Azure VMware Solution portal, thereby circumventing the need to use DRS rules. Coupled with a simplified experience, Placement Policies ensure the rules don't impact the day-to-day infrastructure maintenance and operation activities. 
+Further, the lack of the desired granularity in the vSphere privileges presents some challenges when managing the placement of the workloads on the private cloud. For example, vSphere DRS rules commonly used on-premises to define affinity and anti-affinity rules can't be used as-is in an Azure VMware Solution environment, as some of those rules can block day-to-day operation the private cloud. Placement Policies provides a way to define those rules using the Azure portal, thereby circumventing the need to use DRS rules. Coupled with a simplified experience, Placement Policies ensure the rules don't impact the day-to-day infrastructure maintenance and operation activities. 
 
 ###  What is the difference between the VM-Host affinity policy and Restrict VM movement?
 
@@ -216,4 +198,3 @@ The VM-Host **MUST** rules aren't supported because they block maintenance opera
 VM-Host **SHOULD** rules are preferential rules, where vSphere DRS tries to accommodate the rules to the extent possible. Occasionally, vSphere DRS may vMotion VMs subjected to the VM-Host **SHOULD** rules to ensure that the workloads get the resources they need. It's a standard vSphere DRS behavior, and the Placement policies feature doesn't change the underlying vSphere DRS behavior.
 
 If you create conflicting rules, those conflicts can show up on the vCenter Server, and the newly defined rules might not take effect. It's a standard vSphere DRS behavior, the logs for which can be observed in the vCenter Server.
-