Extremely Slow NTFS Permission Change - Azure File Share

Question

Recently migrated file server data to Azure File Share. No issues with mapping or opening files. The problem is when NTFS permission is updated or changed, that it takes a LOT of time (hours). Any advise or workaround is greatly appreaciated. Thanks.

Answer 1

@Eric Fuentes Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

To understand the issue better: Can you please elaborate bit more on your query. Check if there is any Network Latency?

Slow NTFS permission changes in Azure File Share can be due to several factors, including the size of the directory, the number of files and subdirectories, and the complexity of the permission structure.

When NTFS permissions are updated or changed on an Azure File Share, it can take some time for the changes to propagate to all the file shares and clients that are connected to the share. This is because Azure File Shares use a distributed architecture, and changes to permissions need to be propagated across all the storage nodes that are hosting the share

This article lists common problems related to Azure file share performance and provides potential causes and workarounds. To get the most value from this troubleshooting guide, we recommend first reading Understand Azure Files performance.

Additional information: 1. Use Azure Monitor: Use monitoring tools to analyze the performance and identify bottlenecks.1. You can also consider Azure File sync in this scenario: Azure File Sync, which allows you to cache Azure Files on a local Windows Server. This can improve performance for certain operations, including NTFS permission changes.

Please let us know if you have any further queries. I’m happy to assist you further.    

---

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.