1

We have a local Windows 2008 R2 file server, part of a Windows domain, with security settings on the shared directories depending on domain security groups. I would like to move the file server function to Azure and get rid of our on-premises server.

I am contemplating a setup whereby I would have a VM with file shares, duplicating the same setup and permissions as the on-premises solution, just in Azure (we would use Windows file sharing to map the shared directories for the end users). However, I have noticed that one can use WebDAV with Azure File Storage to share files as well. I believe the virtual machine setup using the virtual machine as the file server would work better for my purposes. Am I right? Does anybody have any other suggestions?

Note that we have a VPN with Azure, which we would use.

2

For your purposes I would use a VM with File Shares, the VM can be joined to your domain (or Azure AD Domain Services) and you can restrict access the same way you do now on premise. Azure File Storage is designed to allow applications to access a file share using SMB. so if you have an app on premise that uses UNC paths and SMB Protocol it can now easily moved to Azure using Azure File Storage.

Azure File Storage is not really designed to store files for users.

  • Thanks @Michael-Brown. That is what I have decided to do. – JGoldman Sep 6 '16 at 23:19
1

Azure files does as you say allow you to access Azure storage using SMB and WebDav, however the only way these are secured is by key, either storage account key or SAS token, you cannot apply NTFS or NTFS like permissions to it. For this reason we have had to implement an IaaS file server until this is possible.

1

The answer to this question will be changing at some point in the future per the recent update from Microsoft on this user voice post.

"Azure Active Directory integration is in plans but we do not have a timeline to share yet."

[https://feedback.azure.com/forums/217298-storage/suggestions/6078420-acl-s-for-azurefiles?tracking_code=6ac92d84c1845d2ab59f44e7ec991bcb][1]

It's also a case where "Azure Active Directory Integration" could be implemented a number of different ways, with a lot of different capabilities. What use cases you'll be able to achieve is still very unclear, however it still seems promising.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.