ARM / Bicep

Overview

We write Bicep, or ARM where you must stay with JSON, for the Azure resources this platform needs. Modules cover the repeated pieces, names and locations are parameters, and what-if is run before a production deployment.

We keep one subscription structure and a parameter file per environment. Existing portal resources are imported or rebuilt only after we have shown the difference, so a deployment does not recreate a storage account.

What we deliver

• Bicep modules and a main template for the platform resources
• Parameter files for dev and production
• What-if output reviewed before the production deployment
• A short guide to adding a resource without editing the template ad hoc

Business benefits

• Environments are created from the same modules with different parameters
• What-if shows a destructive change before it runs
• A new environment does not depend on someone remembering portal clicks