Azure Storage is actively working on features that would address this concern.
We have shipped a public preview of integration with AAD DS: https://azure.microsoft.com/blog/azure-active-directory-integration-for-smb-access-now-in-public-preview/
What we have in preview is a first step along a much larger roadmap for integration with AAD/AD for authentication and authorization. As the blog post says, this initial preview is really about Windows cloud VM access to the Azure file share with an AAD identity. Future refreshes to this feature will add non-Windows (Linux, macOS, etc) support, and the ability to mount the Azure file shares on-premises with your AAD identity. You can learn more about this in our Ignite session as well (at around 22:00): https://www.youtube.com/watch?v=GMzh2M66E9o
We’ll keep you updated on our progress. In the meantime, don’t hesitate to continue posting feedback on this feature below.
Program Manager, Azure Files
Good feedback. Let’s see if it picks up more votes.
332 votesunder review · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
The status of this item has been moved back to Under Review. We initially planned to move to VHDX support as part of our support for HyperV Gen2 VMs, but we ended up using the VHD format for Gen2 VMs as well. Some aspects of the Azure Infrastructure do not cleanly support VHDX OS or data disks. So this feature is dependent on some of these internal services being updated which is an ongoing process.
68 votesJesper Berth commented
Having the same issue, need to specify timeout value