Hygiara
Sign In
Documentation / Getting Started

Getting Started

First Review

The quickest path from an empty workspace to a completed Azure review and report.

What this page is for

This is the end-to-end guide for getting one useful review through the system.

The goal of the first review is not to model every possible setup. It is to prove that:

  • the customer is in the right place
  • Azure access works
  • the review completes
  • the report is generated

When to use it

Use this page when:

  • the workspace is new
  • you are onboarding a customer for the first time
  • you want to prove the flow before adding more structure or more options

How to do it

1. Create the customer

Create the customer first. In Hygiara, reviews and reusable connections belong to a customer. If you skip that mental model, the rest of the workflow feels strange.

2. Choose the authentication path

For the first run, use whichever path gets you to a credible result fastest:

  • use a stored Azure connection if this customer will be reviewed again
  • use an access token if you want a quick one-off run without storing reusable access

3. Queue the review

Open New Review from the dashboard, the customer page, or the reviews page.

The stepper will walk you through:

  1. customer
  2. authentication
  3. connection or token
  4. subscriptions when a stored connection is used
  5. options
  6. confirmation

For the first run, keep the scope and options simple unless you already have a reason to do otherwise.

4. Wait for the scan and report

Large environments can take time. While the review is queued or running:

  • the review page shows a waiting state
  • the results tabs are not final yet
  • the report is not ready yet

5. Check the completed review

Before downloading the report, confirm:

  • the correct customer
  • the correct subscriptions
  • results that look plausible for the environment

6. Download the report

Use Download Report from the review page once the report is ready.

What to expect

The first good outcome is not “everything scored well.” The first good outcome is that the workflow behaves as expected from start to finish.

Common mistakes

  • queueing a review before checking what Azure access is being used
  • assuming queued means the system is broken
  • expecting token mode to show a subscriptions step
  • trying to tune every option before the first basic run succeeds

Next step