An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.
For an Azure VM restore that must stay isolated, use Restore Disk instead of restoring the VM directly.
Restore Disk copies the VM VHDs to a storage account, and then a new VM can be created with the required network configuration. This is the documented approach for VMs that need special network configurations.
Key points:
- Use Restore Disk for isolated recovery scenarios
- This is the recommended option for VMs with special network configurations.
- It allows creation of a VM that matches the required network design after the disks are restored.
- Do not expect Bastion access if the restored VM has no network path
- Azure Bastion connects to the VM over the VM’s private IP inside the virtual network.
- Bastion does not require a public IP on the VM.
- But Bastion still requires connectivity from the Bastion resource to the VM over the private network.
- If the NIC is disabled or the VM is placed in a fully isolated network with no connectivity to Bastion, remote access through Bastion will not work.
- Practical recovery pattern
- Restore the disks by using Restore Disk.
- Create the recovered VM in an isolated or controlled network configuration.
- If remote access is required, place the VM in a network where Azure Bastion can still reach the VM’s private IP.
- If complete isolation is required, Bastion cannot be used until connectivity is allowed.
- Related limitation to consider
- For restored VMs with special network configurations, NICs won’t be created if the machine has Public IP and NAT gateway. This should be considered during restore planning.
So the direct answer is:
- Yes, the VM can be restored in a way that supports special or isolated network handling by using Restore Disk.
- No, Azure Bastion cannot remote into that VM unless Bastion has private network connectivity to the restored VM.