Make T‑SQL notebook execution fully compatible with Service Principals by removing or replacing internal OBO calls that reject SPNs.
When pipelines or automated runs execute Fabric notebooks using a Service Principal (SPN), T‑SQL notebook cells can fail because internal Fabric calls use an on‑behalf‑of (OBO) authentication flow that does not accept SPNs. This breaks CI/CD, scheduled jobs, and automation that must run under non‑user identities.
Request:
Ensure T‑SQL notebook execution does not rely on OBO flows that reject Service Principals.
Make notebook runtime APIs and internal calls accept Service Principals consistently.
Publish clear documentation listing required permissions and recommended configuration for Service Principals when running notebooks.
See error here: (Moving to Stored procedures is step backwards we want move forward with -t-sql notebooks for enterprise scale usage ) https://community.fabric.microsoft.com/t5/Data-Engineering/Fabric-Pipeline-T-SQL-Notebook-and-Service-principal/m-p/5139358#M15589
Recent ideas
Org apps - Cannot be arranged in folders and do not stay hidden
Currently, Organizational Apps (Org Apps) are displayed in the standard Apps section of the Get Apps experience, alongside regular workspace apps. For organizations managing large-scale Power BI depl...akonda1 hour agoNew MemberNew4Views0likes0CommentsIncrease or Make Configurable the Power BI Browser Tab Limit (Currently 20 Items)
Power BI users frequently work across multiple reports, dashboards, semantic models, notebooks, and Fabric artifacts simultaneously. The current browser limitation of 20 open Power BI/Fabric items re...sharadmahajan4 hours agoRegular VisitorNew339Views21likes3CommentsAdd "NO SELECTION" default selected option to slicers
Scenario Currently, slicers have two states: No value selected (bogs report down) BI dev preselects one or more data values (problematic when reports are consumed by other clients/users) Option...arpost6 hours agoPost ProdigyNew8Views0likes0Comments