Azure App Service has supported running containers for a while now, both in standard App Service and in Azure Functions. Setting this up through the UI is pretty straightforward, however, creating the same setup using Infrastructure as code can be a bit tricky. There are several different configuration settings that need to be added that are not always obvious. In this article, we will cover them what these are and when to use them and put them all together in one place.
This week, I discovered that it is possible to use the functions that are in Bicep (and ARM) templates in C# code. Why would you want to do this? Well, for the most part, you wouldn’t. Basic functions like concatenate, split etc., already have equivalents in C# code that would produce the same results. However, I had a specific scenario where it did prove useful. In my scenario, I needed to generate a unique string identifier for some resource naming.
How to create Privileged Identity Management role assignments at deployment time using Bicep
How to make developing Bicep and ARM deployment scripts easier using Docker and VS Code remote Docker extension
The ARM TTK Azure DevOps extension has now been updated to support working directly with Bicep files, no need to compile first!
Azure PowerShell an CLI now have native support for deploying Bicep files