First Review

What this page is for

This is the shortest path from a new workspace to a useful Azure Well-Architected review and downloadable report.

The goal is not to model every possible setup. It is to prove that Azure access works, evidence can be collected, and the first report can be downloaded.

The dashboard keeps this path visible until the first report is downloaded.

Step 1 — Create the project

Projects are the parent object for reviews and reports. Create one before you queue the first review.

1. Open the dashboard.
2. In Path to first report, click Project or use the Create project next action.
3. Give the project a recognisable name, such as "Contoso Corp" or "Internal Platform".
4. Click Create Project.

After the project is created, Hygiara returns you to the dashboard and advances the guide to the connection step.

Step 2 — Add the Azure connection

Connections are reusable Azure credentials for the organization. A review only uses a connection after you select it in the review flow.

1. From the dashboard guide, click Connection or Add connection.
2. Enter a friendly name, Tenant ID, Client ID, and Client Secret.
3. Click Next.
4. Hygiara validates the credentials and shows accessible subscriptions.
5. Configure continuous scanning only if you want scheduled weekly scans.
6. Confirm and save the connection.

After the connection is saved, the guide moves to the review step.

Step 3 — Start the first review

1. From the dashboard guide, click Start review or Start first review.
2. Select the project you just created.
3. Choose the Azure access method. For the first run, the saved connection is usually the simplest option.
4. Select the saved connection or provide one-off access details.
5. Choose subscriptions when the selected access method supports subscription selection.
6. Keep Well-Architected resource assessment enabled for the main report.
7. Choose a WAF rule set. For the first run, the all-rules option is usually the clearest baseline.
8. Enable Landing Zone assessment if you want platform guardrail checks included.
9. Confirm the summary and click Queue Review.

The review appears in the list with a Queued status.

Step 4 — Wait for the review to complete

Large environments take longer. While the review is running:

• The review page shows the current status.
• Results tabs are populated after evidence has been parsed.
• The report is not yet available.

Typical run times are a few minutes for small environments and up to 15–20 minutes for large ones.

Step 5 — Check the completed review

Once the status changes to Completed:

1. Open the review from the project page or the Reviews list.
2. Check Resource Scores first.
3. Open Findings inside Resource Scores to see failed checks.
4. If enabled, check Landing Zone Scores for platform guardrail alignment.

Step 6 — Download the report

1. Open the Report tab on the review page.
2. Download the available Word report.
3. If Landing Zone assessment was enabled, download the separate Landing Zone report as well.

The dashboard first-report guide is dismissed only after a report is downloaded. That keeps the path focused on value, not just on completing a scan.

Common mistakes

• Queueing a review before checking what Azure access is being used
• Assuming Queued means something is broken — it just means the job is waiting to start
• Expecting token-based access to show a subscription picker; token mode uses the subscriptions available to the provided token
• Stopping at the completed review page without opening the Report tab and downloading the first report

Next step

• Project workspace
• Creating a review in detail
• Download reports
• Troubleshoot common problems