Share via

AzureML Compute Instance SSH via public IP

Austin Coffman 0 Reputation points
2025-12-21T14:29:21.8633333+00:00

I noticed my compute instances created in the past week are no longer accessible via ssh with the public IP. For example, the public IP + ssh instructions you see on the compute instance pane will result in a time out. My older compute instance(s) still function properly: ssh via public ip is possible. I noticed that in the resource group the old compute instances have system generated public ips, NSG, and load balancers from azure batch. The newly generated compute instances do not. The compute instances sit in a user created vnet/subnet. For reference private ip SSH within the vnet/subnet that the compute instances sit in works properly.

Is there an azure level policy change that could affect this behavior?

Azure Machine Learning
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-12-21T14:29:28.9133333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The issue you're experiencing with SSH access to your newly created Azure Machine Learning compute instances via public IP could be related to the configuration of the compute instances and the network settings. When creating compute instances in a user-created virtual network (VNet), you have the option to select No public IP, which would prevent the creation of a public IP address for those instances. If this option was selected for the new compute instances, they would not be accessible via public IP, hence the timeout issue you are facing.

    For older compute instances that are functioning properly, they likely have public IP addresses assigned, which is why you can still access them via SSH. Additionally, if the new compute instances are in a managed virtual network and configured for no public IP, you would need to use the az ml compute connect-ssh command to connect over SSH using a private connection.

    To summarize, check the configuration of your new compute instances to see if they were set up with the No public IP option, and ensure that the necessary network settings are in place to allow SSH access if you intend to connect via public IP.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.