Data Management

Azure Data Factory to Fabric Migration: What Moves, What Breaks and What It Costs

Azure Data Factory to Fabric migration in 2026: what Microsoft's built-in tool moves, what it leaves behind, capacity costs, effort and when to wait.

Nov 202611 min readData Management

The short answer

An Azure Data Factory to Fabric migration now starts with Microsoft's own tool: you mount the factory in a Fabric workspace, run the built-in assessment, and move the pipelines marked Ready into Fabric Data Factory with their triggers switched off. Self-hosted integration runtimes, metadata-driven designs with parameterised linked services, some triggers and a few activities still need hand work, and the bill changes from pay-per-run to a fixed Fabric capacity. Most mid-sized factories can be moved in phases over a few months, but there is no deadline forcing you to do it this year.

That last point matters. Microsoft has not announced a retirement date for Azure Data Factory, and its own guidance says ADF and Fabric can run side by side. The reason to move is where new investment is going: Copilot, OneLake, Direct Lake reporting and built-in deployment pipelines arrive in Fabric, not in ADF. The reason to wait is that some of what your factory does today is still in preview or not supported.

This guide covers what the tool really moves, how to triage a factory pipeline by pipeline, a worked cost and effort example for a 60-pipeline estate, the cutover method we use, and the cases where staying on ADF for another year is the right call. It is written for data and analytics leads at mid-sized companies, including pharma and life sciences teams running commercial and patient data through ADF.

Numbers to have in front of you

4readiness statuses the built-in assessment gives each pipeline: Ready, Needs review, Coming soon, Not compatible (Microsoft Learn, updated 5 October 2026)
$262.80a month for the smallest Fabric capacity, F2, on pay-as-you-go in a US region (AlphaBold Fabric pricing guide, August 2026)
$8,409.60a month for F64 on pay-as-you-go, the first size at which Power BI viewers no longer need a Pro or PPU licence (same source)
About 41%saving on a one-year Fabric capacity reservation against pay-as-you-go, for example F64 at $5,002.67 a month (same source)

Azure Data Factory vs Fabric Data Factory: what actually changes

Fabric Data Factory looks familiar, but it is not ADF with a new logo. Microsoft's upgrade planning guide lists the architectural differences that drive most of the effort:

AreaAzure Data FactoryFabric Data FactoryWhat it means for you
DatasetsSeparate, reusable objectsDefined inline inside each activityShared dataset logic is repeated per activity after migration
Linked servicesCan be fully parameterisedConnections do not take dynamic properties; activities can pass dynamic content to the connection objectMetadata-driven frameworks need redesign, not a straight copy
Global parametersGlobal parametersFabric variable librariesDifferent patterns and data types; Microsoft publishes a conversion guide
IdentityManaged identityWorkspace identitySource permissions must be re-granted to the new identity
Key VaultMature, all auth typesNarrower Key Vault reference supportCheck every secret your factory reads before you plan the move
SchedulingShared triggers, managed centrallySchedules set per pipeline, no shared trigger hubOne trigger running ten pipelines becomes ten schedules
On-premises accessSelf-hosted integration runtimeOn-premises data gatewayA new install, new networking checks and a new owner
Mapping data flowsSpark-based data flowsMapping data flow transforms in Dataflow Gen2, in previewEligible flows migrate; others are rebuilt in Power Query, SQL or notebooks
Child pipelinesExecute Pipeline activityInvoke Pipeline activityRenamed, with a different connection requirement
Custom codeCustom activityAzure Batch activitySame function under a new name

Some activities have no direct equivalent. Microsoft lists U-SQL (Data Lake Analytics, itself a deprecated service) and the Validation activity, which you rebuild with Get Metadata, loops and If conditions. Change data capture moves to Fabric Copy jobs, Airflow DAGs move to Fabric's Apache Airflow jobs, and SSIS packages keep running in ADF and are called from Fabric. If your factory depends heavily on any of these, the migration is a redesign project, and it should be budgeted as one.

The three ways to migrate

Mount first

Adding your existing factory to a Fabric workspace as an Azure Data Factory item gives a live, read-only view alongside your Fabric work. Execution stays in Azure. It costs nothing in risk and is the right first step for every estate: you can catalogue what exists, assign owners and plan cutover by domain.

Built-in upgrade

From ADF or from the mounted item, run the assessment, choose the pipelines you want, map linked services to Fabric connections and migrate. Connections are created automatically for common sources such as Blob Storage, ADLS Gen2, Azure SQL and Cosmos DB. Migrated schedule triggers arrive disabled so nothing double-loads.

Manual rebuild

