Cloud Skills Blog

Closing the Skills Gap One Student at a Time

Importing and Exporting Virtual Machine Settings

Posted on: June 18, 2012 by Michael Washam

I wanted to highlight the Export-AzureVM and Import-AzureVM cmdlets as I’ve seen quite a few recent cases where they come in handy when dealing with Windows Azure Virtual Machines.

Here are a few places where they can be exceptionally useful 🙂

Situation #1: Deleting a Virtual Machine when you are not using it and restoring it when you need it
Windows Azure billing charges for virtual machines whether they are booted or not. For situations where you have an “on and off” type of deployment such as development and test or even applications that don’t get as much usage after hours having the ability to save all of the current settings and remove and re-add later is huge.

Situation #2: Moving Virtual Machines between Deployments
If you ever find yourself in the situation where you need to remove and re-configure a VM in a different deployment. This could happen because you booted the VM up but placed it in the wrong cloud service or you misconfigured the virtual network and have to reconfigure.

There are likely many more scenarios but these seem to be the most common.

So here are a few examples to show how it works:

Exporting and Removing a Virtual Machine

# Exporting the settings to an XML file 
Export-AzureVM -ServiceName 'cloudservice'  -Name 'vm name' -Path 'c:\vms\myvm.xml'
# Remove the Virtual Machine 
Remove-AzureVM -ServiceName 'cloudservice'  -Name 'vmname'

Note: Remove-AzureVM does not remove the VHDs for the virtual machines so you are not losing data when you remove the VM.

If you open up the xml file produced you will see that it is a serialized version of your VM settings including endpoints, subnets, data disks and cache settings.

At this point you could easily recreate the same virtual machine in a new or existing cloud service (specify -Location or -AffinityGroup to create a new cloud service). This operation could easily be split up into a few scheduled tasks to automate turning on and turning off your VMs in the cloud to save money when you aren’t using them.

Import-AzureVM -Path 'c:\vms\myvm.xml' | New-AzureVM -ServiceName 'cloud service' -Location 'East US'

For more than a single VM deployment PowerShell’s foreach comes to the rescue for some nice automation.

Exporting and Removing all of the VMs in a Cloud Service

Get-AzureVM -ServiceName 'cloud service' | foreach { 
    $path = 'c:\vms' + $_.Name + '.xml'
    Export-AzureVM -ServiceName 'cloudservice' -Name $_.Name -Path $path
# Faster way of removing all VMs while keeping the cloud service/DNS name 
Remove-AzureDeployment -ServiceName 'cloudservice' -Slot Production -Force

Re-Importing all of the VMs to an existing Cloud Service

$vms = @()
Get-ChildItem 'c:\vms' | foreach {
	$path = 'c:\vms' + $_
	$vms += Import-AzureVM -Path $path
New-AzureVM -ServiceName 'cloudservice' -VMs $vms

11 thoughts on “Importing and Exporting Virtual Machine Settings

  1. Herwig

    I have configured a VM direct via RDP. It’s up and running. How could I clone this VM via PowerShell and start another instance with a new URL?

    1. Michael Washam

      Currently, there isn’t native support for snapshotting blobs in the Windows Azure PowerShell cmdlets but it is pretty easy to do using the storage client library (just have to translate it to PowerShell).

      Once you make a snapshot of the underlying VHD you would just use the Add-AzureDisk cmdlet to create the disk and then create a VM based off of that disk.

      If I get a chance later this week I’ll try to put together a sample. It’s a great idea!

      1. Pavan Keerthi (@pavan_keerthi)

        I would be interested to look at this example.I always thought configuring VM inside a cloud based VM is bad idea,because it will have limitations on networking side.

        If the internal VM could connect directly to blob storage disk even better 🙂

  2. Brian Ehlert

    Is it possible to export the configuration of the Service itself?

    My scenario is that I have to delete the Service and re-create it due to some problem. I also want the AffinityGroup, Region, and any VirtualNetworks that were associated. Without trolling the entire service prior to deletion.

  3. Ralph J

    for some reason the values got blanked out – hopefully this works:

    Import-AzureVM -Path ‘c:vmsmyvm.xml’ | New-AzureVM -AffinityGroup ‘*affinity group name*’ -ServiceName ‘*cloud service name*’ -VNetName ‘*virtual network name*’


leave a reply

Share this page


Connect with Opsgility