Adding existing ARM virtual machine to availability set
Adding existing ARM virtual machine to availability set. I can't do much with certain setups cause they have to be in an availability set and I cant add them to one after they have been created.
Valid suggestion open for upvote
James Bazemore commented
Add me to the votes for this feature!
John Gilmartin commented
+1. Ok, so this can be achieved using available Powershell scripts. But in that case, it should be a no brainer to add the option to the web portal and the CLI.
Please, just add this feature. The comments below well explain all the reasons to do that.
AUSTIN AUDU commented
The restore from Azure Vault is almost useless if we cant get the option during the restore to select the AVset to restore VM into like during a regular build, that way we can fully restore the VM as it was originally.... that would make Azure backup a perfect product...almost :)
Rich Morrissey commented
This is going to lead me to looking into AWS instead.
Mohammed Kasim commented
Any update on this request.. we are with the same requirement. Client wanted to add VMs to availability set. and re-creating is not a good option.
David Graham commented
It's also a requirement if you wish to use Load Balancers so if there is a design change halfway through a deployment it can be a pain to get everything into the right availability sets.
The workaround of requiring people to delete and recreate virtual machines is not without risk and not as simple as allowing availability set memberships to be modified. This capability needs implementing.
Since having an availability set is key to providing high availability and having a service covered under SLA this core administration need is missing. Requirements may change and require people to add existing machines to sets or remove them.
Aidan Finn commented
Agreed. It's extremely disruptive to have to delete/re-create machines if plans change.