This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(246.4, 64%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERP%3C/text%3E%3C/svg%3E)
We are trying to setup a Machine Learning Workspace and only have it accessible via Private Endpoint Connection. When we have it this setup and try to connect from our company workstations it loads the page but we get an "Error Loading recent runs"
If we run this from a VM inside Azure it is fine.
We do have a VPN Gateway set up to access our on-prem which works for other Vnets we have in Azure. We peered the VNET that ML sits in with VNET where Gateway network is setup. unfortunately we had a 3rd party set up the original connection and did not fully document. We have tried to match all settings we have in the working VNET with the ML Vnet but can't seem to see what we are missing. I also can't seem to find what logs to check to see where connections are being blocked.
Hoping I explained our issue will enough.
@Ryan Pighin I think the original setup might have followed the steps mentioned in this document.
Since you already have a VPN setup that is working and the access to the studio is enabled via the jump box and since the runs aren't loading from your workstations, I believe this could be an issue with the storage account network routing. I think by using your trace id and client request id more details can be looked up by a support engineer at the backend to confirm the same.
If it is not possible to change the networking configuration of your storage account, you can try to raise a Azure support case to engage a support engineer and with the above request details you can get the corrections that are required in the configuration to access the studio.
I hope this helps!!
thanks for that info. That helped out, but still having the same issue. I went to open a support ticket and it gave me more options to try. One option was "Make sure you can resolve the workspace FQDNs with your private IP. If you use your DNS server, you need to configure DNS forwarder. See Use custom DNS."
So if we are outside the VLAN is it a different website we would go to than what is listed in the Studio web URL? I really do feel that may be our issue, but not sure if I should be using a separate link.
thx
Ryan
So we have resolved the issue. We found that we had to add a rule to allow that traffic to the private endpoint. Once we did that and add adding a Forward Zone lookup in our DNS for the Private IPs resolved our issues.
Appreciate all that help on this
@Ryan Pighin am running into the same issue wonder if you can share more details or any links you followed. Much appreciated.