When using Failover Clustering with heaps of virtual machines distributed across hosts, you might face a scenario where many VMs need to be live-migrated to other hosts, or when they are started at the same time. In both examples, all VMs will be moved to another host, with no priority. That can cause services failures when, for example, a service starts before the necessary requirement services. To make it simpler, let's say you have VMs with Exchange, SQL, and SharePoint Server, and all of them start before the Active Directory VMs during a failover. All these services require Active Directory to be online first so that the authentication and authorization can happen. In this example, all services will fail and you will need to restart them to guarantee they will start after the Active Directory VM. With VM Priority, you can specify a priority for every VM, allowing them to be moved or started in order, based on their priority.

This...