Reports
Understanding The Report
What the generated report contains and how to read it before sharing.
The generated report turns review results into a Word document for stakeholders, remediation planning, and delivery records.
What matters
The report reflects the review inputs:
- project
- subscription scope
- selected assessment options
- findings and scores available at generation time
If the review scope was wrong, the report will be wrong too.
Report structure
Executive summary
High-level findings, posture narrative, and priority themes.
Landing Zone section
Included only when Landing Zone assessment was enabled. It covers platform structure, governance, management groups, policy signals, and related controls.
Azure estate overview
Summarizes the assessed resource footprint and subscription scope.
WAF pillar reviews
Shows results across Reliability, Security, Cost Optimization, Operational Excellence, and Performance Efficiency.
Remediation roadmap
Turns findings into prioritized follow-up work.
Findings appendix
Lists detailed findings, affected resources, subscriptions, resource groups, impact, and remediation guidance.
Check before sharing
Open the report and confirm:
- project and date are correct
- table of contents is populated
- scope matches the agreed subscriptions
- Landing Zone content appears only when expected
- appendix entries have useful affected-resource context
Avoid
- reading resource names without checking subscription and resource group columns
- sharing a report before confirming the review scope
- treating generated text as final consulting interpretation without review