Support for provisioning and managing Azure IaaS virtual machine environments via Azure Resource Manager (ARM) was recently launched as a Generally Available (GA) feature! There’s several HUGE advantages that ARM provides over the existing Azure Service Management (ASM) API, including simplifying complex configurations, repeatable deployments via declarative templates, resource tagging, role-based access control (RBAC) and more! You can learn more about the advantages of this new API at:
With the GA launch of ARM for Virtual Machine services, lots of us are exploring how to leverage this new API as part of an automated provisioning process. So, I thought I’d update my previous guidance on automated provisioning of IaaS environments for using the new Azure Resource Manager.
In this article, we’ll step through using the latest Azure PowerShell module, which is version 0.9.4 as of this article’s publication date, to perform end-to-end provisioning of a common IaaS VM scenario: load-balanced web applications. My goal in this article is to provide you with code snippets that can serve as “building blocks” for learning and creating your own automated provisioning process using Azure Resource Manager, PowerShell and Desired State Configuration.
In future articles, we’ll look at provisioning this same scenario using other tools and approaches, such as Azure Resource Manager Templates and also the Azure Cross-Platform CLI for Linux and Mac OSX ...
Use Windows PowerShell to easily pick up the user name.
Use Windows PowerShell to get a list of unique process names.