I admit confusion over the point in the article: "This prevents more than one Failover Cluster Instance from using the same drive assignments."

My reference here is: "AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using Failover Cluster Instances and Availability Groups " @ https://msdn.microsoft.com/en-us/library/jj215886.aspx

On page 7, in the "Asymmetric Storage" section: "By enabling this functionality, you can combine the shared storage solution (FCI) with the non-shared storage solution (availability groups), in a single HA + DR solution. Consequently, this enhancement also enables you to use identical drive letters for shared disk resources across data centers."

In the following section, "Instance Naming and File Path": "Each FCI has its own shared storage, which is not accessible by nodes in the other data center, and which should use identical drive letters for the disks, as well as identical file paths for database files and transaction log files in both of the FCIs. Identical file path and drive letters are not an absolute requirement, but if file paths differ, you will need to do a manual RESTORE WITH MOVE when you restore the replica databases on the secondary."

Am I missing the point in some other fashion? Also, the MSDN article is not so clear that the asymmetric enhancement also works for an FCI + Standalone solution, though other notes on the web do say as much.