Ability to move VM into a VNET (Virtual Network)
The ability to move a existing VM into a existing Virtual Network.
Moloko
shared this idea
AdminAzure IaaS Engineering Team
(Azure IaaS Engineering Team, Microsoft, Microsoft Azure)
responded
This was at least partially completed as part of migration of Classic VMs to Azure Resource Manager VMs where the VMs are moved into a VNet as part of migration.
If the desire is to support moving an existing resource manager VM between VNets, then please upvote the following item: https://feedback.azure.com/forums/34192--general-feedback/suggestions/6806232-include-the-option-to-change-virtual-network-in-th
5 comments
-
TJ Cornish
commented
5 years!? Nice job guys.
-
Chin Bae
commented
It's been 3 years, and this feature is still not available. Unbelievable.
-
Samir FARHAT (MVP)
commented
Maybe you can use this script:
https://buildwindows.wordpress.com/2016/03/05/move-azure-arm-vm-between-storage-accounts-and-beyond/ -
Mathieu E.
commented
And for RM VMs ? this could be usefull too
-
Douglas James Boyd
commented
The lack of ability to move and change VMs without deleting and recreating them is a major blocker to the flexibility and agility promised by cloud IaaS computing. You can only add Nics by command line, and only at creation? Can't simply change the network, even by command line, never mind the portal? This is basic stuff we take for granted internally on VMWare - Azure needs to be as agile in order to scale as an alternative data centre to on premise.