Make it possible to change owner on all Fabric items types

[fbcideas_migusr]

Make it possible to change owner on all Fabric items types.

Both through API and in user interface (UI).

Otherwise, we will get issues when the item owner leaves the organization.

[fbcideas_migusr]

Related idea: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=1a2d3ce6-7d4d-ef11-b4ac-000d3a0e6066

[fbcideas_migusr]

Related idea: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=0acce98c-7e4d-ef11-b4ac-000d3a0e6066

[Mary_Aho]

We have this issue now. Our lakehouse owner left and now we're seeing errors in the lakehouse itself. The source dataflow was easily transferred to me, but that's clearly not enough. MSFT should escalate this issue.

[jon_catt]

@Sakshi.Jain

What's the time-frame please? Can you ask for more details please?

This issue is obviously affecting many tenants/customers.

[Ben_DuPreez]

@ Sakshi Jain (administrator) - Echoing the previous poster, what is the expected timeframe for this? It is currently affecting customers and I would like to have something to report back to them on.

[sakshi399]

It would be Q1 of 2025, so pretty soon. We have added the this to the public release notes as well.

https://learn.microsoft.com/en-us/fabric/release-plan/admin-governance#take-ownership-fabric-items

[sakshi399]

This feature is in our roadmap. Please stay tuned. We will share more details as they become available. 

[billyswitzerprx]

Excited to hear this is in development! My organization would like the ability to change the owner of a Fabric resource (e.g. - a notebook or pipeline) to the service principal associated with the workspace itself. Right now the notebooks run under the credentials of the developer who created the resource, who may or may not have access to certain resources in Production.

[AlwaysNewDepths]

Also, the ability to assign an Entra AD group instead of an individual user would be beneficial as then everyone in a team has access.