How do I orchestrate Microsoft Fabric pipelines alongside existing Azure Data Factory pipelines?

During a move from Azure Data Factory to Microsoft Fabric, part of the chain runs in ADF and part in Fabric, and neither service treats the other's pipelines as native steps. You can bridge them with REST calls from one pipeline to the other, with storage events, or by putting both under an orchestrator that sees ADF and Fabric pipelines as peer tasks. The orchestrator route lets you migrate one pipeline at a time without rewiring the chain each time.

Why the boundary matters

Microsoft positions Data Factory in Fabric as the next generation of ADF and publishes an upgrade guide, but migrations are rarely done in one step. While they run, an ADF load might feed a Fabric notebook, or a Fabric pipeline might need to finish before an ADF export. Each service's dependencies stop at its own boundary.

Approaches

Approach How it works Trade-off
Call across with REST An ADF Web activity starts a Fabric pipeline through the Fabric REST API, or a Fabric Web activity starts an ADF pipeline Polling and authentication are yours to build; every migration step means editing the calling pipeline
Storage events One side writes a file; the other starts on an event trigger Loose coupling, but a file is not proof of success, and passing values is awkward
Time gaps Schedule the Fabric side "after" the ADF side Breaks the night the first side is late
Orchestrator dependency Both are tasks in one graph, linked by On Success One more service, but moving a pipeline from ADF to Fabric only changes one task

With Polysync

  1. Connect the Data Factory and the Fabric workspace as two platforms. ADF pipelines and Fabric notebooks, Spark job definitions, pipelines and dataflows are discovered.
  2. Create tasks for each step and link them with On Success dependencies, in whichever direction the chain runs.
  3. When a pipeline moves to Fabric, create its Fabric task, move its dependencies across and disable the old ADF task.

Note that values travel only where the service returns them: ADF pipelines can return outputs through pipelineReturnValue; Fabric pipelines do not return outputs to Polysync, so a downstream step should read the value from storage.

Frequently asked questions

Can a Fabric pipeline call an Azure Data Factory pipeline?

Not with a dedicated activity. A Web activity can call the ADF REST API to start a pipeline run, and you then poll for its result.

Do I have to migrate everything to Fabric at once?

No. Many estates run both for a long time. What matters is that the chain between them is explicit rather than based on time gaps.

Does Polysync migrate pipelines from ADF to Fabric?

No. It orchestrates both while you migrate. The migration itself uses Microsoft's tooling and guidance.

Microsoft, Azure, Azure Data Factory, Microsoft Fabric, Power BI, Logic Apps and Microsoft Marketplace are trademarks of the Microsoft group of companies. Apache Airflow and Airflow are trademarks of the Apache Software Foundation. Databricks and Lakeflow are trademarks of Databricks, Inc. All other product names are the property of their respective owners and are used for identification only. No endorsement by their owners is implied.

Data pipeline orchestration for Azure-first teams

Keep your ADF, Databricks, Fabric and Power BI jobs. Polysync connects them with shared scheduling, cross-platform dependencies and one run history, including jobs on AWS and Google Cloud. No orchestration code to write.

Learn more about Polysync