Azure Verified Modules - Monthly Update [June]
AVM Module Summary
The AVM team are excited that our community have been busy building AVM Modules. As of June 17th, the AVM Footprint currently looks like:
|
Language |
Published |
In development |
|
Bicep |
214 |
49 |
|
Terraform |
44 |
24 |
Bicep Resource Modules Published in June:
Full list of Bicep Resource Modules is available here: AVM Bicep Resource Index
| avm/res/portal/dashboard |
| avm/res/kusto/cluster |
| avm/res/hybrid-compute/machine |
| avm/res/alerts-management/action-rule |
Bicep Pattern Modules Published in June:
Full list of Bicep Resource Modules is available here: AVM Bicep Pattern Index
| avm/ptn/lz/sub-vending |
General Bicep Updates
- There are currently 36 Bicep modules proposed (actively being worked on or looking for owners).
- Providing documentation of Input Parameter usage has been in the documentation for some time. The provided examples are now also rendered into the readmes for modules. Module owners can simplify adopting modules to certain usage scenarios, like an Azure Queue for triggering a job.
Terraform Resource Modules Published in June:
Full list of Terraform Resource Modules is available here: AVM Terraform Resource Index
| avm-res-network-networkwatcher |
Terraform Pattern Modules Published in June:
Full list of Terraform Resource Modules is available here: AVM Terraform Resource Index
| avm-ptn-network-private-link-private-dns-zones |
| avm-ptn-network-routeserver |
General Terraform Updates
- There are currently 115 Terraform modules proposed (actively being worked on or looking for owners).
General AVM Site Updates
- TF Module review process – New article created to detail the steps of the mandatory initial review of Terraform modules. This guides modules owners through the process of the initial code review that needs to take place prior to publishing a new Terraform modules. (ref)
That's A Wrap!
Well folks! That's it from Azure Verified Modules Team. If you missed the update from last month, you can find that here AVM - May Updates Blog. Other than that, as always, we want to say a massive thank you to our community and our teams continued efforts to develop and collaborate.
Published on:
Learn moreRelated posts
Shrinking Azure Pipeline task extensions using esbuild
TL;DR We bundled an internal Azure Pipelines task extension into a single bundled JavaScript file using esbuild. The task package dropped from...
Building on Vercel’s eve + Azure Cosmos DB: An Agent That Remembers
Most “AI agent” demos forget everything the moment the process exits. That’s fine for a toy project, but useless for anythin...
Copilot Studio – Environment-level agent telemetry export to Azure Application Insights (Preview)
We are announcing the ability for administrators to export Copilot Studio agent telemetry at the environment level to Azure Application Insigh...
See our new Azure Cosmos DB Design Patterns
Design patterns are where good data modeling lives or dies. In a NoSQL database like Azure Cosmos DB, the difference between a schema that sca...
Need a different partition key in Azure Cosmos DB? Pick the right approach
Once you create a container, its partition key is fixed at creation, and you can’t change it in place. However, if your original key starts ca...
Azure SDK Release (June 2026)
Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (June 2026) ap...
Fundamentals of Azure DevOps with SQL projects
Building automated pipelines with your SQL database projects enables you to build a rich CI/CD ecosystem to ensure that your application is be...