Skip to content

Commit 6431175

Browse files
authored
Clarify migration steps for Synapse to Fabric
Reworded sections for clarity and improved flow regarding the migration process from Synapse to Fabric.
1 parent 31307b6 commit 6431175

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,6 @@ Before you start:
3535
If your Synapse pipelines include Notebook and/or Spark job definition (SJD) activities, migrate those Spark artifacts to Fabric first. This separation ensures the pipeline migration experience can map those activities to the correct Fabric items instead of leaving them unmapped.
3636

3737
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.
38-
The assistant supports migrating Spark pools (to Fabric environments), notebooks, Spark job definitions, and lake databases (to Fabric lakehouses/shortcuts).
3938

4039
## Migrate Synapse pipelines
4140

@@ -104,7 +103,7 @@ After you map linked services to Fabric connections, select **Confirm** to compl
104103

105104
:::image type="content" source="media/how-to-assess-and-upgrade-your-azure-synapse-analytics-pipelines-to-fabric/successful-migration-completion.png" alt-text="Screenshot showing successful migration." lightbox="media/how-to-assess-and-upgrade-your-azure-synapse-analytics-pipelines-to-fabric/successful-migration-completion.png":::
106105

107-
When migration completes, open the destination folder in your Fabric workspace and review the migrated pipelines.
106+
After migration completes, go to your Fabric workspace to review the migrated pipelines. Each pipeline is created under the workspace and prefixed with its source factory name.
108107

109108
> [!NOTE]
110109
> Pipelines migrate safely with **triggers disabled by default**, so you stay in control of execution.

0 commit comments

Comments
 (0)