Documentation / Getting Started

Getting Started

Overview

What Hygiara is for, what a review produces, and how the main workflow fits together.

What Hygiara does

Hygiara turns an Azure environment from "we think there are issues" into a structured review with evidence-backed findings and a report you can use outside the app.

It sits between raw scan output and manual reporting — combining Azure resource checks, landing zone structure checks, and report generation so the result reads like a considered review rather than a flat control list.

The normal workflow

  1. Create a project for the client or Azure estate you are reviewing.
  2. Add a saved Azure connection, or use Microsoft sign-in or a one-off access token for a quick run.
  3. Queue the review and let it run.
  4. Check the completed review — Resource Scores, Findings, and any Landing Zone Scores.
  5. Open the Report tab and download the generated report or reports.

Hygiara dashboard

What a completed review gives you

  • Pillar scores across the five Azure Well-Architected Framework pillars (Reliability, Security, Cost Optimization, Operational Excellence, Performance Efficiency)
  • Findings tied back to Azure evidence
  • The specific subscriptions included in scope
  • Optional Enterprise Scale Landing Zone assessment results
  • Downloadable Word reports for the assessments that were selected

The three main objects

Everything in the app is organised around three things:

  • Projects — the parent for a client or estate. Review history, templates, schedules, and reports live here.
  • Reviews — where execution status and results live. Each review belongs to a project.
  • Reports — the final output of a completed review. Downloadable from the review page.

Common mistakes

  • Treating the app like a flat scanner dashboard — it is workflow-driven, not menu-driven
  • Skipping the project step and wondering where to find review history later
  • Trying to understand every page before running a first review

Next step