Reviews
Creating A Review
What each step in the review modal is for and how to use it well.
What this page is for
This page explains the review modal step by step — what each step does, what to expect, and what a successful pass through it looks like.
When to use it
Read this when:
- you are queueing a review for the first time
- a step in the modal feels unclear
- you want to understand why the flow changes between stored connections and token mode
How to open the review modal
Click New Review from:
- the top navigation bar (any page)
- the project page (pre-selects the project)
- the Reviews list page
Step 1 — Project
Choose the project this review belongs to.
If you launched the modal from a project page, this is already filled in. If you launched it generically, select the right project here — everything downstream (connections, review history) depends on it.
Step 2 — Authentication
Choose between:
- Stored connection — uses a saved organization-level Azure connection
- Access token — paste a one-off Azure Management API token
This step controls the rest of the flow. If no saved connections exist, use Microsoft sign-in or access token mode, or add a connection first.
Step 3 — Connection or token
With a stored connection: choose a saved connection from the organization-level connection list.
With an access token: paste a valid Azure Management API access token. Hygiara validates it against Azure before allowing you to continue — it is better to fail here than to queue a review that never had valid access.
→ See Access tokens for how to obtain the right token.
Step 4 — Subscriptions (stored connection only)
This step only appears for stored-connection reviews.
Use it to search through and select the subscriptions to include in scope. The list is populated from the subscriptions visible to the saved connection.
Token mode skips this step because all subscriptions visible to the token are included automatically.
Step 5 — Options
This is where review-level options live.
- Well-Architected resource assessment — runs the normal resource-level WAF checks and creates the main report.
- WAF Rule Set — selects which WAF checks run. The selector is searchable and shows whether a rule set contains all rules or a smaller custom set.
- Landing Zone assessment — adds platform guardrail checks and a separate Landing Zone report.
Leave Landing Zone assessment off for a first run until you know the basic resource review flow works.
Step 6 — Confirm
Review the summary:
- correct project
- correct authentication method
- correct subscriptions (if applicable)
- correct options
Reaching this step does not create the review. Clicking Queue Review does.
What to expect
The review modal is intentionally sequential. Each step unlocks the next. Once you have a shape you trust, save it as a template from the review details page so you do not have to rebuild it manually next time.
Common mistakes
- Picking the wrong project in a generic launch (the review history and reports will end up in the wrong place)
- Assuming token mode shows a subscription selection step — it doesn't
- Treating the Confirm step as decorative — it is there to stop accidental queueing
- Enabling Landing Zone assessment before the basic review flow has proved itself
- Changing the rule set without checking the Confirm step before queueing