Migrate Azure Synapse Spark workloads to Microsoft Fabric with code replacements.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "synapse-migration" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/skills-for-fabric/main/skills/synapse-migration/SKILL.md 2. Save it as ~/.claude/skills/synapse-migration/SKILL.md 3. Reload skills and tell me it's ready
Please migrate this Azure Synapse Spark notebook to a Microsoft Fabric Lakehouse, preserve the logic, and convert all mssparkutils calls to notebookutils, including the env-to-runtime namespace change.
Fabric-ready notebook code plus a list of replaced APIs and migration notes.
Please review this Synapse code for Linked Services usage and rewrite it using Microsoft Fabric Data Connections or OneLake Shortcuts, explaining each replacement.
Rewritten code or configuration guidance with a step-by-step mapping from Linked Services to Fabric equivalents.
I am planning to migrate a Synapse Spark workspace to Fabric. Based on the current Spark Pools, Lake Databases, Notebooks, and Spark Job Definitions, provide a migration plan, priorities, and a risk checklist.
A structured migration plan with component mapping, execution order, compatibility risks, and validation recommendations.
Update Check — ONCE PER SESSION (mandatory) The first time this skill is used in a session, run the check-updates skill before proceeding.
- GitHub Copilot CLI / VS Code: invoke the
check-updatesskill.- Claude Code / Cowork / Cursor / Windsurf / Codex: compare local vs remote package.json version.
- Skip if the check was already performed earlier in this session.
CRITICAL NOTES
- To find workspace details (including its ID) from a workspace name: list all workspaces, then use JMESPath filtering
- To find item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace, then use JMESPath filtering
mssparkutilsandnotebookutilsshare the same API surface in most cases — the namespace is the primary change- Linked Services have no direct REST API equivalent in Fabric — they are replaced by Data Connections (for external sources) and OneLake Shortcuts (for storage mounts)
These companion documents provide general Fabric REST patterns. Do NOT read them upfront — reference only when a specific phase requires a pattern not already covered in this skill's resource files:
az rest / az login CLI patterns, authentication recipessqldw-authoring-cli skill)Auth, API endpoints, and item payloads are fully documented in this skill's own files. The common docs above are fallback references only.
| Topic | Reference |
|---|---|
| Migration Orchestrator | migration-orchestrator.md |
| API-Driven Migration Workflow | § API-Driven Migration Workflow |
| Migration Workload Map | § Migration Workload Map |
| Spark Pool → Environment Migration | spark-pool-migration.md |
| Lake Database → Lakehouse Migration | lake-database-migration.md |
| External Hive Metastore → Lakehouse Migration | external-hms-migration.md |
| Notebook & SJD Migration | spark-item-migration.md |
| Library Compatibility (Synapse vs. Fabric RT 1.3) | library-compatibility.md |
| Connector Refactoring (Kusto, Cosmos DB, ADLS OAuth) | connector-refactoring.md |
mssparkutils → notebookutils API Mapping | utility-api-mapping.md |
| Linked Services → Data Connections / Shortcuts | connectivity-migration.md |
| Before/After Code Patterns (incl. Catalog API gaps) | code-patterns.md |
| Migration Report (with Fabric portal links) | migration-report.md |
| Migration Troubleshooting Guide | migration-gotchas.md |
| Validation & Testing | validation-testing.md |
| Security & Governance (Production Readiness) | security-governance.md |
| T-SQL & Spark Configuration Differences | § T-SQL & Spark Configuration Differences |
…
Inspect Fabric alerts, notifications, and automated actions via read-only API calls.
Run authoring T-SQL for Fabric warehouses and SQL endpoints from CLI.
Monitor, inspect, and query Fabric Dataflows Gen2 through a read-only CLI.
Query Fabric Eventhouse data, analyze time series, and monitor ingestion health.
Migrate Databricks notebooks, jobs, and paths into Microsoft Fabric.
List, inspect, and validate Microsoft Fabric Eventstream topology and configuration.
Migrate HDInsight Spark, Hive, and Oozie workloads to Microsoft Fabric.
Build Fabric Spark workflows, author notebook code, and manage lakehouse resources.
Diagnose Spark failures, session issues, and performance bottlenecks in Microsoft Fabric.
Interactively analyze lakehouse data with PySpark, Livy sessions, and Spark SQL.
Use MCP to manage Microsoft Fabric data and analytics operations.
Run read-only T-SQL queries on Fabric warehouse and lakehouse data.