Fabric Notebook Public APIs (Generally Available)

[Anonymous]

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. 

---

Fabric Notebook Public APIs (Generally Available), enabling data engineers and data scientists to programmatically manage and execute notebooks as part of modern, automated data workflows.

With this release, Fabric notebooks become fully addressable through public APIs—from CRUD operations to on-demand execution—unlocking new scenarios across CI/CD, orchestration, and system integration. Most importantly, the Run Notebook API now supports returning an exit value, making it easier than ever to build robust, conditional pipelines around notebook execution.

Why notebook public APIs matter

Notebooks are central to how teams explore data, build transformations, and develop analytics logic. Previously, integrating notebooks into automated systems often required workarounds or platform-specific tooling.

With Fabric Notebook Public APIs, you can treat notebooks as first-class programmable assets, automate notebook lifecycle management at scale, execute notebooks on demand and use their results to drive downstream decisions, and integrate Fabric notebooks with external orchestrators, CI/CD systems, and enterprise platforms.

Full lifecycle management with CRUD APIs

Fabric Notebook Public APIs provides full Create, Read, Update, and Delete support for notebook items in a workspace.

Supported actions include creating notebooks, updating notebook content, retrieving notebook definitions, listing notebooks in a workspace, and deleting notebooks. These capabilities make it easy to build CI/CD workflows, sync notebooks across environments, and manage notebooks programmatically at scale.

Run notebooks on demand with the Job Scheduler API

Beyond management, the public APIs enable you to run notebooks on demand using the Job Scheduler API, together with Cancel job instance and get job instance. You can parameterize notebook runs, customize session configuration, specify environments and lakehouses, monitor execution status, and cancel runs if needed.

This allows notebooks to be invoked as part of larger workflows—whether from Fabric pipelines, external schedulers, or custom automation services.

New in GA: return exit values for better orchestration

A key enhancement in this GA release is support for returning an exit value from notebook runs. This enables notebooks to communicate structured outcomes back to the caller, making it easier to implement conditional branching, success or failure signaling, and downstream orchestration logic.

With exit values, notebooks evolve from simple execution steps into decision-making units within complex data pipelines.

Secure automation with Service Principal support

Notebook Public APIs support service principal authentication for both CRUD and execution APIs, enabling secure, unattended automation and enterprise-grade CI/CD integrations.

Get started

To explore the full API surface and usage examples, see the documentation: Items - REST API (Core) | Microsoft Learn and Job Scheduler - REST API (Core) | Microsoft Learn.