Compute Instance, Attached Compute in ML Studio issues

Hi Carmine Basile,

I understand how frustrating it is to spend so much time just trying to attach a virtual machine to Azure ML Studio. The main reason you're facing these issues is because Azure has strict networking and security rules, especially when the virtual machine (VM) is created outside of the ML Studio. When a VM is inside a Virtual Network (VNet), Azure requires things like private IP addresses, storage accounts in the same network, firewall rule changes, and sometimes private endpoints to allow the VM to communicate with the ML workspace. All of this is meant for advanced security in enterprise environments, but it can feel overwhelming.

The easiest and recommended solution is to create the VM (called a Compute Instance) directly from inside ML Studio. When you do that, Azure automatically sets everything up correctly in the background, and you won’t need to deal with any network settings, IPs, or firewalls. It just works. This way, you can quickly start using the VM for training, AutoML, or notebooks without extra setup. I truly understand your frustration, and I recommend this simpler route to avoid further delays.

I hope this information helps. Thank you!