What problem does it solve? Moving Spark workloads from Azure Synapse Analytics to Microsoft Fabric requires translating mssparkutils calls, replacing Linked Services, recreating Lake Databases as Lakehouses, and reconfiguring Spark Pools — a manual process prone to missed references and broken notebooks. ## Core Features & Use Cases - API-Driven Migration Phases: Orchestrates Spark Pool → Environment, Lake Database → Lakehouse, and Notebook/SJD migration through Synapse and Fabric REST APIs in the correct dependency order. - Code Refactoring Guidance: Provides before/after patterns for mssparkutils → notebookutils, Linked Services → Data Connections and OneLake Shortcuts, Kusto/Cosmos DB connectors, and spark.catalog API gaps. - Validation and Troubleshooting: Includes row-count validation checks, a feature parity matrix, capacity sizing tables, and a gotcha catalog covering blockers like GPU pools and .NET for Spark. - Use Case: A data engineer needs to port a Synapse workspace with 40 notebooks and three Lake Databases to Fabric. The skill inventories the source via REST APIs, creates Lakehouses with shortcuts to existing ADLS data, rewrites notebook utility calls, and produces a migration report with validation results. ## Quick Start Ask the assistant to migrate your Synapse Spark workspace to Microsoft Fabric, providing the Synapse workspace name and target Fabric workspace.