Synapse Migration
Port Azure Synapse Analytics Spark workloads to Microsoft Fabric. Translates mssparkutils calls to notebookutils (including the env→runtime namespace change), replaces Linked Services with Fabric Data Connections and OneLake Shortcuts. Covers Spark Pools, Lake Databases, Notebooks, and Spark Job Definitions. Use when the user wants to: (1) port Synapse Spark notebooks to Fabric Lakehouse or Spark Job Definitions, (2) replace mssparkutils or Linked Services in Synapse code. Triggers: "migrate from synapse", "synapse to fabric", "mssparkutils to notebookutils", "synapse linked service replacement", "port synapse notebooks", "synapse workspace migration".
30-Second Summary
Synapse Migration is an agent-readable workflow from microsoft/skills-for-fabric for synapse migration.
It gives the agent a trigger, ordered guidance, and source-backed checks instead of treating synapse migration as a generic tool.
Use it as a brief only while the linked SKILL.md remains available and the risk boundary is still accurate.
1-Minute Read
What it is
Synapse Migration packages instructions from microsoft/skills-for-fabric into a reusable agent skill brief. The original source is a public SKILL.md file, so the brief can point readers back to the executable workflow instead of a product landing page.
When to use it
Use it when a user asks for help around synapse migration and the agent needs a repeatable workflow, checklist, or review path rather than broad background information.
How to test it first
Open the linked SKILL.md, confirm the trigger and procedure still match synapse migration, list the risk boundary, then ask the agent to apply the smallest read-only step to a sample task.
Watch out
Do not present this as a generic app or platform. Keep the scope tied to microsoft/skills-for-fabric. Risk boundary: CI/CD, deploy, release, rollback, and migration steps must start with read-only inspection and an approval gate; database, Fabric workspace, notebook, lakehouse, warehouse, or Power BI changes need credential and production-data approval; cloud resources, RBAC, credentials, tokens, and private keys must not be changed or exposed without a separate approval; Microsoft Fabric-specific workflow; do not describe it as a generic data engineering skill.