This is an expected behavior.
Because virtual machine startup is restricted on a dedicated failover host,
it conflicts with the vSAN File Service, which requires the startup of an Agent VM on each host in the cluster.
This configuration is not supported.
Please Select an admission control policy other than a dedicated failover host.