Azure Files
An Azure service that offers file shares in the cloud.
1,350 questions
Azure File Sync and Private Endpoint
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 46%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER4%3C/text%3E%3C/svg%3E)
rr-4098
1,826
Reputation points
We have setup File Sync in Entra with a private endpoint and installed the agenton a small onprem file server. We are not using Azure DNS etc.. and updated the local host file for all the private endpoint IP's and FQDN's. When the Server Registration runs it completes and the test connection to the file sync services passes as well. In Entra when I setup the Server Endpoint it fails with "The operation 'Create server endpoint' failed with the following error: The server could not apply the new configuration." The event logs on the file server state it was block since a private endpoint is in place.
I cannot for the left find what I am missing....
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 6%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKD%3C/text%3E%3C/svg%3E)
Keshavulu Dasari 3,095 Reputation points Microsoft Vendor2025-01-30T21:18:58.24+00:00 Hi rr-4098,
Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!
You have completed much of the setup correctly, but there might be a few things to check to resolve the issue with creating the server endpoint. I suggest few considerations.
Verify Network Configuration ensure that the private endpoint is correctly configured and that the network interface associated with the private endpoint has the correct IP address and DNS settings, check that the private DNS zone is correctly set up and that the DNS records for the private endpoint are resolving correctly on your on-premises server.
Make sure that there are no firewall or NSG rules blocking the traffic between your on-premises server and the Azure File Sync service, look at the event logs on your on-premises server for any specific error messages that might give more details about why the configuration is being blocked.
Use the Debug-Storage Sync Server Cmdlet:
- Run the
Debug-StorageSyncServerPowerShell cmdlet on your on-premises server to diagnose common issues such as certificate misconfiguration and incorrect server time.
Check Server Endpoint Path:
- Ensure that the server endpoint path specified is a locally attached NTFS volume. Azure File Sync does not support mapped drives as a server endpoint path.
Update Azure File Sync Agent Make sure you have the latest version of the Azure File Sync agent installed on your on-premises server.
Hope this helps, if you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you
- Run the
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 0%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
Silvia Wibowo 5,126 Reputation points Microsoft Employee2025-01-30T21:22:29.5066667+00:00 Hi @rr-4098 , please verify the Azure File Sync service is running on the server:
- Open the Services MMC snap-in and verify the Storage Sync Agent service (FileSyncSvc) is running. If the service is not running and fails to start, see Storage Sync Agent service (FileSyncSvc) fails to start.
-
rr-4098 1,826 Reputation points
2025-01-30T21:28:09.2266667+00:00 The storage sync agent is running and has been restarted multiple times. Also the local host list the fqdns for all services without the privatelink name which is correct, right?
Sign in to comment
Sign in to answer