Last reviewed 2026-06-30
Direct answer
An Azure architecture review checklist should verify the source input, resource scope, cost exposure, security posture, reliability risks, evidence freshness, deployment readiness, and review handoff. Cloudeval can turn many of those checks into diagrams, reports, grounded answers, exports, and GitHub or CLI workflows.
Confirm the Azure scope, input type, source repository, and expected decision. A review is more useful when the team knows what will be accepted, fixed, or waived.
Inspect topology, dependency paths, architecture findings, cost findings, security signals, and evidence freshness before treating the output as decision-ready.
Capture the next action, owner, evidence, and follow-up run. A checklist should end with a decision, not just a dashboard screenshot.
No. It is a lightweight planning tool. A Cloudeval report attaches project-specific evidence and findings.
Not for the current Cloudeval support story. Keep this page Azure-first until product support expands.
