How to add additional account to access Azure file storage RRS feed

  • Question

  • Hi Team,

    Is there any way to create additional account to access Azure File storage? We have around 3 staffs working on the same file and experiencing a big delay for the file opening and syncing. I am not sure how Azure handle the file lock. We are thinking of creating a new account for each staff to see whether the problem can be improve. Thank you!

    Thursday, July 26, 2018 5:13 AM

All replies

  • Hi Alleanza,

    Azure file shares operate the same as SMB file shares on Windows or other platforms; if a user's application opens a lock on a file, depending on the type of lock opened, nobody else can write to that file while the application is holding a handle to it. There are multiple kinds of locks, some allow others to read while somebody has a write open, others disallow all reads while writes are happening or all writes while reads all happening. File locks also may not apply to an entire file - applications have a great deal of flexibility. This has nothing to do with having other users on the share.

    Although this has nothing to do with the number of users on the share, it's worth noting that today, only one username/password is accepted on an Azure file share: namely, the storage account name (username) and the storage account key (password). Multiple people can use this username to login to the share simultaneously, from different machines, on-premises or in the cloud, but it's still only one user logging on to the share. This will change when we bring AAD authentication and authorization to Azure Files - users will login with their Windows identities instead of a storage account name/storage account key. Please note that even with this feature, this will not change how locking works in SMB.

    My suggestion is to look at how your application uses locks. If this is an application you are developing, perhaps you can switch the lock type used to allow co-editing on the same file, although note this will require additional overhead within your application. More likely, this is an application you are using written by somebody else, in which case you are at the mercy of the application developer. For example, co-editing is not allowed via SMB for Office applications (of course there are good reasons why not :)). If you're working on an Office document, SharePoint Online might be a better choice to get collaboration features.

    Hope this helps!


    Will Gries
    Program Manager, Azure Files

    Thursday, July 26, 2018 5:30 AM
  • @Alleanza, checking in to see if the above response helped to answer your query. Let us know if there are still any additional issues we can help with.

    Sunday, July 29, 2018 7:33 PM
  • Hi Will,

    Do you have a timeline when you can bring AAD authentication and authorization of Azure File share?



    Tuesday, July 31, 2018 7:35 AM
  • I am afraid we do not have an ETA. Our Engineers are actively working on this feature and will be available very soon. If you wish you may leave your feedback here. All the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.

    Tuesday, July 31, 2018 6:51 PM