Azure File Sync Install Requests a Discovery URL and nothing works

Question

Hi All,

I'm new here, we are setting up azure file sync on a 3rd party server Server 2016 and it requests a discovery URL and nothing works we have tried a dozen Microsoft advised URL's and our own azure subscription URL

We did install this in our own environment on our Server 2019 and it gave a drop down for Subscription > Resource > Storage Account but not in their environment

Is this a network/firewall issue on their end?

Kind Regards,

Mattbadm

Answer 1

Thanks for your reply - I can't use the endpoint because I haven't got far enough to add it. Sync service is requesting the discovery URL during install

Tested 1.2 it is enabled

There is no error message per say it just says

I have tried these URL's

https://discoveryservice.trafficmanager.net/

https://management.azure.com/

https://uksouth01.afs.azure.net

https://management.azure.com/metadata/endpoints?api-version=2019-05-01

Answer 2

Hello Matt,

The Discovery URL should not be your Azure subscription URL or storage account URL. It's the Azure File Sync Service endpoint, which is used during server registration.

Since the same installer works in another environment, I'd first check whether the affected server can reach the required Azure endpoints over HTTPS (TCP 443). Common causes include:

• A proxy or firewall blocking outbound connectivity.
• TLS 1.2 not being enabled (required for Azure File Sync).
• DNS resolution issues.
• SSL inspection or deep packet inspection interfering with the registration process.

You can also verify that you're using the latest Azure File Sync agent, as older versions may have connectivity or compatibility issues.

If the issue persists, could you clarify:

Which Discovery URL you're entering?

Does the server have unrestricted outbound HTTPS access?

Are you using a proxy, firewall, or SSL inspection device?

Is there a specific error message after entering the Discovery URL?

Those details will help determine whether this is a connectivity issue or a configuration problem during server registration.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.