Reports
Understanding The Report
What the generated Word report contains, section by section, and how to use it well.
What the report is for
The report is the deliverable. It is designed to stand on its own in a technical review or stakeholder readout without requiring the recipient to have access to the app.
It is a Word document (.docx) generated from the completed review data.
Report structure
Cover page
Project name, review date, and the confidentiality banner.
Table of contents
Auto-generated. Useful for navigating longer reports with many findings.
Executive summary
A narrative summary of the review — what was assessed, what the headline findings are, and what the overall posture looks like across domains. This is usually the first section a non-technical stakeholder reads.
Landing Zone section (if enabled)
Only present when Landing Zone assessment was turned on for the review.
Shows the Landing Zone assessment results: pillar scores, passed and failed checks, and any partial or not-verified states. Each result includes the check description and the evidence state.
Azure estate overview
A breakdown of what was found in the Azure environment: resource counts by type, subscription summary, and an infrastructure topology overview showing the resource shape across the estate.
WAF pillar reviews
One section per Azure Well-Architected Framework pillar:
- Reliability — availability configuration, disaster recovery, backup, health checks, SLA alignment
- Security — identity and access, network controls, data protection, encryption, threat detection
- Cost Optimization — resource sizing, reserved capacity, idle or orphaned resources, spend visibility, and cost-related Azure Advisor evidence when available
- Operational Excellence — monitoring, alerting, diagnostic settings, automation, tagging hygiene
- Performance Efficiency — scalability, load testing, capacity management, and health monitoring
Each pillar section has a score, a narrative summary of what was found, and the findings for that pillar.
Remediation roadmap
Prioritised recommendations grouped by urgency (P1 through P4). This section is the action list — it tells the reader what to fix and in what order.
Findings appendix
The full list of findings across all pillars, with evidence and remediation guidance per finding. This is the detailed reference section for the technical team.
Each detailed finding includes an Impact Scope summary and an Affected Resources table. The affected resources table keeps the resource name, subscription, and resource group aligned together so a resource can be traced back to where it lives. Findings that span multiple subscriptions or resource groups are shown in the same table rather than split into separate subscription and resource group lists.
Very large findings may show a capped list in the Word document with a +N more resources not shown note. Use the review page in the app when you need to inspect the complete resource list.
Glossary
Definitions for terms used throughout the report.
What to expect
The report reflects exactly what was reviewed — the project, the subscriptions in scope, and whether Landing Zone assessment was enabled. If those inputs were wrong, the report will reflect that.
Check the review scope on the review details page before downloading.
Common mistakes
- Sharing the report before checking the subscription scope is correct
- Reading the Findings appendix before the Executive summary and domain scores
- Assuming Landing Zone content appears in every report — it only appears if Landing Zone assessment was enabled for that review
- Reading affected resource names without checking the subscription and resource group columns beside them