azure-verified-modules

To decide whether to reuse an Azure Verified Module, evaluate your required features, region constraints, and compliance needs against the AVM's README. A decision tree helps determine if reuse meets your needs or if a custom implementation is required.

Selecting a compliant Azure Verified Module involves identifying a suitable pattern for Key Vault or Storage, opening the AVM README to confirm feature parity, and providing a pinned version with rationale and implementation notes.

Yes, you can use Azure Verified Modules with strict region constraints by evaluating the module's supported regions and compliance features. The Skill checks these constraints against your requirements before recommending a pinned AVM version.

You need to pin a specific version when reusing an Azure Verified Module to ensure maintainability and stability. Version-pinning prevents unexpected breaking changes from upstream module updates in your infrastructure deployments.

You should avoid using an Azure Verified Module when the module's feature set lacks parity with your specific requirements, or when the decision tree indicates your region and compliance constraints necessitate a custom implementation.