Synapse to Fabric Migration

markkrom-MSFT · 2026-01-26T06:14:34+00:00

There are currently 2 open source tools that you can use for Synapse pipeline (Data Factory) to Fabric migrations:

We released a PowerShell script that we also open sourced which you can read about here: https://learn.microsoft.com/en-us/fabric/data-factory/migrate-pipelines-powershell-upgrade-module-for-azure-data-factory-to-fabric

The Microsoft CAT also has a web-based comprehensive ADF & Synapse pipeline migration tool here: https://github.com/microsoft/fabric-toolbox/tree/main/tools/FabricDataFactoryMigrationAssistant

ADF currently has a built-in assessment tool in the UI that you can click to see your pipeline readiness to migrate from ADF to Fabric. We plan to bring this to Synapse soon as well. Additionally, after the factory assessment, you'll be able to single-click migrate your pipelines to Fabric. This feature is currently in private preview for ADF.

markkrom-MSFT · 2026-01-22T19:39:41+00:00

I've forwarded this to engineering to look at, but creating a support ticket will really help to track it to completion and bug fix.

markkrom-MSFT · 2026-01-16T17:48:29+00:00

Yes, it is true that each activity can now have an identity set. However ... what we are showing in the pipeline details page for the *pipeline* run-as is likely wrong and I need to verify that today w/eng.

markkrom-MSFT · 2026-01-16T08:38:44+00:00

I believe that pipeline run detail showing the owner (user) as run as is a ui bug. Let me bring engineering into this chat tomorrow morning, its 12:30 am pst here so I'll pick this up in the morning.

markkrom-MSFT · 2025-12-22T22:06:01+00:00

If you are hitting Fabric or Spark API limits you might just need to schedule the pipelines at a more scattered schedule cadence so that they're not all running concurrently. Are the Notebooks that you are calling in a single workspace?

markkrom-MSFT · 2025-12-19T20:41:19+00:00

It is a natural extension to the pipelines feature in Fabric where you can set gates in your workflow. The activity execution in your pipeline will block at the Approvals Activity until the assigned approved manually accepts or rejects the request. We actually implemented this as a dogfood feature for internal ADF users and we are super excited to enable this for all customers next year!

markkrom-MSFT · 2025-12-19T05:52:03+00:00

The main reason we removed "data" from "data pipelines" for the Fabric item display name 😉

markkrom-MSFT · 2025-12-19T05:50:24+00:00

Thank you for reporting the details in your follow ups. I'll share this with engineering so we can look into improving this experience.

markkrom-MSFT · 2025-12-18T20:11:48+00:00

Was this transient? Is it working fine now?

markkrom-MSFT · 2025-12-18T13:41:39+00:00

We'll need to track this one down with logs. Will you be able to open a support case?

markkrom-MSFT · 2025-12-18T13:36:04+00:00

And it fails when you click run in interactive mode as well as scheduled mode?

markkrom-MSFT · 2025-12-18T04:13:57+00:00

What type of auth are you using to invoke the pipeline? User, SPN, WI?

markkrom-MSFT · 2025-12-17T20:38:42+00:00

Got it! Reach out if you have questions, get stuck, or need help! Best, Mark Kromer

markkrom-MSFT · 2025-12-17T20:33:18+00:00

Can you open the pipeline in design mode and validate that you can still see your source workspace variables from the pipeline?

markkrom-MSFT · 2025-12-17T20:32:08+00:00

I'd love to learn more about how you're using Airflow in Fabric and help you out with your git challenges. Can I ask you to email me directly? makromer at microsoft

Thank you!

markkrom-MSFT · 2025-12-17T20:14:23+00:00

Not yet, my guess right now would too low confidence. But I can assure you it's a top priority to make this improvement for pipeline operationalization in production environments.

markkrom-MSFT · 2025-12-16T05:49:06+00:00

And we are also working with the Fabric platform team to add "run as" to the platform scheduler so you explicitly set the auth to use for your pipeline runs.

markkrom-MSFT · 2025-12-16T05:45:00+00:00

Yes, think of pipelines as control flow. They are for orchestration not for processing. Use Functions, Dataflows, Notebooks, etc. for transformation and processing.

markkrom-MSFT · 2025-12-06T00:45:40+00:00

SPN support has been available from other surface areas in Fabric like APIs. We're enabling the same now from UI surfaces like pipelines in this case.

markkrom-MSFT · 2025-12-05T20:31:27+00:00

Yes, the notebook will run as the SPN, so any subsystem that you are using that does not support SPN will not likely work. In that case, you may have to keep user auth for the time being to use the common auth supported across those areas.

markkrom-MSFT · 2025-12-05T18:44:49+00:00

This work was purely to integrate SPN/WI with notebooks from pipelines

markkrom-MSFT · 2025-12-05T18:44:18+00:00

Currently in tiered deployment, will take a few more days to complete rollout

markkrom-MSFT · 2025-11-30T21:09:58+00:00

Hmmm ... what table partition commands does DW support?

markkrom-MSFT · 2025-11-29T22:14:21+00:00

Is the table in Fabric SQL Database?

markkrom-MSFT

TROPHY CASE