One of the most crucial decisions in a storage design process for Hyper-V is the question of whether to stick with the traditional SAN model or hop on the wagon of Microsoft's SOFS Architecture. Both solutions can do the main job, that is, providing IOPS for VMs, without any problems. Having done many projects using both architectures, the following is some real-world guidance I use for storage design.

The first and most important design principle: do not use nonredundant systems in production for Hyper-V clusters—no local hard drives, no single hardware SMB3-Shares, and no single point of failures on your storage design. If you cannot fulfill these requirements, don't plan for High Availability on Hyper-V. Plan for disaster recovery instead. Uncluster the Hyper-V Servers and replicate the VMs between the nodes in a small setup or between smaller clusters in a bigger environment via Hyper-V Replica. Having said that, let's focus on the decision to make.

Technically, it's possible...