activator-cli
Creates and inspects Fabric Activator (Reflex) alerts: rules, their data sources, conditions,…
Migrates Synapse Data Factory pipelines to Fabric Data Factory, turning linked services into Fabric connections, inlining datasets into activities, converting global parameters to Variable Libraries, and mapping SynapseNotebook to TridentNotebook. Use for pipeline JSON. For
$ npx -y skills add microsoft/skills-for-fabric --skill pipeline-migration --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/pipeline-migrationContext preview
The summary Claude sees to decide when to auto-load this skill.
Migrates Synapse Data Factory pipelines to Fabric Data Factory, turning linked services into Fabric connections, inlining datasets into activities, converting global parameters to Variable Libraries, and mapping SynapseNotebook to TridentNotebook. Use for pipeline JSON. For
name: pipeline-migration description: "Migrates Synapse Data Factory pipelines to Fabric Data Factory, turning linked services into Fabric connections, inlining datasets into activities, converting global parameters to Variable Libraries, and mapping SynapseNotebook to TridentNotebook. Use for pipeline JSON. For Synapse Spark notebook code use synapse-migration."
> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry > `x-ms-fabric-skill: pipeline-migration` (`az rest`: `--headers "x-ms-fabric-skill=pipeline-migration"`), > including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.
> **CRITICAL NOTES** > 1. To find workspace details (including its ID) from a workspace name: list all workspaces, then use JMESPath filtering > 2. 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 > 3. Fabric does NOT have a "Dataset" item type — all dataset properties are **inlined** into activity `typeProperties` > 4. Linked Services map to Fabric **Connections** — in pipeline activity JSON, `referenceName` on the activity's `linkedService` block uses the Fabric connection **display name** (not the connection GUID); the connection GUID is used only on Fabric REST API calls > 5. Notebook activities change from `SynapseNotebook` to `TridentNotebook` and reference notebooks by **GUID**, not by name > 6. Synapse global parameters become a **Variable Library** item in Fabric, referenced as `@pipeline().libraryVariables.<name>`. Variable Library `Number` types are not consumable in pipelines — Synapse `Float`/`Double` are mapped to `String` for runtime compatibility > 7. The `Validation` activity type does not exist in Fabric — it must be rewritten as `GetMetadata` + `IfCondition` > 8. **Triggers are intentionally excluded** from this skill — recreate schedules manually in Fabric after migration > 9. SSIS package execution, SHIR-exclusive connectors, and Databricks activities are **parked** — see [pipeline-gotchas.md](resources/pipeline-gotchas.md)
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:
> For the notebook side of the migration (the notebooks that pipeline activities call), use the companion **synapse-migration** skill to migrate the notebook content itself.
---
| Topic | Reference | |---|---| | **Pre-Migration Assessment** (run first) | [pipeline-assessment.md](resources/pipeline-assessment.md) | | **Migration Orchestrator** | [pipeline-orchestrator.md](resources/pipeline-orchestrator.md) | | API-Driven Migration Workflow | [§ API-Driven Migration Workflow](#api-driven-migration-workflow) | | Activity Type Mapping | [activity-mapping.md](resources/activity-mapping.md) | | **Notebook Activity Migration** (primary focus) | [notebook-activity-migration.md](resources/notebook-activity-migration.md) | | Linked Services → Connections | [linked-service-to-connection.md](resources/linked-service-to-connection.md) | | Dataset Inlining | [dataset-inlining.md](resources/dataset-inlining.md) | | Global Parameters → Variable Library | [global-parameters-to-variable-library.md](resources/global-parameters-to-variable-library.md) | | Pipeline Gotchas & Parked Activities | [pipeline-gotchas.md](resources/pipeline-gotchas.md) | | Validation & Testing | [validation-testing.md](resources/validation-testing.md) | | Migration Report | [migration-report.md](resources/migration-report.md) |
> **IMPORTANT — Load only what you need.** Do NOT read all resource files upfront.
| When | Read This File | |---|---| | User asks for an assessment, scope, or plan **before** migrating | [pipeline-assessment.md](resources/pipeline-assessment.md) | | User asks to migrate a full pipeline workspace | [pipeline-orchestrator.md](resources/pipeline-orchestrator.md) | | User asks about activity type mapping or unsupported activities | [activity-mapping.md](resources/activity-mapping.md) | | User has SynapseNotebook activities (most common) | [notebook-activity-migration.md](resources/notebook-activity-migration.md) | | User asks about linked services or connections | [linked-service-to-connection.md](resources/linked-service-to-connection.md) | | User asks about Copy, Lookup, or GetMetadata with datasets | [dataset-inlining.md](resources/dataset-inlining.md) | | User has global parameters to convert | [global-parameters-to-variable-library.md](resources/global-parameters-to-variable-library.md) | | User hits SSIS, SHIR, Databricks, or other blockers | [pipeline-gotchas.md](resources/pipeline-gotchas.md) | | Post-migration verification | [validation-testing.md](resources/validation-testing.md) | | Generating a migration summary | [migration-report.md](resources/migration-report.md) |
---
| Target | Token Audience | |---|---| | Synapse Data Plane (pipelines, datasets, linked services) | `https://dev.azuresynapse.net` | | Synapse ARM (global parameters, workspace properties) | `https://management.azure.com` | | Fabric REST API (cre
Microsoft Fabric Skills are reusable AI assistant instructions for working with Microsoft Fabric. They help GitHub Copilot CLI and compatible AI coding tools understand Fabric workloads, APIs, query patterns, and operational best practices.
Repo: microsoft/skills-for-fabric
Creates and inspects Fabric Activator (Reflex) alerts: rules, their data sources, conditions,…
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as…
Ports existing Databricks notebooks and jobs to Fabric, covering dbutils to notebookutils,…
Manages Fabric Dataflow Gen2 items, including creation, M editing, connections, output…
Manages Fabric deployment pipelines for ALM promotion across dev, test, and prod stages,…
Estimates Fabric capacity cost before a migration by profiling Spark, SQL, Power BI, and…