Oh, how I know that. Because MY Hyper-V clusters are designed to be able to boot up, their AD IS ready when the cluster needs it. Tested and proven for EACH installation. That includes Server 2008 (with and without R2) clusters which are way less tolerant than 2016+ HV clustering regard of unreachable AD.
The funny part: Too many VMWare guys blame it on Microsoft, but VMWare suffers a similar problem. Though when it comes to VMWare, those guys read the documentation and best practices. But they don't give M$ the same amount of attention and then blame.... MS.
The funny part 2: The VMWare guys design their cluster auth to work without requiring external auth or the "main customer AD being available". Doing the same for Hyper-V is always a discussion - which I always win, but those endless discussions.
Biting the hand that feeds IT
