It looks like this is just giving us the configuration fragment
that we could pass in or construct maybe a full ARM template
based on this configuration fragment.
If we take the azuredeploy JSON that was created,
let me right‑click and open that in VS Code as well,
yes, here is the full template that would allow us to deploy a VM,
a new VM based on those disk snapshots in the backup here.
And if we take a look in VS Code,
if I open up Explorer and bring out my ARM template outliner,
that'll allow us to browse the template file a bit easier,
and in order to get the ARM template outliner in VS Code and to be
able to work with ARM schemas and ARM templates,
you'll want to make sure to go to the Extensions blade and
load in the Azure Resource Manager Tools,
or ARM Tools extension from Microsoft.
It's a very important extension indeed when you're doing
ARM deployment template work in Azure.
Whoops, I didn't want to leave the outliner here.
Let's go to Resources, we've got our virtual machine,
and again, all of our configuration and all of that stuff here.
Yeah,
and we can see a reference to those managed disks here on
Line 92 that when we do this deployment,
we would attach that disk from the managed disks library in our subscription.
I wanted to show you here, I've got a full backup of a Linux virtual machine.
If I go to File Recovery,
I just want to demonstrate that the process here is just about
exactly the same for a Linux VM as it is an Azure one,
it's just that the script uses a different language.
We choose our recovery point, whatever that is, then we download a script.
The portal will generate a Python script with a one‑time password.
You open up a terminal, execute the Python script,
unlock with a password,
and then you've got a mount operation that happens
just like in a Windows environment. Same thing, same process, it's just using a different engine.