azure-adr

You can document Azure architecture decisions by generating formal Architecture Decision Records that map choices to WAF pillars, capturing context, alternatives, and consequences for each significant infrastructure decision.

An Architecture Decision Record (ADR) is a formal document capturing significant architectural decisions. You need one for Azure infrastructure when making impactful design choices, such as selecting Cosmos DB over SQL DB, to ensure rationale and trade-offs are recorded.

No, generating Infrastructure as Code like Bicep or Terraform is not supported. The Azure ADR focuses strictly on documenting architecture decisions, WAF pillar justification, and trade-off analysis rather than producing deployment code or diagrams.

No, cost estimates are not generated. While the Architecture Decision Record includes cost trade-offs within its WAF pillar analysis, it focuses on documenting the decision rationale and consequences rather than calculating specific financial estimates.

The best way to analyze trade-offs between Azure Cosmos DB and Azure SQL is to create a design ADR that evaluates each option against Well-Architected Framework pillars, formally documenting the context, alternatives, and consequences of your decision.

You can use it for both design and as-built phases. The formal ADR creation supports documenting architectural decisions whether you are planning future Azure infrastructure or recording what has already been implemented.