Troubleshoot connection to a workspace with a private endpoint

When connecting to a workspace that has been configured with a private endpoint, you may encounter a 403 or a messaging saying that access is forbidden. Use the information in this article to check for common configuration problems that can cause this error.


Before using the steps in this article, try the Azure Machine Learning workspace diagnostic API. It can help identify configuration problems with your workspace. For more information, see How to use workspace diagnostics.

DNS configuration

The troubleshooting steps for DNS configuration differ based on whether you're using Azure DNS or a custom DNS. Use the following steps to determine which one you're using:

  1. In the Azure portal, select the private endpoint for your Azure Machine Learning workspace.

  2. From the Overview page, select the Network Interface link.

    Screenshot of the private endpoint overview with network interface link highlighted.

  3. Under Settings, select IP Configurations and then select the Virtual network link.

    Screenshot of the IP configuration with virtual network link highlighted.

  4. From the Settings section on the left of the page, select the DNS servers entry.

    Screenshot of the DNS servers configuration.

    • If this value is Default (Azure-provided) or, then the VNet is using Azure DNS. Skip to the Azure DNS troubleshooting section.
    • If there's a different IP address listed, then the VNet is using a custom DNS solution. Skip to the Custom DNS troubleshooting section.

Custom DNS troubleshooting

Use the following steps to verify if your custom DNS solution is correctly resolving names to IP addresses:

  1. From a virtual machine, laptop, desktop, or other compute resource that has a working connection to the private endpoint, open a web browser. In the browser, use the URL for your Azure region:

    Azure region URL
    Azure Government
    Azure China 21Vianet
    All other regions
  2. In the portal, select the private endpoint for the workspace. Make a list of FQDNs listed for the private endpoint.

    Screenshot of the private endpoint with custom DNS settings highlighted.

  3. Open a command prompt, PowerShell, or other command line and run the following command for each FQDN returned from the previous step. Each time you run the command, verify that the IP address returned matches the IP address listed in the portal for the FQDN:

    nslookup <fqdn>

    For example, running the command nslookup would return a value similar to the following text:

    Server: yourdnsserver
    Address: yourdnsserver-IP-address
  4. If the nslookup command returns an error, or returns a different IP address than displayed in the portal, then the custom DNS solution isn't configured correctly. For more information, see How to use your workspace with a custom DNS server

Azure DNS troubleshooting

When using Azure DNS for name resolution, use the following steps to verify that the Private DNS integration is configured correctly:

  1. On the Private Endpoint, select DNS configuration. For each entry in the Private DNS zone column, there should also be an entry in the DNS zone group column.

    Screenshot of the DNS configuration with Private DNS zone and group highlighted.

    • If there's a Private DNS zone entry, but no DNS zone group entry, delete and recreate the Private Endpoint. When recreating the private endpoint, enable Private DNS zone integration.

    • If DNS zone group isn't empty, select the link for the Private DNS zone entry.

      From the Private DNS zone, select Virtual network links. There should be a link to the VNet. If there isn't one, then delete and recreate the private endpoint. When recreating it, select a Private DNS Zone linked to the VNet or create a new one that is linked to it.

      Screenshot of the virtual network links for the Private DNS zone.

  2. Repeat the previous steps for the rest of the Private DNS zone entries.

Browser configuration (DNS over HTTPS)

Check if DNS over HTTP is enabled in your web browser. DNS over HTTP can prevent Azure DNS from responding with the IP address of the Private Endpoint.

  • Mozilla Firefox: For more information, see Disable DNS over HTTPS in Firefox.
  • Microsoft Edge:
    1. Search for DNS in Microsoft Edge settings: image.png
    2. Disable Use secure DNS to specify how to look up the network address for websites.

Proxy configuration

If you use a proxy, it may prevent communication with a secured workspace. To test, use one of the following options:

  • Temporarily disable the proxy setting and see if you can connect.
  • Create a Proxy auto-config (PAC) file that allows direct access to the FQDNs listed on the private endpoint. It should also allow direct access to the FQDN for any compute instances.
  • Configure your proxy server to forward DNS requests to Azure DNS.