Forum Discussion

SebastiaanR's avatar
SebastiaanR
Brass Contributor
May 28, 2025
Solved

Azure ML Studio - Attached Compute Challenges

Hello community, I'm new to ML services and have been exploring the ML Studio the last while to understand it better from an infrastructure point of view. I understand that I should be able to at...
machine learning
ML Studio
  • MoritzG's avatar
    MoritzG
    May 31, 2025

    To my knowledge (I hope this is still correct by now):

    Attaching an existing Azure VM as a compute target requires a public IP. Even if your Azure ML workspace uses a private endpoint, the attach process defaults to SSH over the public IP. Azure ML does not currently support attaching a VM over a private IP only.
    So, your NSG and subnet config may be fine, but the service still needs that public IP to connect.

    VM not showing in Notebook compute options is also as expected. Attached VMs are only for submitting training jobs, not for interactive notebooks. Only Azure ML-created compute instances/clusters show up in the notebook UI.

    Recommendation: If you want a private-only setup, use a Compute Instance or Compute Cluster created in Azure ML Studio. These can live fully inside a VNet and support private networking properly.

    Hope that helps. Best regards! :)

SebastiaanR's avatar
SebastiaanR
Brass Contributor
Jun 03, 2025

Thanks for taking the time to respond, you've validated what I suspected. I was hoping perhaps I overlooked something, but it seems as though the way I want to do it requires the specific approach that you've articulated.

Resources