Changes made to the Azure file share by using the Azure portal or SMB are not immediately detected and replicated like changes to the server endpoint.

Question

As per the title; changes made to the Azure file share by using the Azure portal or SMB are not immediately detected and replicated like changes to the server endpoint.

I have reviewed the following article:
https://learn.microsoft.com/en-us/azure/storage/files/storage-sync-files-troubleshoot?tabs=portal1%2Cazure-portal&WT.mc_id=Portal-Microsoft_Azure_Support#sync

I noticed there is a PowerShell cmdlet, Invoke-AzStorageSyncChangeDetection; however, I do not understand if this is initiated manually on the portal side or on the server endpoint?

Please advise, and thank you.

Answer 1

@Jake
Invoke-AzStorageSyncChangeDetection should be able to be executed from anywhere you have Azure PowerShell installed. Are you receiving errors or seeing issues when running it?

You could run this command as part of a script in automation, but please note the limitations on the documentation you linked. That said, it sounds like you are trying to use Azure File Sync in a scenario it was not designed for: client-side caching. Azure File Sync is not a client-side caching solution, it's a solution that enables you to cache on a file server. (It's why we do not allow Azure File Sync to be installed on a Windows client - only server.)

There is an existing feedback item where you can add your use-case and monitor for updates from the product team.

-------------------------------

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