Include User Identity in Power BI Embedded Logs (Especially Exports for Compliance) in App-Owns-Data
Currently, the logging for Power BI Embedded for App-Owns-Data scenarios doesn't capture any info pertaining to a user's identity. This is a pretty significant lack as it means there is no way to know when a specific user views a report or performs certain actions. One of the biggest problems this introduces is that organizations cannot determine which user performed an export of data. This introduces significant compliance issues and poses problems in terms of general audit/security practices.
Please add the option to include a UPN in the logs for app-owns-data scenarios. The app would obviously need to somehow supply that context to PBI, but the lack of this means organizations either cannot use app-owns-data OR have to come up with a custom Export method, which may not have the same level of security that Microsoft provides with the native Export.
Recent ideas
Make workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen31 minutes agoAdvocate INew287Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi1 hour agoMicrosoft EmployeeNew13Views6likes0CommentsAuto-propagate Lakehouse (Direct Lake) permissions to users assigned to a Power BI App audience
Problem When a Power BI report uses a Live Connection to a Direct Lake Semantic Model, end users must have explicit ReadAll / ReadData permissions on the underlying Lakehouse (or its SQL analytics e...majofv3 hours agoNew MemberNew5Views1like0Comments