Reading the Signals
I don't usually make predictions in public. But the signals I'm reading in 2022 are loud enough that staying quiet feels like an abdication.
Microsoft is building a unified analytics platform. They're going to announce it with a new name, probably in 2023. And the announcement is going to absorb ADF, Synapse Pipelines, Synapse SQL, Synapse Spark, Power BI, and Azure ML into a single product family — possibly a single workspace experience.
Here's my evidence.
The Evidence Trail
Synapse Already Did This Partially
Synapse Analytics is not a database. It's a workspace. It puts Synapse SQL pools (MPP analytics database), Synapse Spark pools (managed Spark), Synapse Pipelines (ADF-equivalent orchestration), and Power BI report embedding into a single studio interface with a unified security model.
That's four things that used to be separate Azure services (SQL Data Warehouse, HDInsight, ADF, Power BI) in one place. Microsoft already did the consolidation once. Synapse was the first version of the unified analytics platform.
Power BI Is Increasingly "Part of the Platform"
Power BI datasets in Synapse workspaces. Power BI reports embedded in Synapse Studio. Power BI Premium capacity as an analytics compute layer. The separation between "Power BI for reporting" and "Synapse for data engineering" is eroding in Microsoft's product descriptions. The integration points multiply every year.
The Azure Data + Analytics Product Family
Microsoft's product marketing has shifted from individual products ("Azure Data Factory," "Azure Synapse Analytics," "Power BI") to a product family ("Azure Data + Analytics"). When Microsoft starts naming things as a family rather than as discrete products, it usually means the family is about to get a brand.
The ADF / Synapse Pipelines Feature Parity
If Microsoft were maintaining ADF and Synapse Pipelines as genuinely distinct products with distinct roadmaps, their feature sets would diverge over time. Instead, they've converged. The feature parity that exists today is not accidental — it's what happens when two products are being maintained toward the same destination.
What I'm Hearing
I have contacts at Microsoft. I'm not going to attribute statements to individuals, but I will say: the codename "Fabric" is not a secret in the Microsoft data ecosystem. If you've been talking to Microsoft field engineers in 2022, you've probably heard it. A unified analytics platform under a new brand. Everything — ADF, Synapse, Power BI, ML — in one workspace.
I'm expecting the announcement at Microsoft Build 2023 in May.
What This Means for ADF Investment
Here's the question I get from clients when I share this analysis: "Should I stop investing in ADF?"
No. And I'll tell you exactly why.
The ADF skills that matter — pipeline parameterization, metadata-driven frameworks, Data Flows transformation logic, CI/CD with ARM templates, integration runtime configuration — are going to transfer directly to whatever the unified platform becomes. The pipeline JSON schema is the same. The expression language is the same. The connector model is the same. Microsoft is not going to rewrite the engine when they rebrand the container.
This is the same lesson from the SSIS → ADF transition. SSIS skills — ETL logic, metadata-driven patterns, package organization, deployment — transferred to ADF. The tool changed; the craft didn't.
What to Watch in 2023
Three things to track as the consolidation unfolds:
The product announcement. When it comes — I'm predicting Build 2023 — read the technical details, not the marketing. What's the underlying storage model? What's the compute model? What's the security model? Those answers will tell you how much of your existing ADF architecture carries forward.
The ADF roadmap communication. Microsoft will need to communicate whether standalone ADF continues to receive feature investment or enters maintenance mode. Listen carefully to that messaging. "Continued support" and "continued feature investment" mean different things.
The migration path documentation. If the new platform requires significant migration work (new pipeline schemas, new deployment models, new authentication patterns), Microsoft will publish migration guides. The quality of those guides will tell you a lot about how much thought went into backward compatibility.
My Recommendation
Build on ADF v2 patterns now. Invest in parameterization, metadata-driven frameworks, CI/CD automation, and Data Flows. These investments are durable — they transfer to whatever the unified platform becomes.
Don't wait for the announcement to start building. Don't pause current work while you "see what happens with Fabric." The announcement will confirm what I'm telling you today: the technology under the hood isn't changing. Only the name on the box is.
Trust me on this one.