Documentation / Reviews

Reviews

Review Details

How to read the review page once a scan is queued, running, or complete.

What this page is for

This page explains how to use the review details page once a review exists, especially after it completes.

When to use it

Use the review page when you need to:

  • confirm what was reviewed
  • inspect the results
  • understand whether Landing Zone assessment was included
  • download generated reports

How to use it

While the review is running

A progress stepper shows the current stage during execution:

  1. Waiting for worker — queued, waiting to be picked up
  2. Getting information — discovering subscriptions and resolving Azure credentials
  3. Processing information — running Azure resource checks, scoring findings, and generating AI analysis
  4. Generating report — compiling results into downloadable Word reports

The page refreshes automatically while active.

Start with the page header and run context

Read the top of the page first. It tells you:

  • the project
  • the connection source
  • the credential method
  • the subscription scope
  • whether Landing Zone assessment was included
  • whether the review completed

If that information is wrong, the rest of the tabs are less useful.

Read Resource Scores first

This is usually the first results tab worth opening. It has two views:

  • Overview — pillar scores across the five Azure Well-Architected Framework pillars (Reliability, Security, Cost Optimization, Operational Excellence, Performance Efficiency). Click a pillar row to filter directly to findings in that pillar.
  • Findings — the full findings table with search, Severity and Pillar filters, and sortable columns (Type, Finding, Pillar, Resources, Severity). Click any row to open the finding modal.

The finding modal

Click any finding to open a detail panel with three tabs:

  • Overview — what the finding is, why it matters, and a link to the relevant Microsoft documentation
  • Remediation — numbered step-by-step guidance and Azure CLI command templates to fix the issue
  • Resources — the specific Azure resources affected, with subscription and resource group

Use Landing Zone Scores when Landing Zone assessment is enabled

If Landing Zone assessment was turned on, this tab (marked Preview) gives you a second lens on the estate: platform and landing-zone alignment rather than just resource posture. Each pillar includes a tooltip explaining what that pillar covers.

Landing Zone Scores tab

Use Subscriptions to confirm scope

Use the Subscriptions tab before making broad claims about the estate, especially in larger environments.

Save repeatable work as a template

If this review used a stored Azure connection and the scope now feels right, save it as a template from the page header.

That is the right move when you want to:

  • rerun the same review shape later without rebuilding it
  • hand the same project setup to someone else on the team
  • attach a recurring schedule from the project workspace

Use Report as the final output

The Report tab tells you whether report generation is still running or ready. Once ready, use this tab to download the available report outputs.

The main output is the Well-Architected Resource Assessment report. If Landing Zone assessment was included and generated successfully, a separate Enterprise-Scale Landing Zone Assessment report download is also available on this tab.

Report tab

What to expect

While the review is still queued or running, the page shows the processing progress stepper instead of results. Once the review completes and report generation is finished, the Report tab shows the ready downloads.

Common mistakes

  • jumping straight to findings without confirming scope
  • assuming Landing Zone assessment is a replacement for the normal resource review
  • treating the report tab as separate from the rest of the page rather than the final stage of the same workflow

Next step