Teams that manage Azure through the portal or with scripts often cannot repeat a deployment exactly or review a change before it happens.

This session teaches the fundamentals of Bicep to people who are new to infrastructure as code. I am a product manager at Microsoft on Azure Bicep and owning Deployment Stacks.

Bicep is Azure's native infrastructure as code language, and it is stateless, so there is no state file to manage.

In the demo I write a Bicep file in VS Code, use IntelliSense and the linter to catch mistakes as I type, and deploy it with the Azure CLI. I then use Azure Verified Modules, which provide ready-made Bicep modules for common resources, and deploy the environment as a deployment stack, which manages a group of resources as a single unit.

Before each change, Stacks What-If shows exactly which resources will be created, modified, or deleted, and deny settings block deletes made outside the stack.

The result is a first Bicep deployment you can repeat, review, and build on. Everything runs live from VS Code and the Azure CLI.

What attendees will learn: - How to write and deploy a Bicep file in VS Code with the Azure CLI. - How Azure Verified Modules provide ready-made Bicep modules for common resources. - How a deployment stack and Stacks What-If let you see and control every change to an environment.

[eventID:27814]