@Tobias Thank you for your patience while we were looking into your issue. I received the following suggestion from our internal team regarding your use case-
This could be accomplished using DFS Namespaces. However, we don't recommend this scenario currently. All users should either directly access the Azure file share or access the share from Windows Server(s) that have the Azure File Sync agent installed. The reason is that we don’t have change tracking in Azure Files today. So if a user makes a change directly in the Azure file share, it will take over 24 hours to sync the change to the Windows Servers. In addition to the delay in syncing files to the server, if a file is modified in the Azure file share and the same file is modified on the server (before the file update in the Azure file share is synced to the server), it will result in a file conflict.
Hope this is helpful! Please let us know if you have any more questions and we will be glad to assist you further. Thank you!
Remember:
Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.
Want a reminder to come back and check responses? Here is how to subscribe to a notification.