Azure Bicep fail() function was introduced in Bicep CLI v0.33.93. In short this function allows you to fail your deployment when certain conditions are met. In this blog post we will look at how to use it in real world example.
When helping folks at Microsoft Q&A I saw a question regarding creating Dynamic scope with Bicep or Terraform. That led to creating this blog post where we will see what is the resource type behind Azure Update Manager Dynamic scope and how it can be created with Bicep. Of course the same thing applies to Terraform and AzAPI provider.
Recently I’ve published blog post Subscription Level Deployment Schema. When I published it I was not aware that not so many people know what the schemas are used and needed for. With this blog post I want to address this.
Not so long ago in Azure we only had resource group level deployment but a couple of months ago subscription level deployments were implemented. On resource group level we deploy resources like Azure VMs, Service Apps, Azure SQL databases, etc and on subscription level we deploy policy definitions and assignments, resource groups (yes they are resource as well), custom RBAC roles, etc. Because of that it the schema in the ARM templates for resource group and subscription level deployments is different. This is something I haven’t thought about it around the excitement of this new deployment method but my good friend Kristian Nese tipped me. So here are the schemas you should use depending on your deployment:
Yesterday Dave announced that there is a new Azure VM extension that deploys the Service Map Dependency Agent. The example provided was only for PowerShell so it was natural that we need ARM template as well. Continue reading “ARM Templates for Service Map Dependency Agent Deployment”
Cloud Administrator in Azure World 