There are 2 models, Classic and Resource Manager
- Some resources and behaviors are available in one or the other but possibly not both.
- Load balancing traffic across virtual machines created with the Classic deployment model is implicit because virtual machines are members of an Azure Cloud Service, and load is automatically balanced across virtual machines within a cloud service.
- Virtual machines created using Resource Manager are not members of a cloud service, and a separate Azure Load Balancer resource must be explicitly created to load balance traffic across multiple virtual machines.
- Therefore, resources created using one deployment model can’t necessarily interoperate with resources created using a different deployment model.
- Example, Azure Virtual Machines created using one deployment model can only be connected to Azure Virtual Networks created using the same deployment model.