This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
We’ve heard from many of you that the current remediation path (like taking over an item in the UI) helps in the moment, but it doesn’t solve the underlying problem: enterprise items shouldn’t depend on a user principal to keep working, eliminating risk when people change roles or leave.
Associate an identity (Preview) (user, service principal, or managed identity) with certain Fabric items so that the item does not depend on the creator or owner. This is a limited-scope preview for Fabric Lakehouses and Eventstreams.
In this initial release, items in scope can use the associated identity for the same kinds of operations that historically depended on the item owner.
Use the following API to associate the identity:
POST https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items/{id}/identities/default/assign?beta=true
Prerequisite: the calling identity must have Write permissions on the item (and any dependent/child items impacted by the operation).
GET https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items/{itemId}?include=defaultIdentity
GET https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items?include=defaultIdentity
If you’re a Fabric Administrator, you can also use the admin Get item APIs to view associated identity information across workspaces.
GET https://api.fabric.microsoft.com/v1/admin/workspaces/{workspaceId}/items/{itemId}
Learn more in Manage identities associated with Fabric items.
If you have any suggestions for further enhancements to this feature, please share your ideas on Microsoft Fabric Ideas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.