I pay attention to how Microsoft talks about ADF in their marketing materials. Not because I trust marketing, but because product positioning is a leading indicator of roadmap decisions, and roadmap decisions affect the architectures I'm building for clients today.
The signal I've been tracking in 2020: ADF is increasingly positioned as a component of a platform, not a standalone product. That's worth understanding.
The "Azure Analytics" Grouping
Microsoft's 2020 marketing bundles ADF, Azure Synapse Analytics, and Power BI together under "Azure Data + Analytics." The narrative is clean: ADF brings data in, Synapse processes it, Power BI presents it. The three products are presented as a coherent platform for the full analytics lifecycle.
This is not just branding. When Microsoft starts grouping products together in marketing, it usually precedes technical integration -- shared identity, shared monitoring, shared governance. The Microsoft Purview integration that's been rolling out across both ADF and Synapse is an early example of this. Data lineage tracking works across both because they share a lineage metadata layer.
What Synapse Analytics Actually Signals
I wrote about this when Synapse launched: Synapse Pipelines and ADF Pipelines are functionally near-identical. Microsoft's explanation is that they serve different team contexts. My read is that this is a product surface strategy -- Microsoft wants both the data engineering team and the analytics team inside the Synapse workspace.
The endpoint of this strategy is a single Microsoft analytics workspace that includes everything: data integration (currently ADF and Synapse Pipelines), data processing (Synapse SQL, Synapse Spark), and data presentation (Power BI). The Synapse workspace is already 70% of the way there.
I've heard the label "Microsoft Fabric" in some internal roadmap discussions. Nothing public yet. But when you look at the product trajectory -- Synapse Pipelines embedded in Synapse, Power BI Premium getting dataflow capabilities, Purview spanning the entire stack -- the destination is visible even if the timeline isn't.
The Power BI Connection
Power BI getting dataflow capabilities is the organizational signal I find most interesting. Power BI Dataflows (not to be confused with ADF Data Flows -- yes the naming is actively bad) let analysts prepare data inside Power BI without touching ADF. For simple self-service scenarios, this is appropriate.
The problem is that "simple self-service scenarios" tend to expand. An analyst who can build a dataflow to add a calculated column will eventually build a dataflow that joins three tables, applies business logic, and feeds a report that becomes a critical business tool. The governance and lineage story for that data asset is now split across two products.
This is a governance challenge that the "Azure Analytics" platform framing is supposed to address -- unified lineage in Purview, unified identity in Azure AD, unified monitoring in Azure Monitor. Whether it works in practice is still TBD.
What To Do With This Information
Build ADF skills knowing they transfer. The pipeline authoring, the parameterization patterns, the linked service model, the CI/CD approach -- these translate directly to Synapse Pipelines and will likely translate to whatever Microsoft calls the next evolution of this platform.
Don't bet on the product name staying "Azure Data Factory" forever. I'm not predicting imminent deprecation -- ADF has too many production deployments for Microsoft to sunset it carelessly. But the organizational signals suggest that new investment is increasingly going to the Synapse workspace.
Watch where connectors, new activity types, and new Data Flow transformations land first. If Synapse Pipelines consistently gets them before ADF, that confirms the consolidation direction.
If you're making platform investment decisions and want to think through the tradeoffs, I'm here to help.