Here is a quick script to create a new resource group, Storage account, storage account container and upload a VHD



Here is a quick script to use to upload Modules to Azure Automation.


Today I am going to show you how to upload files to Azure Storage using the Azure Resource Manager PowerShell cmdlets. We are going to  upload all of our resources to the resource group and storage account that we created in this previous post. Once you have built your ARM template, VHD or DSC Configuration you can use the script below to upload the files to Azure storage. This scripts uploads files as a block blob type, you can read more about Azure Storage types here. I will cover this a bit more in a future blog post where I will show you how to upload a custom VHD to Azure, for now just note that you should not use the script below as is to upload a VHD.

Deploying Azure Resources with Azure Automation Blog Series




Today I am going to use the Azure PowerShell Module to create a new Azure Resource Manager storage account and 3 containers to store different resources that we will need throughout this blog series. The first container we are going to name vhdimages, we will store custom VHD images here, the second container is named armtemplates, we will store our json/Arm templates here and the last container is named configurations we will store a DSC configurations hear.  Optionally you could store everything in a single container but I have chosen to create separate containers for organizational purposes

If you have not used the Azure PowerShell Module yet you can download it here.  If you are reading this before October 2015 I recommend that you take a look at this Wiki article Deprecation of Switch Azure Mode in Azure PowerShell to understand some of the upcoming changes to the Azure PowerShell module. I plan to update all of these scripts to use the late September release of the module once it is release. Need to know how to connect to Azure with PowerShell check out this blog post.

There are a few rules to know while working with azure storage accounts, each storage account in azure must have a unique name, so it may take a few attempts to find a name that is not already in use by another azure user. Storage accounts and container also can only contain lowercase characters or number.

Deploying Azure Resources with Azure Automation Blog Series

Today I am going to show you how to connect to Azure with the PowerShell Module. There are a few things that you should have in place before trying to connect. You will need to have an Azure Subscription and I recommend setting up Azure AD. I am not going to cover how to get Azure AD setup in this series, there are many blog post out there already on how to setup Azure AD Connect and ADFS.

What Credential should you use to connect to Azure, my recommendation is that you use an organization account that you have granted access to your Azure subscription. You have the option to use an Azure AD account also but if you have signed up to azure with a personal or gmail address you will not be able to authenticate to Azure with that account using the scripts below.  You will get this error

Add-AzureAccount : -Credential parameter can only be used with Organization ID


If you are running the Azure PowerShell module from your desktop you can use the following 3 lines to get connected to Azure.

If you are running the Azure PowerShell module from Azure Automation you can use this workflow as a template.

To use the above workflow you will need to create an credential asset in Azure Automation, I will cover this more in one of the Azure Automation blog post.

Deploying Azure Resources with Azure Automation Blog Series

I’ve decided to produce a single list of community based runbooks I have found useful. I will update this post as I find more.

Start Azure Automation Child Runbook

Send Email from Azure Automation from a Visual Studio Online Service Hook

New Service Request from Template


In this post we are going to apply the DSC Configuration we uploaded in the last blog post to a Server Node.

Lets check the status of the compilation job


We can see that the status now says complete.

Check the status of the Node we want to apply the configuration too


you will notice that the NodeConfigurationName property is null, this means that there is not a configuration applied to the node.

Lets double check what Configurations we have loaded in Azure Automation DSC that we can apply to this node.


by running the cmdlet  $MyAutomationAccount | Get-AzureAutomationDscNodeConfiguration we see that we have two configurations, we are going to use the webserver.IIS and apply it to the DemoDSC Node by running:

$WebNode = $MyAutomationAccount | Set-AzureAutomationDscNode -NodeConfigurationName “webserver.IIS” -id “024b8929-f98b-11e4-80bb-000d3a9096e9”


the ID parameter on the Set-AzureAutomationDscNode command is the ID of the Node as you can see in the above image the demodsc node now has a configuration and the ID property matches the ID I entered in the cmdlet.

below you can see that initially we had the base 14 Windows Features installed, I forced the configuration to apply by running the Update-DSCConfiguration -wait -verbose cmdlet, if i would not have run this command the configuration would have applied the next time the DSC client checked in to Azure Automation DSC. After the DSC Configuration was applied 27 windows Features were installed.


In the past few blog post I have shown you how to get started with Azure Automation DSC, in the first blog post I coved how to Enable Azure Automation Preview and in the second how to Register Servers to Azure Automation DSC.  In this blog post I am going to go over how we can upload a DSC configuration to Azure Automation DSC.

First we will need a Configuration, there are a few public repositories the most popular two are on Github and  Powershellgallery. for my example we are going to use the configuration below.

save the above configuration as  webserver.ps1

Upload Configuration to Azure Automation DSC

Start Compilation Job

Check Status of Compilation Job


In the next blog post I will show you how to link the configuration to a Node.

In the previous blog post I showed you how to enable Azure Automation DSC Preview, now lets take a look at how we can register existing on premise servers to Azure Automation DSC.

First we need to export meta configurations from Azure.

Now we can move the DscMetaConfigs directory that was downloaded in the previous script, to a network share or a local machine.

This single command needs to be run on the local server that you want to register to Azure Automation DSC to set the local DSC Configuration to use Azure Automation as the Pull Server.

I installed the latest PowerShell v5 update on my test machine to get this next command to work, you can download it here.

as you can see below I now have one node registered with Azure Automation DSC


If you are registering a new Azure VM with Azure Automation DSC the process can be done at build time of the VM.