DEV.co
Open-Source Testing · Azure

ResourceModules

ResourceModules is a curated library of Bicep and ARM template modules for Azure infrastructure deployment, maintained by Microsoft. The project has transitioned to Azure Verified Modules (AVM) and is no longer receiving updates in this repository.

Source: GitHub — github.com/Azure/ResourceModules
736
GitHub stars
436
Forks
PowerShell
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
RepositoryAzure/ResourceModules
OwnerAzure
Primary languagePowerShell
LicenseMIT — OSI-approved
Stars736
Forks436
Open issues121
Latest releasev0.11.1 (2023-09-20)
Last updated2025-08-28
Sourcehttps://github.com/Azure/ResourceModules

What ResourceModules is

A collection of reusable Bicep/ARM modules covering 50+ Azure resource types, with integrated CI/CD pipelines for GitHub Actions and Azure DevOps. Modules include validation, testing, and versioned publishing; the codebase is primarily PowerShell-driven for orchestration.

Quickstart

Get the ResourceModules source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/Azure/ResourceModules.gitcd ResourceModules# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Enterprise Azure deployments with standardized modules

Organizations needing consistent, pre-tested Bicep modules for common Azure resources (VMs, storage, networking, databases) can use these curated building blocks to accelerate IaC adoption.

CI/CD pipeline templates for Bicep validation

Teams can reference the integrated GitHub Actions and Azure DevOps pipeline configuration for their own module validation, testing, and publishing workflows.

Learning reference for Bicep best practices

Developers new to Bicep can study the module structure, parameter naming conventions, and deployment patterns established in this mature codebase.

Implementation considerations

  • Verify which modules have been transitioned to AVM; consult the AVM Module Index and BRM repository for current versions and documentation.
  • Ensure your environment runs latest versions of PowerShell, Bicep CLI, and GitHub Actions/Azure DevOps agents; older tooling may cause unexpected failures.
  • Review parameter naming and 'standard interfaces' (diagnostic settings, RBAC) for differences between CARML and AVM versions if migrating.
  • Test module deployments in a non-production environment first; architectural decisions and outputs may differ from internal documentation.
  • Plan for eventual migration from ResourceModules to AVM; this repository will not receive updates going forward.

When to avoid it — and what to weigh

  • You need active bug fixes or new features — This repository is in transition to AVM and no longer receiving updates. New module improvements and fixes go to the AVM Bicep Repository (BRM) only.
  • You require modules not yet migrated to AVM — Some ResourceModules were retired without AVM equivalents. Capabilities may have been refactored; migration paths are not guaranteed.
  • You need guaranteed long-term support — CARML/ResourceModules is a transitional project. Microsoft explicitly directs new work to AVM, making this a legacy codebase for long-term commitment.
  • Your toolchain requires the latest Bicep CLI or PowerShell — Last push was August 2025 but no release since September 2023 (v0.11.1). Tool compatibility with current versions is unclear without testing.

License & commercial use

MIT License (permissive OSI-approved license). Allows commercial use, modification, and distribution with attribution and no warranty.

MIT License permits commercial use. However, no warranty or support is provided. Since this is a transitional project no longer receiving updates, commercial use should be paired with a plan to migrate to AVM or maintain modules independently.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceStale
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitPossible
Assessment confidenceHigh
Security considerations

Modules implement Azure best practices (RBAC, diagnostic logging, encryption parameters) but no formal security audit or vulnerability disclosure process is documented. Transitional status means security updates are unlikely in this repository; rely on AVM for current security guidance. Review each module's RBAC and network configuration before production use.

Alternatives to consider

Azure Verified Modules (AVM) - Bicep modules

Direct successor to ResourceModules with active maintenance, published to Public Bicep Registry, and continued Microsoft investment. Use this for new projects.

Terraform Registry / Terraform Azure Provider modules

If you prefer Terraform over Bicep, offers similar curated modules with broader community support and active maintenance.

Azure Quickstart Templates (azure-quickstart-templates)

Community-driven collection of templates; less curated than ResourceModules/AVM but may cover niche scenarios and receive community contributions.

Software development agency

Build on ResourceModules with DEV.co software developers

ResourceModules is no longer maintained. For new Azure IaC projects, adopt Azure Verified Modules (AVM) in the Public Bicep Registry for active support and Microsoft backing.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

ResourceModules FAQ

Should I use ResourceModules or AVM for new projects?
Use AVM (Azure Verified Modules). ResourceModules is deprecated; all new features and fixes go to AVM. ResourceModules is suitable only for reference or legacy systems already in use.
What happens if I file an issue in ResourceModules?
Microsoft will transfer it to the appropriate AVM repository (BRM for Bicep modules). Contributors are asked not to work on CARML; improvements will not be integrated.
Are all CARML modules available in AVM?
Most are, but some were retired. Capabilities may have been refactored into other modules. Check the AVM Module Index and BRM repository for the current module.
Can I use the CI/CD pipeline code from ResourceModules?
Yes, as a reference, but verify compatibility with current tool versions. AVM uses an updated CI platform; review it for your needs rather than copying legacy code.

Software developers & web developers for hire

From first prototype to production, DEV.co delivers software development services around tools like ResourceModules. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source testing and beyond.

Migrate to Azure Verified Modules

ResourceModules is no longer maintained. For new Azure IaC projects, adopt Azure Verified Modules (AVM) in the Public Bicep Registry for active support and Microsoft backing.