These days it’s normal to deploy and configure all aspects of your Azure Resources using the Azure Resource Manager and the accompanying ARM Templates. But sometimes you walk into a missing feature that’s is not (yet) available in the ARM system.

The other day I wanted to configure Application Logging on Blob Storage for a Web App Service and found out this needs a SAS URL. And this is something an ARM template cannot provide for you.

When I recently was configuring an Azure AD application, I could not assign the delegated permissions for an Azure SQL Database. It did cost me a full day to find out the Azure Portal user interface has an unexpected user interaction when it comes to selecting APIs.

In this article, I will explain how you can find all APIs available for your application.

Azure Key Vault is a great resource to store your secrets like passwords, connection strings, certificates, etc. and access them programmatically. A great feature is to add or update your secrets during deployment so you do not have to manage your secrets manually.

In this article, I will explain how you can add secrets to an Azure Key Vault using ARM templates.

When I start on a project that uses Azure resources, one of the first things I do is build the infrastructure and automate the deployment using VSTS or TFS. The definition of the infrastructure is defined using ARM templates.
When you search online you will find plenty of examples on how to create and use ARM templates. But when you move beyond the basics, you’ll find out the documentation is lacking.

In this post, I’ll explain how you can extend Azure Web Apps with Virtual Applications and Virtual Directories using ARM templates.

The other day I needed to get the URLs for all pages in my blog for some PowerShell scripting I wanted to do Like most websites, this blog has a sitemap and I wanted to use that as a source.

As I could not find any existing PowerShell scripts on the web that I could use, I just wrote one myself.

Now I like to share this script with you.