Azure Bicep Conventions and Best Practices

Follow these conventions when writing, reviewing, or refactoring Bicep templates to produce secure, maintainable, and idiomatic Infrastructure as Code.

File Structure

Organize every Bicep file in a consistent top-to-bottom order so readers always know where to look:

1. import statements (for shared types and functions from other files)
2. targetScope (if not the default resourceGroup)
3. metadata (optional -- file-level description)
4. type definitions (user-defined types)
5. func declarations (user-defined functions)
6. param declarations
7. var declarations
8. resource and module statements
9. output declarations