Fabric Updates Blog

4 MIN READ

Fabric CLI in Azure DevOps: automation without friction (Preview)

Microsoft Employee

6 months ago

If you haven’t already, check out Arun Ulag’s hero blog “FabCon and SQLCon 2026: Unifying databases and Fabric on a single, complete platform” for a complete look at all of our FabCon and SQLCon announcements across both Fabric and our database offerings.

Modern analytics platforms demand modern DevOps practices. As organizations standardize Azure DevOps for CI/CD, they expect seamless integration with the services that power their data and analytics workloads. With Microsoft Fabric, that expectation is fully met.

The Fabric CLI—built for CI/CD

The Fabric CLI (fab) enables teams to automate and manage Fabric environments through simple, scriptable commands. When used through the Fabric Azure DevOps extension, the CLI is automatically provisioned in the pipeline runtime environment.

With the Fabric ADO Extension and its built-in Fabric CLI task, your pipelines can:

Deploy and promote artifacts across environments
Manage workspaces and items
Trigger and orchestrate operations
Integrate Fabric deployments into CI/CD flows

The CLI is automatically provisioned in the pipeline runtime environment, removing one of the most common sources of CI/CD friction: tool installation and environment preparation.

Zero setup, zero friction

Traditionally, using a CLI in CI/CD requires explicit installation steps embedded in every pipeline definition. With automatic CLI availability in Azure DevOps, the pipeline becomes dramatically simpler.

With the Fabric ADO Extension—clean and declarative:

- task: FabricCLI@1

inputs:

scriptType: 'ps'

scriptLocation: 'inlineScript'

inlineScript: 'Fab ls'

FabricCLIVersion: 'v1.2.0'

This streamlined experience delivers immediate benefits:

No dependency scripting
No agent-level configuration
No external binary downloads
No repetitive setup steps in every pipeline

The CLI is simply there when you need it.

Flexible scripting: your language, your style

The Fabric CLI task is not limited to a single scripting language. It supports four script types to match whatever is standard in your team or required by your agent OS.

Script Type	scriptType value	Agent OS
PowerShell	'ps' or 'powershell'	Windows
PowerShell Core	'pscore'	Windows, Linux, macOS
Batch	'batch'	Windows only
Shell (Bash)	'bash' or 'sh'	Linux, macOS

Choose the script type that fits your agent pool and team conventions. Cross-platform teams typically use PowerShell Core (pscore) so the same pipeline YAML runs on both Windows and Linux agents without modification.

Script Location: inline or file path

The task also gives you full control over where your script lives. The script Location input accepts two modes:

inlineScript—write the script directly inside the YAML definition
scriptPath—point to a .ps1, .sh, or .bat file checked into your repository

Option A: inline script

Ideal for short, self-contained automation that lives alongside the pipeline definition. The entire script is embedded in the YAML:

- task: FabricCLI@1

displayName: 'Fabric CLI script with env vars'

inputs:

scriptType: 'bash'

scriptLocation: 'inlineScript'

inlineScript: |

fab ls

fab create ws3-test.Workspace -P capacityname=FabCapacity

fab cd ws3-test.Workspace

fab cd ..

fab rm ws3-test.Workspace -f

FabricCLIVersion: 'v1.2.0'

FabricCLIEncryption: true

Option B: script file path

Best for complex automation or scripts shared across multiple pipelines. The script is stored in source control and referenced by path:

- task: FabricCLI@1

displayName: 'Run Fabric deployment script'

inputs:

scriptType: 'pscore'

scriptLocation: 'scriptPath'

scriptPath: '$(Build.SourcesDirectory)/scripts/deploy-fabric.ps1'

FabricCLIVersion: 'v1.2.0'

Streamlined pipelines, improved upkeep

Enterprise environments often manage dozens or hundreds of pipelines.

Automatic CLI installation eliminates that boilerplate and keeps YAML definitions clean and readable. Pipelines focus on business logic and deployment intent—not environment preparation.

This directly improves:

Pipeline clarity and readability
Long-term maintainability
Ease of troubleshooting and debugging
Onboarding for new engineers

Deterministic and consistent execution

One of the biggest challenges in CI/CD is version drift. Different agents, environments, or teams may accidentally use different CLI versions, leading to unpredictable behavior and hard-to-reproduce bugs.

By embedding the CLI within the Azure DevOps extension:

Pipelines use a supported and validated CLI version
Behavior is consistent across all environments
Deployments become more deterministic
Operational risk is reduced

Consistency is foundational to enterprise DevOps maturity. With the Fabric ADO Extension, this is built into not bolted on.

Get Started

The Fabric Azure DevOps Extension is available on the Azure DevOps Marketplace. Install the extension once, add the FabricCLI@1 task to your pipeline, and let the platform handle the rest.

Add_CLI_task_to_your_pipeline

Figure 1 Fabric ADO extension - CLI task.

- task: FabricCLI@13

inputs:

scriptType: 'ps'

scriptLocation: 'inlineScript'

inlineScript: 'Fab ls'

FabricCLIVersion: 'v1.2.0'

No installation. No friction. From pipeline trigger to Fabric command, it all runs in a single task.

The Fabric CLI task extension is available now on the Visual Studio Marketplace. Add it to your Azure DevOps organization and start managing Fabric resources directly from your pipelines.