fabric-deployment-pipelines

Manage Microsoft Fabric deployment pipelines and CI/CD stage deployments via REST API.

4|1|Updated May 22, 2026
One-click install
npx skills add https://github.com/ThomazRossito/ai-data-agents --skill fabric-deployment-pipelines-thomazrossito
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fabric-deployment-pipelines
Source: https://github.com/ThomazRossito/ai-data-agents/tree/main/plugins/ai-data-agents/skills/fabric-deployment-pipelines
Command: npx skills add https://github.com/ThomazRossito/ai-data-agents --skill fabric-deployment-pipelines-thomazrossito

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually promoting content between Microsoft Fabric workspaces (Dev, Test, Prod) is slow, error-prone, and requires multiple REST calls to initialize operations, poll long-running operations, and validate conflicts. This Skill encapsulates the full CI/CD cycle for Fabric deployment pipelines. ## Core Features & Use Cases - Pipeline Lifecycle Management: Create multi-stage deployment pipelines, assign workspaces to stages, and manage role assignments (RBAC) via the Fabric REST API. - Automated Deploys with LRO Polling: Execute full or selective item deploys between stages with automatic long-running operation polling until success or failure, including conflict resolution policies (PreferRemote/PreferWorkspace). - Audit & Rollback: List deployment operation history, use structured deployment notes for auditing, and perform rollback via re-deploy or Git Integration. - Use Case: A data team needs to promote semantic models and reports from a Development workspace to Testing every sprint. Use this Skill to create the pipeline, assign workspaces, and run the deploy with a single call while the operation is polled to completion. ## Quick Start Ask the agent to create a three-stage Fabric deployment pipeline, assign the Dev, Test, and Prod workspaces, and deploy all content from Development to Testing with a deployment note.

Frequently Asked Questions about fabric-deployment-pipelines

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

FAQPage Schema
How do I deploy content between Microsoft Fabric workspaces with the REST API?▼

Create a deployment pipeline with stages, assign each workspace to a stage, then call the deploy endpoint with source and target stage IDs. The deploy returns a 202 Accepted LRO, which you poll via the operations endpoint until the status is Succeeded or Failed.

Fabric deployment pipelines vs Git integration: which should I use?▼

Use deployment pipelines for workspace-to-workspace promotion across Dev/Test/Prod environments. Use Git integration when you need version control, pull requests, and code review workflows. Since 2025H2, pipelines can also generate automatic commits when Git integration is configured on the target workspace.

Can I deploy only specific items in a Fabric deployment pipeline?▼

Yes, selective deploy is supported by including an items array in the deploy payload with sourceItemId and itemType values such as SemanticModel or Report. Omitting the items array deploys all content from the source stage.

Why does my Fabric deploy fail with a 422 conflict error?▼

A 422 conflict occurs when an item with the same name already exists in the target stage. Resolve it by setting options.conflictResolution.conflictResolutionPolicy to PreferRemote to overwrite the target, or PreferWorkspace to keep the local version.

How do I roll back a Fabric deployment pipeline deploy?▼

There is no native rollback endpoint. Identify the previous working operation via the operations history, restore items in the source stage (using Git integration and updateFromGit if configured), then execute a new deploy with a rollback note.

Why is my Fabric deployment LRO timing out?▼

Large deployments can exceed the default 120-second polling window. Increase the timeout to 300 seconds or implement custom polling against the operations endpoint until the status leaves Running or NotStarted.