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
1 Comment
- ga4fRegular Visitor
I'm facing the same issue, how the heck they say that is GA.
Hoping for a improvement.
Recent ideas
📉 How Would You Investigate a 20% Drop in Revenue?
A data analyst shouldn’t stop at identifying what happened. The real questions are: Where did the decline occur? → Why did it happen? → What caused it? → What should we do next? By analyzing regio...aliulmurtaza1 hour agoNew MemberNew4Views0likes0CommentsAdd “Don't show this again” option to Power Query Insert Step warning
When a transformation is performed while an earlier Applied Step is selected, Power Query displays the “Insert Step” warning every time. This is useful for new users, but becomes unnecessary for expe...bjs17464 hours agoNew MemberNew3Views0likes0Comments