REST API Support for Setting Lakehouse Datasource Connection to Service Principal(lake fix identity)
Problem:
Currently, when a dataset is connected to a Lakehouse as a datasource in Power BI Fabric, it defaults to a cloud connection mapped to SSO. In embedded mode, reports built on these datasets fail due to a lack of identity, as they do not inherit authentication from the service principal. To resolve this, users must manually adjust the datasource settings via the Power BI service
https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-fixed-identity
Proposed Solution:
Introduce a new REST API or extend the current API functionality to allow programmatic setting (or re-setting) of the connection to the service principal, including updating datasources.
Benefits:
Automates the process, reducing manual intervention
Minimizes downtime for embedded reports
Enhances developer experience and deployment efficiency
Ensures consistency in authentication settings across different environments
Impact:
This feature will significantly improve the workflow for organizations embedding Power BI reports using service principals, ensuring seamless and automated datasource authentication.
1 Comment
- cdudenRegular VisitorThis same issue is a major blocker for our embedded scenario. Not being able to do this means we have to manage reports across hundreds of customer workspaces instead of having a common, shared report that we can bind to the customer's data at run time. Major gap.
Recent ideas
OneLake Catalog full-text and content search
Why is it not possible to search OneLake by item description or even content? So I was thinking about how a user can find a table if they don't know in which lakehouse it is located? Why can't you se...TePe6 hours agoHelper IVPlanned1.1KViews21likes5Comments