Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Did you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now

yaronprigal

Introducing Bulk Export and Import APIs for CI/CD in Microsoft Fabric (Preview)

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. 


Enterprise DevOps teams expect automation, repeatability, and full control over their release pipelines. While Microsoft Fabric provides built‑in Git Integration and deployment experiences, many organizations also require additional CI/CD capabilities that integrate directly into their DevOps tooling and release processes.

To support these, we’re introducing the Bulk Export and Import Item Definition APIs—a new set of REST APIs in Preview.

CI/CD with Fabric item definitions as code

Every item in Microsoft Fabric—such as notebooks, pipelines, reports, and semantic models—are backed by a structured item definition that fully describes its configuration and content. The Bulk Export and Import APIs allow these definitions to be treated as source code:
  • Exported programmatically from a workspace
  • Stored and versioned in Git
  • Validated through pull request workflows
  • Promoted across environments using automated pipelines
This enables a clean separation between authoring, review, and deployment, aligning Fabric with established enterprise DevOps practices.

Git‑based deployment using a build environment

In this CI/CD model, deployments across Microsoft Fabric workspaces are driven from a central Git repository, where Fabric item definitions are treated as code and promoted through a structured release flow. All environments—Dev, Test, and Prod—are aligned to the same main branch, while each stage is deployed independently using dedicated build and release pipelines.

Pipelines typically begin by exporting Fabric item definitions from a development workspace using Fabric Git Integration or the Bulk Export API. These definitions can then be validated in a build environment through automated checks, pull request reviews, and policy enforcement before promotion.

During deployment, the pipeline invokes the Bulk Import API to promote approved item definitions into the target workspace. The API supports both creating new items and updating existing ones in place, while relying on Fabric’s built‑in dependency handling to ensure items are deployed in the correct order. This enables consistent, repeatable deployments into test and production environments without manual intervention.

Figure_1-_Suggested_build_and_release_pipelines_using_bulk_export_import_APIFigure_1-_Suggested_build_and_release_pipelines_using_bulk_export_import_APIFigure 1: Suggested build and release pipelines using bulk export/import API

Built for scale and enterprise automation

The Bulk Export and Import APIs are optimized for:

  • Batch operations across large workspaces.
  • Long‑running, asynchronous execution.
  • Service principal and managed identity authentication.
  • Repeatable, auditable deployments across environments.
These capabilities make them especially well‑suited for enterprise CI/CD pipelines, disaster recovery workflows, and large‑scale environment promotion scenarios.

Get started

The Bulk Export and Import APIs are available as part of the Microsoft Fabric REST API surface in Preview. To learn more about supported item types, authentication, and best practices, see the detailed Fabric API guide.

Check out the complete CI/CD tutorial using the Bulk Export and Import APIs for a step‑by‑step example of this deployment model in action.

As always, we look forward to seeing how your teams use these APIs to build robust, automated CI/CD pipelines in Fabric—and we welcome your feedback in the comments as we continue to evolve the platform.