Adding Azure Virtual machine to an existing availability set

Question

I want to create two virtual machines in Azure which should not be connected to each other. I created first virtual machine and also created an availability set as part of its creation process.

Now when I create the second virtual machine then I don't get the availability set created as part of first virtual machine in the drop down list of availability sets.

However if I try to connect the second virtual machine as part of first one then I am able to see the availability set created as part of first virtual machine.

Is it mandatory for virtual machines to be connected to each other so that I can add them to the same availability set? Is this a limitation only from azure portal and there is a workaround using powershell?

UPDATE:

If we connect two virtual machines then we can get the benefit of availability set. However, at the same time both virtual machine becomes part of same cloud service and hence are load balanced by azure which does not support sticky session.

My scenerio is that I have identical front-ends which needs to support sticky session. Therefore I don't want to connect them to each other. However, I want to get the benefits of availability sets as mentioned in the article on Availability sets.

So can I set availability set for two identical virtual machines not connected to each other?

Answer 1

The term "Availability Set" means that you want to bring one or more VM within one service group for maximize the availability during an event of downtime. So what you see on Azure Portal is correct behavior however you might have some misunderstanding with regard to Availability Set. You can read more on "Availability Set" here.

So when you try to connect second virtual machine as part of first, you do see the availability set, because this way you want your VM to use the settings from the first and add another VM to the same group to maximize the availability. This second VM becomes the part of first one.

When you create an independent VM (call is second or 3rd or any) you are actually creating a brand new VM which is going to run independent to any other VM you may or may not have and thats why you dont see "availability set" instead you can create a new "availability set" based on this new VM.