VMM is not aware of site-aware clustering feature introduced in Hyper-V 2016 which creates huge discrepancy when DO kicks in and also during deployment of new VM using VM/Service Templates. This needs to be inherited in SCVMM for better placements and VM deployment experience in Hyper-V cluster.

https://techcommunity.microsoft.com/t5/failover-clustering/site-aware-failover-clusters-in-windows-server-2016/ba-p/372060