The core issue is the inability to directly access Microsoft Fabric SQL Databases from within Fabric Notebooks, despite the availability of JDBC and ODBC connection strings. The built-in notebook authentication token library appears to be missing Fabric SQL as an option.
It does not currently appear possible (or at least not documented how) to access a Fabric SQL Server Database from within a Fabric Notebook. I see JDBC and ODBC connection strings, but these don't work apparently because the library to create authentication tokens is missing Fabric SQL as an option.
Current Impact
1. Enterprises must create complex workarounds ("Rube Goldberg architectures") to establish basic data flows that leverage SQL Server
2. The platform fails to deliver on its "unified" promise, leading to a loss of faith in the Fabric brand
3. SQL Server's established strengths are not being leveraged effectively, further eroding trust that Fabric can deliver on enterprise data needs
Summary
This is a critical feature request that highlights a significant gap in Microsoft Fabric's platform integration. The inability to easily access Fabric SQL Databases from Fabric Notebooks undermines the platform's unified vision and creates unnecessary complexity for enterprise users. The request is well-justified, technically feasible, and would bring significant value to the platform.
on:
Button Slicer width and Height should not changed
on:
Small multiples category axis can't be a local cal...
miguel
on:
Support dynamic sources and destinations in Datafl...
@jboarman - Our team is working to get Notebook integration with SQL database in Fabric. Our phase I of this feature is out - it's called magic T SQL. Now just add the below line in a cell and connect to your database easily-
%%tsql -artifact sqldb1 -type SQLDatabase -bind df2
please check out this document for further details - Run T-SQL code in Fabric Python notebooks - Microsoft Fabric | Microsoft Learn
Thanks
Sukhwant