IaaS v2 – New enhancement with Azure Architecture

I won’t take too long to reveal the facts you are searching for and surfing the internet. Let me first give you a brief answer about IaaS version 2.
Definition:IaaS v2 describes few architectural changes in Azure. This was made possible by the introduction of a new management framework called Azure Resource Manager, (ARM).
Definition decoded:
The story of ‘IaaS v2″ begins with understanding the differences between Azure Service Management (ASM), and Azure Resource Managers (ARM). A management framework is available for almost all IT systems. The management framework that was originally designed and used to manage Azure Service Management (ASM) was also known as Classic. Microsoft has now introduced a new framework called Azure Resource Manager (ARM). This is why we have two portals for Azure management. One is the default portal that works on ASM framework and the other is the Azure Ibiza preview portal that works on ARM framework. Even Azure PowerShell CMDLETS can be used in two modes: ASM or ARM.
The ARM framework introduces many architectural changes to improve the management of Azure IaaS services today. The new design is called ‘IaaS v2’ and the older design is ‘IaaS v1″.

Changes in IaaS 2.0:+ Cloud Service has been replaced by Resource Group. IaaS 2.0 completely eliminates the cloud service concept as a container. The Resource Group could now include virtual machines as well as any other resources that are related to the same department or application.
+ Load balancer is now an individual resource or discrete resource, and is not tied to anyone like in cloud service.
+ We don’t need to give VIP (Virtual Ip address). We can assign VMs to Internet routable IPs so that VMs can be directly connected to the Internet. If we deploy a load balancer, the VIP can only be assigned to that load balancer.
+ There will now be three fault domains, whereas in IaaS (ASM), there were only two.
+ Virtual Machines will be bound with Azure Key Vault service, which is designed for greater security because it encrypts credentials as well as keys used for storage access.
+ Network adapters are now an independent resource that can be created and managed to protect the network configuration in case of VM failure. If required, the Network Adapters can be linked quickly to any other VM.
+ VM Endpoints are no longer required. The same task of allowing traffic from a specific port is performed by configuring NAT rules on a load balancer component.
Benefits of IaaS v2
+ Role Based Access Control
+ More control over the IaaS environment
+ Template-based deployment
IaaS V2’s most significant impact is when it allows you to create templates to deploy resource group and then apply them at a much faster pace. ARM framework allows us to create JSON (Java Script Object Notation), based templates. In real-time, if an application needs to be deployed and has typical requirements like VM, storage, network, etc., we can create a JSON template that will tell the JSON framework to create all these resources and to build a Resource Group. Once this task is completed, all resources are deployed on Azure. You can also deploy the same template to multiple locations if you need the same application. This makes application deployment super fast. Cloud Formation is a feature of AWS that allows you to get an idea of the platform. I hope this has helped you to get a solid understanding of IaaS version 2. You can also find links to further research if you are interested in the subject.
What Microsoft has explained about ARM?https://azure.microsoft.com/en-in/documenta