Question
Migrating Classic Build Pipelines to YAML After March 2023 Deprecation
Kavi Cedar
0 reputation · 02 Apr 2022, 12:15 UTC
79.8K views1
Loading…
0 reputation · 02 Apr 2022, 12:15 UTC
Goal: Determine whether existing classic build pipelines will continue to run after the announced September 2024 cutoff for classic pipeline creation and editing, and understand any differences between Azure DevOps Services and Azure DevOps Server.
The March 2023 update deprecated the classic UI editor, introduced a compatibility shim that permits existing pipelines to operate until the cutoff, and noted that the exact date may vary between the cloud service and on‑premises server. Organizations also need to consider that migration assistant output is advisory and that extensions relying on the classic pipeline API must adopt the new REST endpoints.
What is the precise date after which classic pipelines are blocked from execution in Azure DevOps Services? Does the cutoff differ for Azure DevOps Server, and if so, what is the Server‑specific timeline? After the cutoff, will existing classic pipelines continue to run until manually disabled, or will they be stopped automatically?
Existing classic build pipelines will continue to run after the cutoff date. The deprecation focuses on the creation and editing of classic pipelines, not their execution. Once the cutoff is reached, you will be unable to create new classic pipelines or modify existing ones via the UI, but previously configured pipelines will remain operational until they are manually disabled or deleted.
There is no single, global "kill date" for the execution of classic pipelines across all versions of Azure DevOps. The behavior differs based on your deployment model:
For the cloud-hosted service, the primary deadline is the restriction on the classic UI editor. While Microsoft provides general guidance on deprecation windows, they typically maintain backward compatibility for existing pipeline execution to prevent breaking production CI/CD workflows. The "cutoff" refers to the transition to a read-only state for the classic designer.
The timeline for Azure DevOps Server is tied to the specific version of the software installed. Because the server is managed by the organization, the deprecation of classic features occurs only upon upgrading to a version where those features are removed or restricted. There is no external "cloud-style" cutoff date that automatically disables features on an on-premises instance.
While existing pipelines continue to run, organizations should prioritize migration to YAML for the following reasons:
To verify the behavior of your specific environment, you can perform a scoped test:
Missing Detail: To provide a more precise version-specific timeline for Azure DevOps Server, please specify the exact version (e.g., 2020.1, 2022) currently deployed in your environment.
Use comments to ask for clarification. Post a solution as an answer.
32,775 reputation · 02 Apr 2022, 18:56 UTC
One clarification worth adding to the existing answer: the announced cutoff concerns creation and editing, not execution. After it takes effect, classic pipelines typically become read-only in the UI — but "read-only" in practice means you also lose the ability to change variables, triggers, or agent pools through the designer, which effectively freezes maintenance even though runs continue.
Two practical follow-ups before relying on the compatibility shim:
Also note the migration assistant's YAML output is advisory: custom scripts, conditions, and task versions often need manual correction, so plan a review pass per pipeline rather than a bulk convert-and-trust.
azuredevops