Infrastructure as code
CoreBicep
Declarative Azure infrastructure language that compiles to ARM JSON.
Key points
- Bicep supports resource-group, subscription, management-group, and tenant deployments when the file and deployment operation target the same scope.
- Uses symbolic names and modules to make resource references and reuse clearer.
- Decompiler output from ARM JSON is a starting point that may need refactoring.
Best-known use cases
- Author readable repeatable Azure deployments.
- Convert an existing ARM JSON file into maintainable source.
What candidates often confuse it with
- Bicep vs ARM JSON: authoring abstraction vs native deployment representation.
- Module vs resource: reusable grouped deployment vs one declared Azure resource.
Key takeaway
Prefer Bicep for readable Azure-native authoring while remembering Resource Manager remains the deployment engine.
Related services
- Azure Resource Manager
- ARM templates
Relevant exam tasks
- D3.1.S1 — Interpret an Azure Resource Manager template or a Bicep file
- D3.1.S2 — Modify an existing Azure Resource Manager template
- D3.1.S3 — Modify an existing Bicep file
- D3.1.S4 — Deploy resources by using an Azure Resource Manager template or a Bicep file
- D3.1.S5 — Export a deployment as an Azure Resource Manager template or convert an Azure Resource Manager template to a Bicep file