A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
Hello Handian, thanks for reaching out! I ran into the same thing when I first onboarded on-prem/Arc-registered VMs—under the “Connect” blade you only get “Connect with SSH,” even on Windows machines. That’s because:
• Azure Bastion is a PaaS service you deploy into an Azure Virtual Network; it only knows how to RDP/SSH into VMs that have a private IP on that VNet
• Arc-enabled servers, by default, are external resources (on-prem, other clouds, Azure Stack HCI) and don’t live inside your Azure VNet, so Bastion can’t see or route to them
• The Arc connected-machine agent exposes an SSH channel for management, which is why you see SSH for every Arc VM
If you want RDP over Bastion into your Arc-managed Windows boxes you currently need to deploy the Arc Proxy/Gateway service (gated preview) or use the new Bastion extension for Arc machines, which will bridge Bastion into your on-prem hosts. Until that preview capability is enabled in your tenant, Bastion won’t show up as a connection option for Arc VMs.
Hope that explains why you only see SSH—for now that’s expected behavior with Arc. Let me know if you want details on the Arc Proxy/Gateway preview!
References