Please enter your information to subscribe to the Microsoft Fabric Blog.

Thanks for subscribing to the Microsoft Fabric Blog. You’ll receive email notifications when we publish new posts.

Microsoft Fabric Updates Blog

  1. Updates
  2. Idris Motiwala

Assessing Your Azure Data Factory for Migration to Fabric Data Factory

As organizations modernize their data integration workflows, moving from Azure Data Factory (ADF) to Fabric Data Factory is an important milestone. Before starting the migration, it’s crucial to determine which pipelines and activities are ready to move, which require modifications, and which are not yet supported in Fabric. The built-in migration assessment tool in ADF streamlines this evaluation.

Why perform a migration Assessment?

Migration involves more than transferring resources. It ensures compatibility and minimizes disruption. Use the assessment tool to:

  • Identify pipelines and activities ready for migration.
  • Flag items that need changes or aren’t currently supported.
  • Export a comprehensive report for planning and tracking.

How to Run the Assessment

  • Open your Azure Data Factory instance in the Azure portal.
  • Select the Start assessment (preview) in the authoring canvas toolbar.
Figure 1: Start assessment

Review the side pane listing of your pipelines and the activities within. Expand each pipeline for more details.

Screenshot showing assessment summary on the side panel
Figure 2: View assessment summary

  • Select Export to download a CSV report with pipeline and activity statuses. Screenshot showing the drilldownn of assessment along with export option

Figure: View assessment summary drill-down

Understanding Assessment Results

Each pipeline and activity will be tagged with one of four statuses:

  • Ready: For migration.
  • Needs review: Requires changes before migration (e.g., parameters).
  • Coming soon: Support in progress; migrate later (e.g., dataflows).
  • Not compatible: No equivalent in Fabric; refactor required.

Note: The overall pipeline status will reflect the most restrictive status among its activities—if there are activities tagged as “Needs review,” “Coming soon,” or “Not compatible,” the pipeline will inherit “Not compatible” as the pipeline status to ensure migration readiness is accurately represented.

Next Steps

While we are building a native UX based migration experience you may:

Resources

Related blog posts

Assessing Your Azure Data Factory for Migration to Fabric Data Factory

Blog's featured image

Manage OneLake security for Mirrored Databases (Preview)
January 20, 2026 by Aaron Merrill

OneLake security now supports Mirrored Databases in Microsoft Fabric with the ability to define OneLake data access roles on all Mirrored item types. This update brings granular, role-based access control to data replicated into OneLake from transactional systems, extending the OneLake security model beyond lakehouses and enabling secure reuse of mirrored data across the organization. … Continue reading “Manage OneLake security for Mirrored Databases (Preview)”

Read more
Blog's featured image

Simplifying data movement across multiple clouds with Copy job – Enhancements on incremental copy and change data capture
January 20, 2026 by Ye Xu

Copy job is the go-to solution in Microsoft Fabric Data Factory for simplified data movement, whether you’re moving data across clouds, from on-premises systems, or between services. With native support for multiple delivery styles, including bulk copy, incremental copy, and change data capture (CDC) replication, Copy job offers the flexibility to handle a wide range … Continue reading “Simplifying data movement across multiple clouds with Copy job – Enhancements on incremental copy and change data capture”

Read more