Pipelines with unsupported activities, parameterised connection frameworks or event triggers are rebuilt by hand. This is slower but often the moment to remove duplicate pipelines, adopt OneLake shortcuts instead of copies, and move transformation into a lakehouse or warehouse.

How to triage a factory, pipeline by pipeline

Run the assessment, export the result and give every pipeline one of four actions. The status tells you what the tool thinks; the business owner tells you whether it matters.

Assessment statusDefault actionTypical effortWatch for
ReadyMigrate with the built-in tool, then validateLow: mostly testingHidden dependencies on shared triggers, global parameters or Key Vault secrets
Needs reviewMigrate, then fix flagged settings by handMediumConnection mapping, identity changes, dynamic expressions that reference datasets
Coming soonLeave in ADF, mounted in Fabric, and re-check each quarterNone nowDo not rebuild something Microsoft is about to support
Not compatibleRebuild, replace, or keep in ADF if the pipeline is stableHighU-SQL, Validation activities, unsupported connectors, event triggers

Before any of that, delete what nobody uses. Most factories that have run for a few years carry pipelines that load tables no report reads. Cross-check the last run date and the downstream consumers, retire the dead ones, and the migration gets smaller before it starts.

Worked example: cost and effort for a 60-pipeline factory

The figures below are planning assumptions for illustration, not benchmarks. They show how we size an ADF to Fabric migration for a mid-sized company with one factory, a self-hosted integration runtime for an on-premises ERP, and about 40 Power BI users.

Assessment result. After retiring unused pipelines, 60 remain: 35 Ready, 12 Needs review, 8 Coming soon and 5 Not compatible.

Work itemAssumptionPerson-days
Validate Ready pipelines35 x 0.5 day17.5
Fix Needs review pipelines12 x 2 days24
Rebuild Not compatible pipelines5 x 4 days20
Coming soon pipelinesStay in ADF, mounted0
On-premises data gateway to replace the SHIRInstall, networking, tests3
Global parameters to variable librariesOne library per environment2
Parallel run and reconciliationTwo weeks of side-by-side loads10
Cutover and hypercareSwitch schedules, watch first runs3
Total79.5

That is roughly 16 weeks for one engineer, or eight to ten weeks with two working in parallel, with the 8 Coming soon pipelines left in ADF until Microsoft supports them.

Run cost. ADF bills per activity run, per data integration unit hour and per data flow vCore hour. Fabric bills a capacity whether or not pipelines are running, although pay-as-you-go capacities can be paused. If testing shows the estate fits on an F8, the list price is $1,051.20 a month on pay-as-you-go or $625.33 a month on a one-year reservation, according to AlphaBold's August 2026 pricing guide. That capacity is shared with any lakehouse, warehouse and Power BI work you put on it. Below F64, the 40 report viewers still need Power BI Pro, which Microsoft lists at $14 per user per month, so $560 a month stays in the budget either way.

Now change one assumption. If the factory is metadata-driven, with one generic pipeline reading a control table and parameterised linked services, most of it will land in Needs review or Not compatible, and the effort can double. That design choice, not the pipeline count, is the number to check first.

How to run the migration, step by step

Inventory and clean up

List every pipeline, linked service, integration runtime, trigger and global parameter. Retire pipelines with no recent runs or no downstream consumers.

Mount the factory in Fabric

Add the factory as an Azure Data Factory item in a Fabric workspace so the team can see ADF and Fabric work side by side while nothing changes in production.

Run the assessment and triage

Export the readiness status for every pipeline and assign migrate, fix, wait or rebuild, using the table above and the business owner's view of criticality.

Build the landing zone

Create workspaces per environment, Fabric connections, the on-premises data gateway, workspace identity permissions and variable libraries before the first pipeline moves.

Migrate in waves

Start with low-risk copy pipelines in non-production, then move by business domain. Keep finance and month-end loads for a later wave.

Run in parallel and reconcile

Run old and new pipelines against the same sources and compare row counts, totals and key fields in the target tables until they match for an agreed period.

Cut over and switch off

Enable Fabric schedules, disable the ADF triggers for the same pipelines, watch the first runs closely and keep a documented way back for each wave.

Common ADF to Fabric migration mistakes

  • Treating the assessment as the plan

    Ready means the tool can move it, not that it will behave the same. Shared triggers, secrets and identity still need checking.

  • Forgetting the gateway

    The self-hosted integration runtime does not migrate. The on-premises data gateway is a new install with its own owner, updates and network rules.

  • Double loading

    Enabling Fabric schedules before disabling ADF triggers runs the same load twice and can duplicate rows in append-only tables.

  • Sizing capacity by guesswork

    Pick a capacity from measured consumption on a trial or test workload, not from the SKU a vendor slide suggests.

  • Rebuilding what is coming

    Rewriting a Coming soon pipeline by hand burns effort Microsoft may save you a quarter later.

  • No reconciliation sign-off

    Without written proof that old and new outputs match, the first odd number in a report will be blamed on the migration.

