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
Support SNC Authentication for SAP BW in Power BI Report Server
Organizations are increasingly moving toward encrypted and certificate-based authentication for SAP BW connections due to security and compliance requirements. Currently, Power BI Report Server (PBI...Indramouli1 day agoNew MemberNew6Views0likes0CommentsHow to remind the Global team to respond to ECNs with greater efficiency
Suggest Power BI send emails to each responsible person, and display how many days they have spent handling each ECN, compared to the required number of calendar days for completion.richardzhu1 day agoNew MemberNew36Views5likes2Comments