Automatically mount an Azure file share to a Windows clients using GPO
Momently its not possible to map a azure file storage share via GPO, because the two fields for username and password are greyed out.
Thank you for your feedback! As we work to get Azure Files to parity with Windows File Server, we absolutely agree this functionality is required. For now, I’m leaving this item open so we can collect feedback on it – please vote for it to help us prioritize it!
Alessandro Cardoso commented
You can use Group Policy Preference to mount an Azure Files that is Domain Joined.
It shows in Windows Explorer or you can access it from Command Prompt, but I noticed that some Services like IIS do not see the Driver, unless you run a net use ... command locally
Hi Team, this is a must for many organisations with a large user base and is something I am working on as part of an Architecture Review and the inclusion of Azure File Shares.
Jefferson Areche commented
I have registered the storage account in AD On Premise to use authentication via Azure AD, with this the authentication to access Azure Files is done through the network user of the computer (desktop computer joined to the domain). With that, it is only necessary to create the unit mapping GPO (without specifying username and password)
Kevin Roberts commented
Please could you update with progress?
Is there any process on this requirement??
" we absolutely agree this functionality is required"...february 2018
September 2019...and...absolutely nothing new !
This would be good for test environments in azure
Leon van de Goor commented
Any status updates to be expected soon?
Has there been any motion on this function in the last 12 months? I would love to use Azure Files to potentially replace traditional file servers but can not do this until we have a secure way to do persistent mounts via say GPO.
Chris Thoms commented
Agree this is a deal breaker for our use of Azure Files in our enterprise, as creating a GPO w/script for each file share is a serious security concern due to exposing the storage account key and the lack of ACL control. Please keep me posted if this feature becomes available.