In my previous post I wrote about using Azure automation to start and stop an Azure VM that is deployed using Resource manager. If you did not read that one I suggest you read it first since I will use that setup and the scripts in this post. The azure automation has a great editor, but there is no version control in it. To solve this Microsoft added an option to integrate with GitHub and Visual Studio Online.
Last week I updated my Azure storage and Virtual machines to Azure Resource Manager. Before that I had the OneShare for MSDN app from Sogeti to start and stop my VM every day so I could start using it without having it to boot manually. Unfortunately the app cannot authenticate with Azure Resource Manager so I have to find another way to make it automatically start and stop. Azure Automation The first thing I thought of was Azure Automation, I use that a lot and I have the knowledge of PowerShell to make this happen.
In the trend of my recent blog post I create a new addition to my automation of Office 365 tasks. This time creating a report with the license consumption per month with PowerShell automation, Azure table storage and Power BI. In this post I will take you with me thru the steps to set this up. What do we need? Before we can get started coding we need to do some plumbing first.
We are rolling out Office 365 at my current assignment. Within this project we want to automate as much as possible to avoid human error and reoccurring tasks. We already used a lot of PowerShell for our current SharePoint farm, so the most obvious thing was to look at PowerShell for automating those tasks. In this article I will take you with me on the journey that we took. Why Azure Automation We choose Azure Automation for a few reasons.