# Creation of classic build pipelines

Creation of classic build pipelines. A Maester check for Azure DevOps, Pipelines.

Source: https://maester.dev/docs/tests/AZDO.1020

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

<div class="test-byline"><div class="test-byline-avatars"><a class="test-byline-avatar test-byline-avatar--author" href="/contributors/sebastianclaesson" title="Sebastian Claesson · Original author"><img src="https://github.com/SebastianClaesson.png" alt="Sebastian Claesson" width="28" height="28" loading="lazy" decoding="async" /></a></div><div class="test-byline-meta"><span class="test-byline-text">Contributed by <a href="/contributors/sebastianclaesson">Sebastian Claesson</a></span><a class="test-byline-link" href="/contributors">All contributors →</a></div></div>

<p class="test-part">Part of <a href="/docs/tests/maester">Maester</a> · Azure DevOps · Pipelines · <a href="/docs/tests">All checks</a></p>

```powershell title="Run this check"
Invoke-Maester -TestId AZDO.1020
```

## Overview

Creating classic build 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:
Enable the policy to disable creation of classic build pipelines.
1. Sign in to your organization.
2. Choose Organization settings.
3. Under the Pipelines section choose Settings.
4. In the General section, toggle on Disable creation of classic build 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

* [Devblog - Disable creation of classic pipelines](https://devblogs.microsoft.com/devops/disable-creation-of-classic-pipelines/)

## Details

<details>
<summary>Every attribute of this check</summary>

| Field | Value |
| --- | --- |
| Test ID | AZDO.1020 |
| Severity | Medium |
| Suite | Maester |
| Product | Azure DevOps |
| Feature | Pipelines |
| Area | Engineering systems |
| Resource type | Tenant |
| User impact | Medium |
| Implementation cost | Low |
| MITRE ATT&CK | None |
| PowerShell test | [Test-MtCheckAZDO1020](https://github.com/maester365/maester/blob/main/tests/maester/azure-devops/Test.AZDO.1020.ps1) |
| Services | AzureDevOps |
| Learn more | [https://devblogs.microsoft.com/devops/disable-creation-of-classic-pipelines/](https://devblogs.microsoft.com/devops/disable-creation-of-classic-pipelines/) |

</details>

## Source

- Test: [`tests/maester/azure-devops/Test.AZDO.1020.ps1`](https://github.com/maester365/maester/blob/main/tests/maester/azure-devops/Test.AZDO.1020.ps1)
- Documentation: [`tests/maester/azure-devops/Test.AZDO.1020.md`](https://github.com/maester365/maester/blob/main/tests/maester/azure-devops/Test.AZDO.1020.md)