- Q1: The behavior of creating resources in the resource group of the VNET occurs because Azure attempts to ensure the compute is deployed with network proximity to the VNET for better performance. But you can specify the resource group explicitly during the compute creation process.
az ml compute create --name <COMPUTE_NAME> \ --``type`` AmlCompute \ --resource-group <RESOURCE_GROUP_OF_ML_WORKSPACE> \ --workspace-name <WORKSPACE_NAME> \ --vnet-name <VNET_NAME> \ --subnet <SUBNET_NAME> \ --no-public-ip
- To enable networking for the compute without a public IP in a custom VNET, you must set up the appropriate configurations for both inbound and outbound traffic. Make sure you configure
- NSG Rules
- Use Nat Gateway To get inbound without public ip, you might need to use VPN / Express route / Private Endpoints.
Hope this helps