Getting Started
Overview
What Hygiara is for, what a review produces, and how the main workflow fits together.
What this page is for
This page gives you the shortest useful mental model for the product before you start clicking around.
Hygiara is built to turn an Azure environment from "we think there are issues here" into:
- a structured review
- evidence-backed findings
- a report you can use outside the app
It sits between raw scan output and manual reporting.
When to use it
Read this first if:
- you are new to the product
- you are trying to understand why customers, reviews, and reports are separated the way they are
- the rest of the UI feels fragmented and you want the workflow first
How the product works
The normal flow is:
- create a customer
- decide how the review will authenticate to Azure
- queue the review
- wait for the review and report to finish
- inspect the review details
- download the report
The product is designed around that sequence. Once you understand it, the navigation starts to make sense.
What a review gives you
A completed review gives you:
- domain scoring across the main architecture areas
- findings tied back to Azure evidence
- the actual subscriptions included in scope
- optional ESLZ results
- a downloadable Word report
What to expect
You should expect the product to feel workflow-driven rather than menu-driven. The most important objects are:
- customers: where review history and reusable access live
- reviews: where execution status and results live
- reports: the final output of a completed review
Common mistakes
- expecting the product to behave like a flat scanner dashboard
- treating customers as optional labels instead of the parent object for review history
- trying to understand every page before running a first review