Automated Code Linting in Azure DevOps

4 posts · Jul 2016 – Aug 2026

What this trail covers

Azure Pipelines supports automated code linting through MegaLinter integration, enabling code consistency checks for various file types (PowerShell, ARM, Bicep, JSON, YAML, Terraform, Markdown) via Pull Request analysis. This allows for parallel linting, parallel linter execution, and direct feedback within PRs, aiming to enforce coding standards and improve code quality. This post adds integration for Lighthouse API for performance monitoring and Axe-Core for accessibility monitoring within CI/CD pipelines. Copilot Code Review for Azure Repos is now in public preview, offering automated code reviews with customizable instructions, support for managed DevOps pools, and improved billing visibility.

All Microsoft trails

Aug 2026Copilot Code Reviews for Azure Repos (public preview)Introduces GitHub Copilot Code Review for Azure Repos in public preview. Enhancements include organization, project, and repository-level enablement, support for Managed DevOps Pools (using Azure Pipelines), custom instructions for defining code standards, automatic code reviews via branch policies (including for draft PRs), and project-level cost attribution in Azure Cost Management. Future features include viewing logs for failed reviews and configurable Lite/Balanced review levels.
Sep 2023Achieve Code Consistency: MegaLinter Integration in Azure DevOpsThis post details a solution for implementing MegaLinter in Azure DevOps by creating a central repository with a pipeline and configuration files. This pipeline is invoked via branch policies whenever a Pull Request is submitted for any repository, cloning the source repository, identifying modified files, and reporting results back to the PR. The solution leverages MegaLinter's ability to run linters in parallel and incorporate linting results as comments in PRs.
Feb 2021Continuous Monitoring for Web Performance and AccessibilityThis post introduces the integration of Lighthouse API for web performance monitoring and Axe-Core for accessibility monitoring into Azure Pipelines. It demonstrates how these open-source tools can be used within CI/CD pipelines to prevent performance regressions and common accessibility bugs from reaching production, specifically in the context of the Azure Cloud Collaboration Center.
Jul 2017Human readable tests and build chaining in July's VSTS extension round-upThis post introduces two new extensions for Azure DevOps: SpecFlow+LivingDoc, which generates living documentation from Gherkin feature files for better stakeholder understanding and accessibility, and Trigger Build Task, which allows chaining build definitions together with customizable options for triggering other builds based on specific criteria.
Jul 2016Gradle build task now also supports PMD analysisThis post introduces support for PMD static analysis within the Gradle build task in Azure Pipelines. A new 'Run PMD Analysis' checkbox is added to the Gradle build task, instructing Gradle to perform PMD static analysis. The build summary will report the number of issues found, and detailed logs will be available in the build artifact tab. The default set of PMD rules (basic and bracing rules) will be used, with encouragement for users to specify other rules in their Gradle scripts. Existing PMD configurations will be respected.
Advertisement