AZDO.1021: Creation of classic release pipelines.
| ID | AZDO.1021 |
| Severity | Medium |
| Suite | Mito |
| Product | Azure DevOps |
| Feature | Pipelines |
| Security area | Engineering systems |
| Resource type | Tenant |
| User impact of fixing | Medium |
| Effort to fix | Low |
| Reads from | Azure DevOps |
| Further reading | https://devblogs.microsoft.com/devops/disable-creation-of-classic-pipelines/ |
What this checks and how to fix it
Section titled “What this checks and how to fix it”Creating classic release pipelines should be disabled.
Rationale: YAML pipelines offer the best security for your Azure Pipelines. In contrast to classic build and release pipelines.
Remediation action:
Section titled “Remediation action:”Enable the policy to disable creation of classic release pipelines.
- Sign in to your organization.
- Choose Organization settings.
- Under the Pipelines section choose Settings.
- In the General section, toggle on Disable creation of classic release pipelines.
Results: How the feature works If you turned on the toggle to Disable creation of classic build and classic release pipelines, then no classic build pipeline, classic release pipeline, task groups, and deployment groups can be created.
The user interface will not show the Releases, Task groups, and Deployment groups left-side menu items if you have none of them.
Existing classic pipelines If you have classic build pipelines, classic release pipelines, task groups, or deployment groups, you’ll still be able to edit and run them. The Pipelines left-side menu will continue to show the corresponding menu items. However, the buttons to create new ones will be disabled.
Related links
Section titled “Related links”Mito check. Author: SebastianClaesson. Open-source licences.
Open-source licences. CIS Benchmark material © Center for Internet Security, Inc.; CISA SCuBA baselines are public domain (CC0).
© 2026 Virtual Petals. Mito is a Virtual Petals service, hosted in Microsoft Azure UAE North.