AVD Assessment Portal

Collect the inventory

Run one read-only command, then paste its output here.

For Cloud Shell, PowerShell

Collect and pseudonymize

Paste everything from the command to the last line

Read in this browser. The paste itself isn't saved.

What the command does

The collector reads what is in your subscriptions through Resource Graph and writes an evidence package in Cloud Shell. Then the facts script gives the estate a pseudonym, which the later steps use instead of any name. Both only read. Run each command in Azure Cloud Shell and paste the output back: nothing you paste or type leaves this page unless you send a report yourself.

Running it on a schedule? Check the optional reader

An optional read-only identity lets GitHub Actions in your private repo run the collector with nobody signed in. Set it up from the reader guide; this check only reads.

Check the reader

Residency and regions

Where the estate's data must stay, and where you would like it.

Data must stay in named regions
Regulation or contract, not preference.

Regions data must stay in Preferred regions, most preferred first (up to 3)

notes

Where the answers go

The discovery interview asks what telemetry can't know. The answers become intake.json (avd-intake/v1), which holds only choices, region names, times and the estate pseudonym. Private notes go in a notes file that stays on your device.

Network and identity

The network the landing zone joins, and the identity it is held to.

The network the landing zone has to join notes The identity lane the estate is held to notes

Working hours

When most users start and finish, and on which days.

Most users start Most users finish Time zone

notes

Users and use cases

Note who works on the estate and what hurts today, then build intake.json.

notes on users and use cases notes, anything else

Default network kind for imported user checks Load avd-linecheck JSON (optional)Drop one or more user network and sentiment exports. Banded in your browser, never uploaded.

EstateFilled in from the Collect step. Answered on

Download discovery notes

About the notes and intake.json

Notes only for now; the structured use case record comes with avd-assess's discovery guide. Importing avd-linecheck exports folds banded user ratings, symptom chips and per-network reachability into intake.json (with zero free text). The block writes intake.json beside the evidence packages, where the validator reads it.

Analyze against the standards

Run the read-only validator, then paste its output here.

For Cloud Shell, PowerShell

Validate

Paste everything from the command to the last line

Read in this browser. The paste itself isn't saved.

What the validator checks

The validator checks every host pool after deployment: wiring, app group access, session host health, profile storage, scaling, diagnostics and backup. Scoring against the avd-assess method, with intake.json, joins this step when the validator's assess mode lands.

Review the findings

Load assessment.json, then decide each finding: fix, accept or defer.

Load assessment.jsonDrop it here or choose it. Read in your browser, never uploaded. Earlier review.json (optional)Carries forward the decisions whose outcome didn't change, marked for a second look.

As-is architecture & network diagram

Generated from your Assessment Report (assessment.json, C21) findings and Discovery Intake (intake.json, C19) answers across all five control planes and four Azure architecture zones.

Export SVG (.svg) Export Mermaid (.mmd) Export Draw.io (.drawio)

Hide passing checks Reviewed on

Findings, worst first
Check	Outcome	Decision	Reason	Review by	Private note

Download notes with findings

What review.json holds

The decisions become review.json (avd-assessment-review/v1), which pins the report by its hash and holds only check IDs and reason codes. A note on a finding goes to your private notes file. The block writes it beside the evidence packages.

Plan the remediation

The findings to fix become an ordered plan you can download.

Load assessment.json in the Review step first.

Planned on

The plan, in priority order: gap, warn, unknown; then severity
Order	Plane	Check	Outcome	Change	Why

What goes into the plan

The findings you chose to fix, and every finding nobody reviewed, become an ordered plan: what good looks like and why, the landing zone parameter or setting that changes it where one is known, and what is outside the landing zone's reach. Accepted and deferred findings stay out. Saved as plan.json (avd-remediation-plan/v1), which holds only check IDs, citations and public values, and plan.md for people.

A landing zone change fixes only what the landing zone deployed. A finding on a resource it doesn't own is changed where that resource is managed.

Assessment settings

Report a problem

AVD assessment portal