Updating symantec endpoint protection
Using affinity groups will unnecessarily associate your VMs to specific hardware that limits the choice of VM sizes that are available to you.It might also lead to capacity-related errors when you attempt to add new VMs if the specific hardware associated with the affinity group is near capacity.Three key differences that sometimes surprise Hyper-V users are: For virtual machines created in the classic deployment model, you can use Azure Virtual Network to extend your existing infrastructure. You can provision and manage virtual private networks (VPNs) in Azure as well as securely connect them to on-premises IT infrastructure. You’ll need to specify the network that you want the virtual machine to belong to when you create the virtual machine.You can’t join an existing virtual machine to a virtual network.You shouldn’t use the temporary disk (the D: drive by default for Windows or /dev/sdb1 for Linux) to store data.They are only temporary storage, so you would risk losing data that can’t be recovered.
This article covers using the Classic deployment model.
Affinity group features are already deprecated in the Azure Resource Manager deployment model and in the Azure portal.
For the classic Azure portal, we're deprecating support for creating affinity groups and creating storage resources that are pinned to an affinity group.
Microsoft recommends that most new deployments use the Resource Manager model.
For the FAQ when using the Resource Manager model, see here.All subscribers can run server software on an Azure virtual machine.