Currently, Fabric Workspace Identity cannot be used to authenticate against custom APIs protected by Microsoft Entra ID.
Azure Managed Identities support requesting an access token for a specific API audience/resource, making it possible to securely call custom APIs without managing credentials. Fabric Workspace Identity appears to be limited to Fabric-integrated authentication scenarios.
Adding support for acquiring tokens for custom APIs would make Workspace Identity behave more like an Azure Managed Identity and reduce the need to use separate Service Principals with the Client Credentials flow for Fabric workloads.
No CommentsBe the first to comment
Recent ideas
Feature Request: Add a Warning Prompt Before Deleting Tables That Contain Measures
Problem Statement: In Power BI, measures are linked to specific tables. When a developer deletes a table from the model view or report view, Power BI automatically deletes all measures assigned to ...Murtaza_Ghafoor12 minutes agoSuper UserNew2Views0likes0CommentsCustom visuals: allow same-tab navigation & reduce confirm-navigation friction for trusted links
Description: Custom visuals (e.g. Deneb) that trigger navigation via href currently have two limitations that create friction for legitimate, author-controlled use cases: Links always open in a ne...AlexSenEON2 hours agoNew MemberNew5Views0likes0CommentsSeparate Download and Publish Permissions for Power BI Workspaces
Idea / Feature Request Introduce more granular permissions in Power BI to independently control report download and report publishing permissions at the workspace level. Business Scenario We have ...ewarstdhyjugkhi3 hours agoMicrosoft EmployeeNew20Views8likes0CommentsSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull224 hours agoAdvocate INew31Views1like1Comment