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.
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.
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 … Continue reading “Fabric Notebook Public APIs (Generally Available)”
This release brings consistent, secure, and scalable configuration management directly into notebooks—streamlining environment-aware development and CI/CD workflows without hardcoding. Why it Matters As projects grow, managing environment-specific settings can become complex. With Variable Library support in notebooks, you can: Key Highlights The following is an example of how to use Variable Library in notebook. Resources
The Fabric notebook version history feature has launched! This new feature is designed to significantly improve your experience in developing and managing notebooks by providing robust built-in version control capabilities. Highlights These enhancements are part of our ongoing efforts to improve collaboration, reproducibility, and the overall user experience within Fabric. We believe these updates will … Continue reading “Notebook Live Versioning”
