Skip to main content

Archived certification · retired

Azure Data Engineer Associate (DP-203)

Retired along with its renewal assessment; Microsoft's certification page carries the retirement notice without restating the date. DP-700 is the live Fabric-based data engineering credential and is the nearest equivalent, but the AZ retirement notice does not name it as the replacement.

Vendor record

Retired

Retired along with its renewal assessment; Microsoft's certification page carries the retirement notice without restating the date. DP-700 is the live Fabric-based data engineering credential and is the nearest equivalent, but the AZ retirement notice does not name it as the replacement.

Source: Microsoft Learn · Read 22 September 2026

Sourced fields only; this does not mean every exam detail has been verified. Pricing and renewal policies have their own sources and check dates. Confirm the currency, tax and final booking total with the vendor.

Role-fit guidance is TechWaymark editorial interpretation. It is separate from the recorded vendor facts and does not measure hiring outcomes.

Existing candidates and holders

Check the vendor's booking and credential rules if you are already studying or hold this qualification. An exam retirement does not erase your previous learning. This page preserves the record and does not change any saved credential.

Practical exercise for existing holders
Certifications Project guide Home projects Back to certification

Home labs & practical projects

Assess a legacy Azure analytics pipeline for migration

A project to do with your own tools, with guidance on what to create and capture.

Design project Suggested time: 2–3 hoursNo hardware required for the design

For existing holders and historical learning. Check the current credential before starting exam preparation.

01

What you could create

An existing data team maintains an older Azure analytics pipeline. It needs to understand dependencies and data-quality risks before considering a new platform.

Example evidence format
Project evidence map (example)
Legacy pipeline dependency mapScope and inputs
Migration equivalence and rollback test planDecisions and reasoning
Evidence record (example)
EvidenceWhat to capture
Legacy pipeline dependency mapShow the inputs, scope and decisions behind this record. The plan preserves business semantics rather than only row counts.
Migration equivalence and rollback test planInclude the evidence supporting your conclusion. Historical credential content is not treated as a current platform recommendation.
02

What you'll need

Document, spreadsheet or diagram tool

Create a historical pipeline diagram with ingestion, transformation, storage and reporting. Include one hidden schedule dependency and an undocumented data-cleaning rule.

Project record

Keep the working files for legacy pipeline dependency map and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

No paid platform is needed for the written version. Use a document, spreadsheet or diagram tool you already have.

The organisation and records are fictional. Write down assumptions; do not substitute confidential employer information.

03

Suggested milestones

  1. 1

    Plan and investigate

    Inventory data contracts, identities, schedules and recovery assumptions.

  2. 2

    Develop your approach

    Identify tests needed to compare old and proposed outputs.

  3. 3

    Verify and explain

    Write a staged migration assessment with rollback and reconciliation criteria.

04

Useful resources

Use these resources to deepen your understanding and check key details.

Turn the project into evidence

Keep your artefacts and reasoning together so you can explain what you did.

A useful starting point

Create a historical pipeline diagram with ingestion, transformation, storage and reporting. Include one hidden schedule dependency and an undocumented data-cleaning rule.

What a good result looks like
  • The plan preserves business semantics rather than only row counts.
  • Historical credential content is not treated as a current platform recommendation.

Finish the project

Keep the decision record and note unanswered questions. A written design is not evidence that a technical control has been tested.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.

Explore the certification library