Hello ASY ASY
Please be informed that that the D:\XMLFiles\XMLArchive\
folder on your on-premises server is not correctly considered part of the Server Endpoint's synchronized scope. Because when you configure a Server Endpoint, you define a specific local path on your server that Azure File Sync will monitor and synchronize. All subdirectories and files within that specified path should be included in the sync.
- Go to your Azure Storage Sync Service and Navigate to your Sync Group.
- Under the "Server endpoints" section, click on the entry for your on-premises server.
Look at the "Path" field.
- Is it precisely
D:\XMLFiles
? If it is, thenD:\XMLFiles\XMLArchive\
is a subdirectory, and it should sync. Is itD:\
or some other parent folder, andXMLFiles
is a subfolder? If so, thenD:\XMLFiles\XMLArchive\
should still be covered. - Is there any chance the Server Endpoint was configured only for
D:\XMLFiles
and theXMLArchive
folder was later created outside its perceived scope, or there's a misunderstanding of how subdirectories are handled? (Unlikely if it's a direct subfolder, but worth confirming).
Post which Examine Azure File Sync Agent Logs on the On-Premises Server:
- On your Windows Server, open Event Viewer.
- Navigate to Applications and Services Logs -> Microsoft -> FileSync -> Sync.
- Look for any warning or error events related to download or synchronization. These logs will tell you if the agent is even attempting to download changes for that archive folder and why it might be failing.
Why it's Not Normal Behavior and What to Expect?
If D:\XMLFiles\XMLArchive\
is indeed a subfolder of your configured Server Endpoint path (e.g., D:\XMLFiles
), then any files placed into /myfileshare/XMLArchive/
via your Azure Function should absolutely sync down to D:\XMLFiles\XMLArchive\
on your server.
- Confirm it encompasses the
D:\XMLFiles\XMLArchive\
directory. diagnosing why the download isn't happening. Look for specific error messages or warnings in the Sync event logs. - If all configurations look correct and logs don't immediately reveal a clear issue, consider restarting the Azure File Sync Agent service on your on-premises server to force a rescan. (Search for "Services" -> find "Azure File Sync Agent" -> Restart).
References:
- https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/files/file-sync/file-sync-troubleshoot
- https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-portal%2Cproactive-portal
Hope the above answer helps! Please let us know do you have any further queries.
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.