Blog Post

Fabric Updates Blog
2 MIN READ

Assessing Your Azure Data Factory for Migration to Fabric Data Factory

ssrinivasara's avatar
ssrinivasara
New Member
10 months ago

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.

Assessing_Your_Azure_Data_Factory_for_Migration_to_Fabric_Data_Factory

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

Published 10 months ago
Version 1.0
No CommentsBe the first to comment