Tag: Bicep

Provision Microsoft Fabric with Azure Bicep

Overview

Microsoft Fabric consolidates analytics workloads (including Power BI) on a tenant-wide capacity. These Fabric capacities (SKUs F2–F2048) can be provisioned declaratively with Bicep like any other Azure resource. This post covers:

Easy handling of optional Azure Web App settings in Bicep

Often you don’t need all the configurations of an app per stage; sometimes they are optional. This is often the case for the development stage in particular.

Use constants in Azure Bicep to simplify your IaC life.

Azure is an ecosystem full of constants, identifiers, IDs or role definitions. Unfortunately, ARM and Bicep do not provide as much support as they could.
So you have to become active yourself, as bitter as it sounds.

Avoid hardcoded Microsoft URLs with Bicep environments

Bicep has a great feature, which meanwhile also leads to warnings during execution if you don’t pay attention to it: the avoidance of static values like URLs in Bicep files. A corresponding warning looks like this:

Validate Bicep config during CI/CD with Azure DevOps

Bicep scripts are ideally part of the source code and can also be used as such in the build process of the application.

What's Bicep on Azure and why you should use it?

To generate resources automatically in Azure, you could either do Azure Resource Manager templates, which no one really wanted to do because they are far too complex and clumsy - or use third-party solutions Terraform and Pulumi.