An Azure service for ingesting, preparing, and transforming data at scale.
Since the issue happens on the laptop across Firefox, Chrome, and Edge, but works on the phone, this points to a laptop-side network, DNS, proxy, firewall, or cookie setting issue rather than an Azure Data Factory service outage.
Try this in order:
- Use an InPrivate/Incognito window.
- Azure Data Factory Studio can fail to load if third-party cookies are blocked.
- In Edge, open
edge://settings/content/cookiesand make sure Allow sites to save and read cookie data is enabled and Block third-party cookies is disabled. - If all cookies should not be enabled, add adf.azure.com under Allow.
- In Chrome, open
chrome://settings/cookies, either select Allow all cookies or add adf.azure.com under Sites that can always use cookies. - Refresh ADF Studio after the change.
- Test direct connectivity from the laptop.
- In the browser address bar, open
adf.azure.comagain. - If it still times out, open Command Prompt and run an
nslookupagainst the ADF host name. - A normal DNS response means DNS is likely working and the next check is local firewall or HTTPS blocking.
- In the browser address bar, open
- If DNS resolves normally, check local network controls.
- Since the phone works, compare whether the laptop is using a VPN, proxy, security software, or corporate firewall.
- Local IT should verify that HTTPS connections to the ADF host name are not blocked.
- If DNS does not resolve normally, test broader resolution.
- Run
nslookup datafactory.azure.comandnslookup azure.comto see where name resolution fails. - If resolution is failing, the issue can be with the DNS server. Changing the DNS server, for example to 8.8.8.8, can work around that.
- Run
- If the browser can reach the ADF service endpoint and returns 404, that usually indicates the client side is fine and the issue is on the ADF service side.
- In that case, file a support ticket and include the Activity ID from the error message if one is shown.
Given the screenshot shows ERR_CONNECTION_TIMED_OUT, the strongest next checks are:
- third-party cookie settings for
adf.azure.com - VPN/proxy/firewall on the laptop
- DNS resolution from the laptop with
nslookup