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.

0005. Bicep with pinned Azure Verified Modules, following avd-landing-zone

proposedReviewed 2026-10-18Source: decisions/0005-bicep-with-azure-verified-modules.md

Context and Problem Statement

The family's guardrails prefer Azure-native, GitHub, HashiCorp and open-source tooling, and the reference kit uses Terraform. This project deploys a handful of Azure resources at subscription scope, often next to an AVD landing zone built with Bicep. Which infrastructure-as-code tool fits?

Considered Options

  • Bicep with pinned Azure Verified Modules, following avd-landing-zone's conventions
  • Terraform with the azurerm provider, like nerdio-hcl

Decision Outcome

Chosen option: "Bicep with Azure Verified Modules", because it's Azure-native, needs no state file or backend, runs from Cloud Shell as is, and matches the landing zone the assessed desktops usually sit in.

Consequences

  • Good, because there's no state to store or protect, and what-if previews come free.
  • Neutral, because Bicep is Azure-native, which the guardrails list alongside HashiCorp.
  • Bad, because Terraform users of the family can't reuse these modules directly.

More Information

The Terraform choice for Nerdio is nerdio-hcl 0001.

Linked from one page