Azure Virtual Desktop, from inventory to operations, as code you can read.
Five open-source repos that inventory an AVD estate, deploy a hardened landing zone, run it with agents a person approves, and remember what every deployment taught. Bicep and PowerShell, run from Azure Cloud Shell.
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, Liquidware 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.
How the pieces fit
Each repo owns one stage of the lifecycle. They pass versioned, redacted contracts to each other instead of sharing code, and the second brain sits under all of them.
Read-only PowerShell that answers what is in an AVD environment today, and whether a subscription is ready for a deployment and the deployment landed correctly.
An Azure Virtual Desktop landing zone for cloud-native organizations: Entra ID-joined, Intune-managed, private by default, deployed end to end from one Bicep template.
An optional Liquidware tier on top of a landing zone: ProfileUnity, FlexApp through AVD app attach, CommandCTRL, and Stratusphere UX for assessments. FSLogix stays the profile container.
Slice by slice
What they share
Read first, change with approvalCollectors and agents read freely. Every change to an estate goes through a plan a person approves, with a kill switch.
Tenant data stays with the tenantPublic repos hold generalized knowledge only. Estate data lives in the owner's private repo, and guards in CI catch leaks.
Every number traces to evidenceRules carry a history and a reason, sizing comes from measured observations, and answers cite a commit.
Azure-native and openBicep, PowerShell and GitHub Actions, all runnable from Azure Cloud Shell. Liquidware is the one partner product, as an optional tier.
Contribute
Contributions and forks are welcome and encouraged. Fork a repo and make it your own, or send back what you learn: an issue for a bug, a question or an idea, or a pull request with a fix, a test, a doc or a lesson from a real lab run. Small pull requests are easiest to review.
Before you open one, run the checks the repo's README lists and keep tenant data, IDs and secrets out of the repo, issues and pull requests. A change to a contract between repos comes with the matching pull request in the repo on the other side.