Azure Virtual Machines Automation - Deployment
Welcome to this series where you will learn the various best practices for deploying Azure Virtual Machines and how to manage them at scale. To get started, we are going to take a look at various deployment options; how you scale this out from your initial deployment and finally to a complete self-service solution for your enterprise IT customers.Learn ARM templates (4 tutorials), from the beginning
Infrastructure as Code Infrastructure as Code, IaC is the process of expressing your infrastructure as Code as readable text files over using UIs to configure the same. The benefits of doing so are many. Below are some benefits: Dev and Ops can work in the same process. There's a need for Developers and Ops to work more tightly to innovate faster with speed and accuracy. Developers normally store their code in a version control system like Git. You can now do the same with your templates, text files desribing your Cloud resources. Anyone can deploy. When your templates are in version control, anyone on the team can deploy, just use a tool like Azure-CLI or PowerShell to do so. When everyone in a team can deploy it's important that it can be done reliably. You know what's in the Cloud. Before IaC you were/are using a graphical interface or some tool to manage your resources. It's easy to loose track of what you have in the Cloud. If you instead express your resources as text files it's a lot easier to see what's going on. Easier to reproduce elsewhere. In theory at least, it should be a lot easier to recreate your Cloud operation elsewhere if you are looking to expand your company's business elsewhere.
