Bicep Best Practices

Keep Bicep interfaces small, derive stable configuration close to its source, and prove each change with compiler and deployment-preview evidence.

Minimize parameters

Before adding a parameter, inspect every caller and ask why the value varies. Keep it only when callers legitimately supply different values that cannot be derived from stable inputs or shared environment facts.

• Derive predictable resource names from a small identity such as application, environment, and region.
• Put genuinely environment-specific input values in parameter files.
• Read facts shared by every deployment in an environment from one typed configuration object or module.
• Avoid forwarding a parameter unchanged through layers merely to reach a leaf module.
• Retain an explicit override only for a documented, real exception.

Centralize repeated derivations once:

param environment string
param workload string