skills.rest
paulasilvatech
paulasilvatechOFFICIAL
Explore all skills by this author →
GitHub

synapse-migration

Migrate Azure Synapse Spark workloads to Microsoft Fabric via REST APIs.

Updated Aug 19, 2026
Search Tags:#migration#Spark#lakehouse#Synapse#onelake#microsoft fabric#notebookutils
One-click install
npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill synapse-migration-paulasilvatech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: synapse-migration
Source: https://github.com/paulasilvatech/Fabric-Agentic-SDLC/tree/main/.github/skills/synapse-migration
Command: npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill synapse-migration-paulasilvatech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Moving Spark notebooks, Spark Job Definitions, Lake Databases, and Spark Pools from Azure Synapse Analytics to Microsoft Fabric requires rewriting mssparkutils calls, replacing Linked Services, and recreating catalog metadata — a manual, error-prone process without a structured API-driven workflow. ## Core Features & Use Cases - Phased Migration Orchestration: Migrates Spark Pools to Fabric Environments, Lake Databases (built-in or external Hive Metastore) to Lakehouses with OneLake Shortcuts, and Notebooks/SJDs with lakehouse binding, executed in dependency order. - Code Refactoring Guidance: Provides before/after patterns for mssparkutils → notebookutils (including the env→runtime namespace change), Linked Services → Data Connections/Shortcuts, Kusto/Cosmos DB connectors, ADLS OAuth token providers, and unsupported spark.catalog methods. - Validation & Troubleshooting: Includes a gotcha catalog (G1–G9), feature parity matrix, capacity sizing tables, and post-migration validation checks for row counts, schemas, and shortcut health. - Use Case: A data engineer needs to port a Synapse workspace with 5 Lake Databases and 40 notebooks to Fabric. The skill inventories the databases via the Synapse data-plane API, creates Lakehouses with schema mapping, creates ADLS shortcuts per table, refactors notebook code, and produces a migration report. ## Quick Start Ask the AI to migrate your Synapse workspace to Microsoft Fabric by providing the Synapse workspace name and target Fabric workspace name.

Frequently Asked Questions about synapse-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Synapse Spark notebooks to Microsoft Fabric?▼

Migrate Synapse notebooks to Fabric by replacing mssparkutils imports with notebookutils, rebinding the notebook to a Fabric Lakehouse and Environment, and deploying via the Fabric Items REST API. Environments and Lakehouses must exist before notebooks can bind to them.

How to replace mssparkutils with notebookutils in Fabric?▼

Replace mssparkutils with notebookutils by changing the namespace — most APIs are identical. The main exception is mssparkutils.env, which becomes notebookutils.runtime.context, and getSecret now takes a full Key Vault URL instead of a linked service name.

What replaces Synapse Linked Services in Microsoft Fabric?▼

Synapse Linked Services are replaced by Fabric Data Connections for external databases and OneLake Shortcuts for ADLS Gen2 or Blob storage mounts. Key Vault linked services are replaced by direct notebookutils.credentials.getSecret calls using the vault URL.

Does Microsoft Fabric support external Hive Metastore from Synapse?▼

Fabric does not support connecting to an external Hive Metastore. Metadata must be extracted via JDBC queries against the HMS database and recreated in the Fabric Lakehouse catalog, with table data mounted as OneLake Shortcuts.

Why does spark.read.synapsesql fail after migrating to Fabric?▼

spark.read.synapsesql fails because the Synapse SQL connector has no Fabric equivalent. Replace it with a direct Delta read from the migrated Lakehouse table, or use JDBC with an Entra ID access token against the Fabric Warehouse SQL endpoint.

What Synapse workloads cannot be migrated to Fabric?▼

GPU-accelerated Spark pools and .NET for Spark (C#/F#) Spark Job Definitions are not supported in Fabric and are migration blockers. These workloads must remain in Synapse, be rewritten in PySpark, or move to Azure ML.

Related Skills

Explore More Data & Analytics Skills→
patrikboroschpatrikborosch
14

synapse-migration

Automate Azure Synapse Spark workload migration to Microsoft Fabric via REST APIs.

Community
Advanced
9vantage9vantage

e2e-medallion-architecture

Implements Bronze/Silver/Gold medallion lakehouse architectures in Microsoft Fabric using PySpark and Delta Lake.

Community
Advanced
rritecrritec
3

synapse-migration

Migrate Azure Synapse Spark workspaces into Microsoft Fabric with validation and reporting.

Community
Advanced
9vantage9vantage

pipeline-migration

Migrate Synapse Data Factory pipelines to Microsoft Fabric Data Factory via REST APIs.

Community
Advanced