Skip to main content

Automation for Microsoft Azures

Azure automation with ARM templates and Bicep is infrastructure as code: resources are described in a declarative file and deployed repeatably through Azure Resource Manager. Bicep is a cleaner language that compiles to ARM JSON. This unit begins the Compute stage and removes manual portal clicking from deployments.

Stage: Compute · Part of the Microsoft Azure roadmap · Last reviewed 19 November 2026

What to learn in Automation

Automation interview questions

What is the difference between ARM templates and Bicep?

Both are declarative and deployed by Azure Resource Manager. ARM templates are verbose JSON. Bicep is a concise domain-specific language that compiles into an ARM template, with better readability, modules and tooling support, and the same resource coverage.

What does the what-if operation do in Azure deployments?

What-if compares your template with the current state of the resource group and reports which resources would be created, modified or deleted, without changing anything. It is used to review impact before running a real deployment, particularly in complete mode.

Where Automation fits in the Microsoft Azure roadmap

Automation belongs to the Compute stage (intermediate level). Run workloads.

Back to the full Microsoft Azure roadmap