avd-opsavd-current-state
Personal project. Research and learning only. Not for production. No warranty.
- Built on my own time for research and learning. Not affiliated with, endorsed by or supported by my employer or Microsoft.
- Don't run any of it in production or against tenants that matter. Test in a dedicated lab subscription and tenant first.
- Provided "as is", without warranty of any kind, under each repo's license. You use it at your own risk and own the Azure charges it incurs.
- Contributions and forks are welcome and encouraged. See Contribute.
What is there now. Read-only PowerShell that answers what is in an AVD environment today, whether a subscription is ready for a deployment, and whether the deployment landed correctly.
The repo is the source of truth: nickprignano/avd-current-state. This page says where it fits.
What it does
- The collector builds a portable evidence package of the AVD workload and the platform around it.
- The validator runs preflight and post-deployment checks and writes a pass/fail report.
- Only
Get-andTest-calls against Azure. Nothing is created, changed or deleted. - The facts script turns packages into one redacted snapshot (contract C11): counts, public values and pseudonyms, no names or IDs.
How it fits
- Its C11 facts feed avd-second-brain; avd-swarm sees them only as cited evidence from the brain.
- The validator checks a avd-landing-zone deployment before and after.