The Microsoft Data path that actually makes sense of chaos.

My path. In order. The real one.

Let me be straight with you. Data is the area where I have the lightest direct hands-on experience, and I want this page to be honest about that.

What I do have: early-career fundamentals with Microsoft Access, working knowledge of SQL and Microsoft Fabric, and the data-center / virtualization foundations from my Pre-Sales Engineer days at Ingram Micro (Hyper-V, SCVMM, Data Core, Veeam). I am currently learning Microsoft Fabric and a bit of Data Lake hands-on, the same way I have learned every other Microsoft technology over 11 years: by doing it.

What I also have, and this is the part that matters for you: I am a Microsoft Global Senior Cross Solution Partner Solution Architect. I work with data specialists inside global partners every single day. I see how they build their careers, what certs actually moved the needle for them, and which paths stalled. This page is the synthesis of that — not a pretend-deep-data-engineer guide, but the honest path I see specialists walk.

Here is what my own career looked like as it relates to data.

• Early career · College & first jobs
  Microsoft Access fundamentals
  My first hands-on with structured data was on Microsoft Access in school and early jobs. Tables, queries, simple relationships. Not glamorous. But it taught me how data thinks before I had any business calling myself a data person.
• 2012-2015 · Ingram Micro
  Pre-Sales Engineer / Technical Account Manager
  Years of working on Microsoft Server, Hyper-V, SCVMM, Data Core, Veeam, and VMware. The data-center foundation. I was not engineering data pipelines, but I was learning how the storage, compute, and network underneath data systems actually behaves at scale. That foundation makes everything that comes later easier.
• 2015-2021 · Ingram Micro & RSA
  Security Pre-Sales / Product Marketing
  NetWitness Suite was a heavy data play at the security layer (logs, packets, endpoint telemetry). Working with NetWitness for 3 years taught me what real-time data ingestion, indexing, and query patterns look like under pressure. That experience translates directly to how I understand Sentinel and KQL today.
• 2021-2025 · Microsoft
  Senior Partner Technology Strategist
  4+ years working with Microsoft partners across the data estate. I was not the data engineer in the room. I was the strategist helping partners decide where to invest, which workloads to lead with, and how to position. I watched data engineers in those partner orgs build full careers from DP-900 through DP-203.
• 2025-Today · Microsoft
  Global Senior Cross Solution Partner Solution Architect (still learning)
  My current role brings me into Fabric, Power BI, and the modern Microsoft data stack regularly. I am hands-on with SQL, exploring Microsoft Fabric and Data Lake concepts, and learning alongside the specialists I work with. I am writing this page as someone walking the path with you, not someone who finished it ten years ago.

What I am sharing on this page is the path I see data specialists walk inside the Microsoft partner orgs I work with every day, combined with what I am learning hands-on right now in Fabric and SQL. If you want a guide written by someone who has been a Senior Data Engineer for 15 years, this is not it. There are great ones out there.

What this page offers: an honest, partner-architect-shaped roadmap. DP-900, AZ-900, DP-300, DP-203. Walked by enough specialists I trust that I can tell you which steps matter and which ones get skipped.

Who this is actually for.

I would rather tell you to close this tab than waste your time. So let me be direct about who should keep reading, and who should not.

This path is for you if:

• You are patient. Data work rewards patience and punishes shortcuts.
• You like solving puzzles and are okay with the answer being buried three layers deep in a join.
• You want a role where your work compounds. Data skills get more valuable every year, not less.
• You are already in a BI or analyst role and want to move into engineering.

This path is not for you if:

• You want to be a data scientist building novel ML models. That is a different path, AI-300 or a PhD track.
• You hate SQL. Sorry. SQL is the language of data, and this path lives in SQL.
• You want fast results. Data careers compound slowly. If you want a quick win, the AI path has shorter feedback loops.

Still here? Good. Let me tell you what usually goes wrong.

The biggest mistakes I see every time.

I have mentored enough people through this path to see the same mistakes on repeat. Each one adds months. One of them can cost you a year.

The sequence, in order, with timing.

Four certs. Nine to twelve months of focused work. Here they are, in the exact order that makes each next cert easier than the last.

Total: 23-35 weeks of focused study. $528 USD in exam fees. A credential stack that tells employers you can build, not just talk about.

What to do between certs.

Here is what separates the people who get certified and also get hired, from the people who get certified and stay stuck: what they do between exams.

The cert is proof you studied. The project is proof you can build. Employers want both. Here is what I recommend doing in the weeks between each exam:

After DP-900:

• Provision an Azure SQL Database in the free tier. Create a few tables. Run queries. Delete them. Try again.
• Read the "SQL Server anti-patterns" posts on Microsoft Tech Community. You will learn what not to do, which is as valuable as learning what to do.
• Post one LinkedIn note explaining a data concept you now understand. Public writing forces clarity.

After AZ-900:

• Deploy an Azure Storage account, upload files, configure access. Data Lake Storage Gen2 is just Storage with hierarchical namespace turned on. Play with it.
• Read one Azure architecture reference case for a data workload per week. Healthcare, finance, retail. See the repeating patterns.

After DP-300:

• Set up automated backup, configure Always On availability groups in a lab. You are not studying for an exam, you are learning how production systems survive failure.
• Follow three Microsoft MVPs in the data space. See what they debate. See what they recommend.

After DP-203:

• Build a real pipeline. Data source, bronze/silver/gold layers in a data lake, orchestration in Data Factory or Synapse, dashboard at the end. End to end. Document it on GitHub.
• Start applying for Data Engineer roles. You have the credentials, the pipeline portfolio, and the language. Time to get paid for it.

If you can only do one thing between certs: build one tiny project. Not a perfect one. A small, shippable, shareable one. Momentum beats perfection every time.

Thriving, not just surviving.

Most cert guides end at "you passed, congrats, apply for jobs." That is like teaching someone to drive and then dropping them on the highway. Let me tell you what actually happens after you are certified, and how to not just survive it but use it.

The 2026 retirement watch.

Microsoft is retiring 11 certifications in 2026. Here is what matters for this specific path:

DP-100 retires June 1, 2026

Replaced by AI-300 (Machine Learning Operations Engineer Associate). This does not affect the core data engineer path above. DP-100 was the ML-focused cert, and its replacement AI-300 is for MLOps engineers specifically. If you are doing data engineering, stay on DP-203.

DP-900, DP-300, DP-203 are all current

As of April 2026, all three certs on this path are current and actively maintained. The path is safe to start today.

DP-800 and DP-750 are in beta

Microsoft just released DP-800 (SQL AI Developer Associate) and DP-750 (Azure Databricks Data Engineer Associate) in beta. These are optional specializations you can layer on top of DP-203 later. Watch the space.

Bookmark this page. As Microsoft announces more changes through 2026 and into 2027, I will update this section. Or see Microsoft’s official retirement list:

Microsoft’s official credential retirement page →