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
Support Managed Private Endpoint for Azure DocumentDB (with MongoDB compatibility)
Fabric does not offer a secure way to connect to Azure DocumentDB (with MongoDB compatibility). It is currently only supporting the Azure Cosmos DB for MongoDBmorten-gn28 minutes agoNew MemberNew3Views0likes0CommentsAllow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels1 hour agoAdvocate IIINew176Views0likes2CommentsMake 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...TeemuMultanen2 hours agoAdvocate INew292Views47likes2CommentsSupport 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...ewarstdhyjugkhi2 hours agoMicrosoft EmployeeNew16Views6likes0Comments