Migrating Classic Build Pipelines to YAML After March 2023 Deprecation

Execution Status After the Cutoff

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.

Timeline and Platform Differences

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:

Azure DevOps Services (Cloud)

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.

Azure DevOps Server (On-Premises)

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.

Migration Considerations

While existing pipelines continue to run, organizations should prioritize migration to YAML for the following reasons:

• Version Control: Classic pipelines are stored in the internal database; YAML pipelines are stored in Git, allowing for PR reviews and history.
• API Dependencies: Extensions that rely on the classic pipeline API may stop functioning or require updates to the new REST endpoints.
• Consistency: YAML allows for the use of templates, reducing duplication across multiple projects.

Verification Steps

To verify the behavior of your specific environment, you can perform a scoped test:

1. Create a dummy classic pipeline (if the UI still permits).
2. Trigger a manual run to confirm the agent communication is intact.
3. Attempt to modify a single variable in the UI to check if your organization has already entered the "read-only" phase for classic configurations.

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.