Azure / Azure/bicep

Request for Feedback & Ideas on Bicep Best Practices

Open
#17,660 5 comments 6 reactions 1 assignee Claimed by @emilyredm View on GitHub
documentation help wanted
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

**Summary:**
We're opening this issue as a space for the community to share, refine, and discuss Bicep best practices. The goal is to crowdsource your wisdom building with Bicep every day.

**Why we're doing this:**
As the Bicep ecosystem grows, having a shared understanding of "what good looks like" becomes more important.

**This will:**
- Inform features (like future AI/MCP tools, Bicep linter, etc.)
- Potentially shape future official documentation
- Help new and experienced users write cleaner, more maintainable Bicep

**Types of best practices:**
1. Authoring best practices – practices that improve readability, reuse, maintainability, or performance
2. Security best practices – practices that help protect sensitive data, avoid misconfigurations, or align with security standards
Other
🔖 If you can, please indicate whether your tip falls under "authoring", "security", or both!

**What we'd like to hear from you:**
- Share your own best practices or patterns
- Highlight anti-patterns or things you’ve learned to avoid
- Link to resources, examples, or blog posts you’ve found helpful
- Suggest things you think should be in a “Bicep style guide”

Thank you for your collaboration! 💪

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.