liquidware-ninjaSecond brain & toolkit
Personal project. Research and learning only. Not for production. No warranty.Not for production
  • Built on my own time for research and learning. Not affiliated with, endorsed by or supported by my employer, Liquidware or Microsoft.
  • Bring your own Liquidware licenses. Don't run any of it in production or against tenants and subscriptions that matter. Test in a dedicated lab first.
  • Provided "as is", without warranty of any kind, under each repository's license. You use it at your own risk and own the Azure charges it incurs.
  • Contributions and forks are welcome and encouraged on public repos. See Contribute.

avd-liquidware

Automation for running Liquidware products in Azure: Stratusphere UX for assessments, and an optional tier for Azure Virtual Desktop (ProfileUnity for profile portability and UEM, FlexApp packages through AVD App Attach, and CommandCTRL for support) deployed against an existing avd-landing-zone estate while keeping FSLogix as the primary profile container.

Public · MITBicep (AVM)PowerShellAzure Cloud ShellEntra Kerberos

What It Does

  • Stratusphere UX in Azure (stratusphere/): Subscription/network preflight checks, Azure Marketplace Hub, Database, and Collector appliance deployment, Connector ID Key rollout across session hosts via Azure Run Command, and safe teardown that enforces the family's never delete the last copy rule.
  • ProfileUnity & FlexApp Tier in Bicep (profileunity/bicep/main.bicep): Subscription-scoped Bicep deploying rg-<base>-liquidware, spoke VNet peering, Private DNS zone links, Key Vault, Premium Azure Files shares (lwconfig, portability, appattach) with allowSharedKeyAccess: false and Entra Kerberos, and the ProfileUnity Management Console VM.
  • Two-Step Configuration Promotion & App Attach Registration (scripts/): Deploy-LiquidwareTier.ps1, Managed Identity blob staging to on-demand ACI file-share promotion, and operator-registered AVD App Attach without storing standing Entra client secrets on the console VM.
  • Red-Teamed Specifications (docs/): Detailed architecture specifications (docs/spec.md and docs/deploy-spec.md) defining product ownership boundaries, RBAC per path, cost controls, and security reviews.

Try It in Azure Cloud Shell

if (-not (Test-Path ~/avd-liquidware)) { git clone https://github.com/nickprignano/avd-liquidware.git ~/avd-liquidware }
Set-Location ~/avd-liquidware; git checkout -q main; git pull -q --ff-only
Invoke-Pester -Path ./tests -CI

Repository on GitHub Tier Architecture Spec Deployment Spec Fit with AVD & FSLogix