What kinds of issues does the ARM Template Linter detect?

It detects missing required fields (like location or apiVersion), deprecated API versions, hardcoded secrets in parameters without secureString type, unused parameters and variables, missing tags, and common structural issues in resource definitions.

How is this different from the az deployment validate command?

The az deployment validate command checks that your template is valid JSON and references valid resource providers, but it requires an Azure connection. This linter checks for best practices, code quality, and common mistakes entirely offline in your browser.

Can I use this for Bicep files?

This tool is specifically for ARM JSON templates. For Bicep syntax formatting and validation, use the Azure Bicep Formatter tool.

ARM Template Linter

MonitoringAzure

Analyze Azure ARM templates for best practices, missing fields, and common issues.

ARM Template (JSON)

Raw Output

Output will appear here...

About This Tool

The ARM Template Linter analyzes Azure Resource Manager templates for best practices, missing required fields, and common issues. It checks for proper use of parameters, variables, and outputs, validates resource API versions, and flags security anti-patterns like hardcoded secrets. The linter runs entirely in your browser and provides actionable feedback with severity levels and suggested fixes, helping you catch problems before deployment.

When to Use This Tool

•Validate ARM templates before submitting a pull request to catch missing required fields and deprecated API versions.
•Audit existing ARM templates for security issues like hardcoded passwords or overly permissive network rules.
•Check that ARM templates follow organizational naming conventions and tagging requirements.
•Identify unused parameters and variables that add unnecessary complexity to your templates.

Frequently Asked Questions

What kinds of issues does the ARM Template Linter detect?: It detects missing required fields (like location or apiVersion), deprecated API versions, hardcoded secrets in parameters without secureString type, unused parameters and variables, missing tags, and common structural issues in resource definitions.
How is this different from the az deployment validate command?: The az deployment validate command checks that your template is valid JSON and references valid resource providers, but it requires an Azure connection. This linter checks for best practices, code quality, and common mistakes entirely offline in your browser.
Can I use this for Bicep files?: This tool is specifically for ARM JSON templates. For Bicep syntax formatting and validation, use the Azure Bicep Formatter tool.

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.