Creation of classic build pipelines.

Why This Matters

Allowing unrestricted creation of classic build pipelines in Azure DevOps can lead to inconsistent build configurations, potential exposure of sensitive credentials, and reduced traceability in your CI/CD processes. Classic pipelines lack the same level of governance and templating capabilities as YAML-based pipelines, making it harder for administrators to enforce security policies and maintain audit trails. Without proper controls, users may inadvertently introduce vulnerabilities or bypass organizational security standards, increasing the risk of unauthorized code deployments or data breaches.

What Aether365 Checks

Aether365 verifies whether users in your microsoft-365 environment have permission to create classic build pipelines. This check appears in the Aether365 dashboard under the microsoft-365 security checks section.