When not to migrate yet

Your factory is stable, cheap to run on pay-per-run pricing, and nobody is asking for Fabric features such as OneLake or Direct Lake reporting
Most pipelines come back Coming soon or Not compatible, especially metadata-driven frameworks, SSIS-heavy estates or event-triggered loads
Your workloads are small and bursty, so a capacity that bills around the clock would cost more than today's consumption bill
A bigger platform decision is still open, such as Fabric versus Databricks or Snowflake, and moving pipelines first would lock it in
Month-end, quarter-end or a regulatory submission is inside the next migration window

Regulated data, and when to bring in Azure Data Factory consultants

For pharma and life sciences teams, the pipelines that matter most are usually the ones loading syndicated prescription data, CRM activity, specialty pharmacy and hub feeds into a commercial data warehouse. Those loads have vendor delivery windows, restatements and licence terms, and some carry patient-level data. A migration has to preserve the late-file and duplicate-file checks, keep access as narrow as it is today under workspace roles and sensitivity labels, and prove that weekly brand numbers did not move. Our guide to the pharma commercial data warehouse covers what those loads feed.

Many teams do the Ready pipelines themselves and bring in Azure Data Factory consultants for the parts that need judgement: the triage, the gateway and identity setup, rebuilding metadata-driven frameworks and running reconciliation. If you are budgeting for outside help, our breakdown of Microsoft Fabric consultant cost shows how rates and project totals are built. If the move is also a chance to change the reporting layer, see Power BI consulting, and for pipeline work on other platforms see our ETL services.

Greenwolf's founder came up through pharma commercial operations consulting at ZS, and our Microsoft Fabric consulting and Azure data engineering team plans and runs these migrations in your own tenant. We are an independent consultancy and do not claim a Microsoft partnership; we will also tell you when staying on ADF is the cheaper answer.

Questions about migrating Azure Data Factory to Fabric

Is Azure Data Factory being retired?
Microsoft has not announced a retirement date for Azure Data Factory, and its guidance says ADF and Fabric Data Factory can run side by side. New capabilities are being built into Fabric, which is why most teams plan a phased move rather than an urgent one.
How do I migrate Azure Data Factory pipelines to Fabric?
Mount your factory in a Fabric workspace, run the built-in assessment, and migrate the pipelines marked Ready, mapping linked services to Fabric connections. Migrated schedule triggers arrive disabled, so you test, reconcile and then switch schedules over. Pipelines the tool cannot move are rebuilt by hand.
Does the self-hosted integration runtime migrate to Fabric?
No. In Fabric, on-premises sources are reached through the on-premises data gateway, and managed virtual network runtimes are replaced by virtual network data gateways. Plan the gateway install and network checks before the first pipeline that needs it.
Can mapping data flows be migrated to Fabric?
Eligible mapping data flows can be upgraded to mapping data flow transforms in Dataflow Gen2, which Microsoft lists as a preview capability. Flows using unsupported connectors or transformations need to be rebuilt in Power Query, warehouse SQL or Spark notebooks.
Is Fabric cheaper than Azure Data Factory?
Not automatically. ADF bills per activity run and data movement, while Fabric bills a capacity, from $262.80 a month for F2 on pay-as-you-go in a US region according to AlphaBold's August 2026 guide. Fabric tends to pay off when the same capacity also runs your lakehouse, warehouse and Power BI work.
How long does an ADF to Fabric migration take?
It depends on how many pipelines need hand work, not on the total count. In our illustrative 60-pipeline example, the effort came to about 80 person-days, or eight to ten weeks with two engineers. Metadata-driven factories can take twice as long.
What happens to ADF global parameters in Fabric?
They become Fabric variable libraries. The patterns and data types differ, so expressions that reference global parameters need updating, and Microsoft publishes a conversion guide for it.

Want a straight answer on whether to move your factory?

Send us the shape of your ADF estate: pipeline count, integration runtimes and what the loads feed. We will tell you what the assessment is likely to show, what it would take to migrate, and whether waiting is the better call.

Contact us

Reviewed by Team Greenwolf Tech Labs ยท

Part of our Data Management and Engineering hub. Start with our data management services.

Talk to us

Is this a problem you are living with?

If any of the above sounds like your week, tell us which part. We will come back with what it would take to fix it.

  • A reply from a consultant, not a sales sequence
  • Usually within one working day
  • No obligation, and nothing to sit through

We reply from [email protected], usually within one working day. We do not add you to a mailing list.