Restore an Azure VM with the existing VM still running

mij2020 361 Reputation points

I have a VM that has an Windows Update issue.

I want to restore the Azure managed disk to about 1 month ago to see if this issue was there at that point.

I don’t want to affect the original VM because its still working ok apart from the update problem.
What is the best way to do this?

The disk has Azure Disk Encryption on it and is domain joined.

I can restore the disk and create a new VM from it (with a different Azure name), add into a different subnet – but this will still start it up with the same internal computer name/guids/domain join as the existing. I don't care about logging into the domain on the test VM once restored - i just need local access.
But I would like both VM’s to be up at the same time.

What is the best way to isolate this “test recovered VM” so it does not have any impact on the existing server?
I thought about recovering the disk and then moving it to a different subscription then creating the VM from the disk after its been moved but that wont work due to the encryption on it needing to communicate with the Keyvault to decrypt.

Is there a good way to do this?

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
6,804 questions
Azure Disk Encryption
Azure Disk Encryption
An Azure service for virtual machines (VMs) that helps address organizational security and compliance requirements by encrypting the VM boot and data disks with keys and policies that are controlled in Azure Key Vault.
153 questions
0 comments No comments
{count} votes

Accepted answer
  1. Andreas Baumgarten 91,766 Reputation points MVP

    Restoring the VM in a different Virtual Network (with a different subnet) may work. Just be sure there is no peering activated between the two virtual networks.

    Subnets in the same Virtual Network are routed automatically. But 2 Virtual Networks are not "connected" if you don't activate the peering.

    Maybe this is helpful.


    Andreas Baumgarten

    (Please don't forget to Accept as answer if the reply is helpful)

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. mij2020 361 Reputation points

    I don't have another vnet - but I could certainly create one. The separate VNet wont have access to our AD either so that prevents any weirdness with 2 computers using the same account, and it would have access to the Keyvault to decrypt the disk when starting up.

    I shall try that.

    0 comments No comments