Migration Sequencing Error — Azure DevOps Engineer (AZ-400)
You got the migration order wrong. Dependencies, data gravity, and blast radius determine sequence.
Right Tool, Wrong Phase of the Migration Journey
The exam distinguishes between tools used to assess, tools used to replicate, and tools used to cut over. Azure Migrate surfaces dependency maps and sizing recommendations; Azure Database Migration Service executes live schema and data transfer. Candidates conflate these roles and apply the replication tool during the assessment phase, or vice versa. When a scenario mentions downtime tolerance or data volume, that is the signal telling you which phase—and which tool—is in scope.
The Scenario
A company is migrating their DevOps toolchain to Azure DevOps. You recommend starting with Azure Pipelines because the team is most excited about managed CI. But the pipelines depend on an on-premises Artifactory for package management and deploy to on-premises servers via custom scripts. Moving the build pipeline first means every build fetches dependencies across a VPN from Artifactory (slow), and deployments still target on-premises infrastructure (no Azure benefit). The correct sequence: (1) Migrate the artifact repository to Azure Artifacts first, (2) Set up deployment targets in Azure (App Service, AKS, or VMs), (3) Migrate pipelines last with updated package sources and deployment targets. The pipeline is the consumer of artifacts and deployment targets — it should move after its dependencies, not before.
How to Spot It
- •DevOps toolchain migration follows the same dependency rules as application migration. Package repositories and deployment targets are dependencies. Pipelines consume them. Migrate dependencies first so the pipeline has something to pull from and push to when it moves.
- •Azure DevOps migration: Azure Repos (source control) and Azure Artifacts (packages) should migrate before Azure Pipelines. Boards and Test Plans can migrate independently since they have fewer technical dependencies.
- •When the exam describes migrating a CI/CD toolchain, identify what the pipeline depends on: source code repository, package feeds, secrets/credentials store, and deployment targets. Each dependency should be available in Azure before the pipeline migrates.
Decision Rules
Whether YAML environment protection rules and Artifacts retention policies must be fully provisioned before any YAML-driven deployment stage is activated, rather than after, to eliminate the unprotected deployment and artifact-publishing window that opens during the classic-to-YAML cutover.
Domain Coverage
Difficulty Breakdown
Related Patterns