fabrical.
Back to feed
Fabric Recent Update·Mar 26, 2026·Jene Zhang

Fabric notebooks support Lakehouse auto-binding in Git (Preview)

View original article

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 notebooks now support lakehouse auto-binding when used with Git. It is designed to simplify multi-environment workflows and reduce the operational overhead of managing lakehouse references across development, test, and production workspaces.

Comparing hard-bind notebooks to a specific lakehouse, teams now can adopt cleaner Git-based CI/CD workflows and focus on versioning notebook logic rather than environment-specific configuration.

Simplifying notebook and Lakehouse management

In practice, notebooks often move across multiple workspaces through Git sync or deployment pipelines. Historically, lakehouse references required careful handling during these transitions, sometimes resulting in manual rebinding or environment-specific fixes.

With lakehouse auto-binding in notebook, Fabric can resolve the appropriate lakehouse as notebooks move across Git-connected workspaces. This makes notebooks more portable and better aligned with Fabric’s lifecycle management model, where metadata is tracked in Git while data is always preserved.

How auto-binding works in Git workflows

To use lakehouse auto-binding, you must explicitly enable the setting from the notebook settings page, it manages all lakehouses in the notebook, including the default and any added lakehouses. Once enabled, the configuration is captured as part of the Git workflow.

In the Git repository view, a new file named notebook-settings.json is generated to store the notebook configuration used across CI/CD workflows. This file is managed by Fabric and ensures consistent behavior as notebooks move across environments.

While the configuration is visible in the repository, it is not recommended to edit notebook-settings.json directly. To ensure workflow consistency and avoid configuration drift, users should always enable or update auto-binding through the Fabric user experience rather than modifying the file manually.

Get started

If you’re using Git integration with Fabric notebooks, lakehouse auto-binding can help simplify multi-environment development and deployment. Learn more, explore Notebook source control and deployment.

Related blog posts

Fabric notebooks support Lakehouse auto-binding in Git (Preview)

Microsoft JDBC Driver for Microsoft Fabric Data Engineering (Generally Available)

The enterprise-grade JDBC driver enables secure, flexible, and performant connectivity to Spark SQL workloads running in Microsoft Fabric, using Fabric’s Livy APIs as the execution layer.

Upgrade your Synapse pipelines to Microsoft Fabric with confidence (Preview)

To modernize workloads on Microsoft Fabric, bringing Synapse pipelines forward is a critical next step.

Microsoft Fabric

Accelerate your data potential with a unified analytics solution that connects it all. Microsoft Fabric enables you to manage your data in one place with a suite of analytics experiences that seamlessly work together, all hosted on a lake-centric SaaS solution for simplicity and to maintain a single source of truth.

Get the latest news from Microsoft Fabric Blog

This will prompt you to login with your Microsoft account to subscribe

Visit our product blogs

View articles by category

View articles by date

What's new

Microsoft Store

Education

Business

Developer & IT

Company

  • © 2026 Microsoft
  • Manage Cookies
  • Contact Microsoft
  • Privacy
  • Terms of use
  • Trademarks
  • About our ads
#Announcements#Data Engineering#Data Science