Skip to content

Commit 661315b

Browse files
authored
Update how-to-upgrade-your-azure-synapse-analytics-pipelines-to-fabric-data-factory.md
1 parent c6023c2 commit 661315b

1 file changed

Lines changed: 22 additions & 9 deletions

File tree

articles/data-factory/how-to-upgrade-your-azure-synapse-analytics-pipelines-to-fabric-data-factory.md

Lines changed: 22 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -20,17 +20,30 @@ With the Synapse pipelines migration experience (Preview), you can:
2020
- Assess pipeline readiness directly in your Synapse workspace.
2121
- See compatibility gaps at the pipeline and activity level.
2222
- Migrate supported pipelines to a Fabric workspace.
23-
- Export results to CSV to plan remediation and phased validation.
23+
- Export assessment and migration results to CSV to plan upgrade, remediation and phased validation.
2424

2525
## Prerequisites
2626

2727
Before you start:
2828
- You have an **Azure Synapse Analytics workspace** that contains pipelines.
2929
- You have access to a **Microsoft Fabric tenant** and a **Fabric workspace**.
30-
- If you want to preserve your folder structure, **recreate the same folders** in your Fabric workspace first, then migrate folder by folder.
30+
- To preserve your folder structure, **create the same folders in your Fabric workspace first**, then migrate pipelines one folder at a time.
3131

32+
## Migrate Spark artifacts (Notebooks + SJDs) to Fabric using the Spark migration assistant before migrating Synapse pipelines
33+
If your Synapse pipelines include Notebook and/or Spark job definition (SJD) activities, migrate those Spark artifacts to Fabric first. This ensures the pipeline migration experience can map those activities to the correct Fabric items instead of leaving them unmapped.
3234

33-
## Step 1: Run an assessment in Azure Synapse Analytics
35+
Use the [Synapse-to-Fabric Spark Migration Assistant](/fabric/data-engineering/synapse-to-fabric-spark-migration-assistant) to migrate Spark-related items from your Synapse workspace into a Fabric workspace.
36+
The assistant supports migrating Spark pools (to Fabric environments), notebooks, Spark job definitions, and lake databases (to Fabric lakehouses/shortcuts).
37+
38+
39+
## Migrate Synapse pipelines using the built-in Synapse pipelines migration experience
40+
After creating your Spark artifacts in Fabric, migrate pipelines using the Synapse pipelines migration UX (Preview). This built-in experience helps you assess readiness, understand compatibility gaps, and migrate supported pipelines to Fabric Data Factory.
41+
When the pipelines migration runs:
42+
43+
If matching Fabric notebooks/SJDs already exist, the migration can map the corresponding activities to those Fabric items.
44+
If the target Fabric notebooks/SJDs don’t exist yet, those activities may be left unmapped/deactivated until you create the required Fabric items and update the refer.
45+
46+
### Step 1. Run an assessment in Azure Synapse Analytics
3447

3548
- In **Azure Synapse Analytics**, open the workspace you want to assess.
3649
- In the **Integrate** hub, select **Migrate to Fabric (Preview)**, then select **Get started**.
@@ -46,12 +59,12 @@ Each pipeline is categorized using one of the following statuses:
4659
| Status | What it means |
4760
|---|---|
4861
| **Ready** | Good to go for migration. |
49-
| **Needs review** | Changes are required before migration. |
62+
| **Needs review** | Changes are required before/after migration. |
5063
| **Coming soon** | Support is in progress; migrate later. |
5164
| **Unsupported / Not compatible** | No equivalent in Fabric; refactor required. |
5265

5366

54-
## Step 2: Select pipelines to migrate
67+
### Step 2. Select pipelines to migrate
5568

5669
After reviewing results, select the Synapse pipelines you want to migrate to your Fabric workspace.
5770

@@ -61,7 +74,7 @@ A phased approach works well:
6174
- Start with **Ready** pipelines to validate end-to-end behavior.
6275
- Then address **Needs review** items and rerun assessment to confirm progress.
6376

64-
## Step 3: Map linked services to Fabric connections
77+
### Step 3. Map linked services to Fabric connections
6578

6679
In the migration flow, select a destination **Fabric workspace**, then map **Synapse linked services** to **Fabric connections**.
6780

@@ -77,7 +90,7 @@ For guidance on creating and managing connections in Fabric, see
7790
> Pipelines can migrate even if you don’t map connections, but **activities that use those connections remain deactivated** until you configure them in Fabric and reactivate them.
7891
7992

80-
## Step 4: Complete migration
93+
### Step 4. Complete migration
8194

8295
After you map linked services to Fabric connections, select **Confirm** to complete migration.
8396

@@ -88,7 +101,7 @@ When migration completes, open the destination folder in your Fabric workspace a
88101
> [!NOTE]
89102
> Pipelines migrate safely, with **triggers disabled by default**, so you stay in control of execution.
90103
91-
## Post-migration checklist
104+
### Step 5. Post-migration validation
92105

93106
After migration:
94107
1. Validate connections and credentials.
@@ -105,6 +118,6 @@ Use these resources to round out your end-to-end Synapse-to-Fabric migration pla
105118
- [Upgrade your Azure Data Factory pipelines to Fabric](/fabric/data-factory/how-to-upgrade-your-azure-data-factory-pipelines-to-fabric-data-factory)
106119
- [Migration Assistant for Fabric Data Warehouse - Microsoft Fabric | Microsoft Learn]/fabric/data-warehouse/migration-assistant)
107120
- [Spark Synapse to Fabric Spark Migration Assistant (Preview)](/fabric/data-engineering/synapse-to-fabric-spark-migration-assistant)
108-
- [Spark Synapse to Fabric Spark Migration Assistant (Preview) (review branch)](https://review.learn.microsoft.com/en-us/fabric/data-engineering/synapse-to-fabric-spark-migration-assistant?branch=release-fabsqlcon-2026-de)
121+
- [Synapse-to-Fabric Spark Migration Assistant](/fabric/data-engineering/synapse-to-fabric-spark-migration-assistant)
109122

110123

0 commit comments

Comments
 (0)