avd-opsavd-swarm
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.
On top: the how of operating. Agents that manage Azure and Entra ID without the portals. They read freely and change nothing until a person approves the exact plan.
The repo is the source of truth: nickprignano/avd-swarm. This page says where it fits.
What it does
- A coordinator hands questions to specialist agents: readiness, deploy, hosts, images, users and cost.
- Writes go through plans approved in GitHub Environments, with one layered kill switch only the owner resets.
- The write path never runs in the public repo; adopters run it from a private repo synced from a release tag.
- Today only the S1a spike runs. Everything after the first two write actions is designed, not scheduled.
How it fits
- Gets estate facts only from avd-second-brain, as cited C11 and C12 evidence, and re-reads live state before any change.
- Changes together with avd-second-brain (decision 0003).