Reports
Understanding The Report
What the generated report is for, how it is structured, and how to use it well.
What this page is for
This page explains the intent of the report and how to read it as an output, not just as an export.
When to use it
Read this when:
- you want to know whether the report is good enough for stakeholder use
- you are preparing to share the output outside the app
- you want to understand what each section is trying to do
How the report is meant to be used
The report is designed to stand on its own in technical review and stakeholder readout.
In practice, that means it should:
- summarise the review clearly
- show where the main concerns sit
- give enough structure that someone can act on it
How it is typically structured
Most reports move from broad interpretation to detailed evidence:
- executive summary
- Azure estate overview
- domain review sections
- roadmap or implementation direction
- appendix material
What to expect
You should expect the report to reflect the review scope and options used, including ESLZ when that option was enabled.
It is not a substitute for judgment. It is the structured deliverable that comes out of the review workflow.
Common mistakes
- treating the report as a raw export rather than a delivery asset
- reading detailed findings before understanding the summary and scope
- assuming ESLZ content should appear in every report regardless of whether it was enabled