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.
CATEGORY(IES): Data Engineering, Data Science, Announcements
Microsoft Fabric, Fabric Notebooks, Git integration, Source control, CI/CD
Notebooks are rarely just a single file. Real-world notebook projects depend on supporting assets—such as reusable scripts, configuration files—that live alongside notebook code. While these files could be stored in a notebook’s built-in Resources folder, they were not included when committing notebooks to Git. This broke end-to-end source control and made CI/CD workflows harder to adopt.
Today, Fabric notebooks now support committing the built-in Resources folder to Git, enabling true source control for notebook-based projects.
What’s new
With this update, the built-in Resources folder can be included when committing a notebook to Git. Supporting files—such as Python modules, configuration files, and small data assets—are versioned alongside the notebook itself and restored when syncing from a repository.
Notebook resources often include files you don’t want to track in Git—such as large assets, temporary code modules, generated outputs, or test datasets.
To support real-world workflows, Fabric provides multiple ways to control what gets committed:
- Git exclusion rules let you exclude files or folders based on criteria like file name, type, or size—making it easy to keep large files or transient artifacts out of your repository.
- Standard .gitignore support is also available inside the Resources folder, so teams can apply familiar Git patterns to ignore temporary files, test data, or generated content.
Together, these controls help teams keep repositories clean and lightweight, and do not cause a noticeable performance impact on commit or sync operations. They give teams full flexibility without compromising developer velocity or reliability, while still versioning the resource files that matter most.
Designed for safe adoption
To avoid unexpected changes, this feature is opt-in and disabled by default. Once enabled, users have fine-grained control over what gets committed, including exclusion rules and .gitignore support.
Getting started
If your workspace is connected to a Git repository, you can enable resource support from the notebook’s settings page and git settings section. Once enabled, resources are automatically included whenever the notebook is committed.
Support for the Environment Resources folder, as well as integration with deployment pipelines and public APIs, is coming soon—stay tuned.
Learn more, please visit: Notebook source control and deployment
