Moving a Microsoft Azure VM to a Different Subnet Within a Virtual Network

the logical process to carry out a subnet migration is to:

1. migrate a vm from one subnet to another, followed by
2. update the vm configuration which will restart the vm

the msdn documentation at http://msdn.microsoft.com/en-us/library/azure/dn643636.aspx offers a sample powershell statement as below.

get-azurevm –name <a target vm name> –servicename <the associated service name> `
| set-azuresubnet –subnetnames <a target subnet to migrate to> `
| update-azurevm

and i am here providing a sample scenario of moving a vm from a dev subnet to a test one as illustrated below.

	a virtual network, foonet, has three subnets: ad, dev, and test, while each subnet is configured with a specific ip address range as shown.
	the intent is to move the vm, app1, currently in dev to the subnet, test.
	the vm, app1, is deployed to the service, foo-devtest, i.e. http://foo-devtest.cloudapp.net.
	an ise session is connecting to the microsoft azure subscription account and has successfully moved the vm to the target subnet, test. for those who are not familiar with microsoft azure powershell, a self-training tool called quick start kit (qsk) is available at http://yungchou.wordpress.com/2014/01/21/announcing-windows-azure-iaas-quick-start-kit-qsk-at-http-aka-ms-qsk/ .
	the vm now resides in the subnet, test.