Member-only story
TECH BASICS
Introduction to Azure Bicep: Part 1
Azure | Cloud | IaC | DevOps | Automation
What is Azure Bicep?
The role of Infrastructure as Code (IaC) is to provide a consistent and repeatable way to define and manage infrastructure resources in a cloud environment. Azure Bicep is another solution from Microsoft or I can say improved solution on top of ARM templates. It is an open-source domain-specific language (DSL) for authoring Azure Resource Manager (ARM) templates. Bicep is designed to simplify the authoring experience for ARM templates, making it easier for developers to deploy and manage Azure resources. It uses a simplified syntax that is closer to the way that resources are described in the Azure portal, and supports a wide range of Azure resources and resource types.
A domain-specific language (DSL) is a programming language or specification language that’s tailored to a particular application domain. DSLs are designed to be easy to read and write for people who are working in that specific domain, and to express concepts and constraints that are common to that domain.
Azure Bicep was released in August 2020 and since then there have been many releases.
How Bicep Works?
Bicep files are written in a declarative style, where you define the desired state of your infrastructure resources, rather than specifying the step-by-step instructions to create them. When you run a Bicep file, it compiles into an ARM template that can be deployed to Azure.
Work with Bicep?
- VS Code with Bicep extention
- Azure CLI
Read more — Set up Bicep development and deployment environments — Azure Resource Manager | Microsoft Learn
How to deploy Bicep file?
Let’s take a quick example of creating a storage account. Mainly a bicep file is organised in following section -
