Transfer ownership of a Fabric Lakehouse

[ag91375]

I am looking for a way to transfer ownership of a Fabric Lakehouse.

I found the following link on using PowerShell's Invoke-PowerBIRestMethod for one to take ownership of a Fabric Warehouse. Does this API also support Fabric Lakehouses as well as all other
Fabric artifacts as of April 2024?

https://learn.microsoft.com/en-us/fabric/data-warehouse/change-ownership

Are there any other straightforward ways to transfer ownership of a Fabric Lakehouse?

[MKOD]

This will be a dealbreaker on Fabric overall if this can't be resolved ASAP. 

If I understand this correctly, Microsoft has put their clients in a position where all of their critical production data integration processes could fail just because one person gets a new job and leaves the company?????? - Or goes on parental leave and has their credentials diabled???? Mind-boggling.

Some orgs have processes that are built to capture point-in-time information. If they spend days resolving ownership issues, they kill the integrity of their data. 

Where is the documentation and direction that instructs (impractical as it is) that all Lakehouses should only be created with a service account? Wait, also dataflows, since they define the ownership of the (now hidden) staging lakehouse - which could be used by a dataflow even when a lakehouse is not involved anywhere in the source or destination!

This is an Unaccceptable risk for any organization to take!! - I get that Fabric is not fully featured, and that many problems will be solved iteratively as time goes on, but this is tablestakes - not a nice to have.

[Highandstoned]

Had contact today with support, and they gave me this script. It changes the owner of the sqlendpoint of the lakehouse:

# Install the Power BI PowerShell module if not already installed
Install-Module -Name MicrosoftPowerBIMgmt

# Import the Power BI PowerShell module
Import-ModuleMicrosoftPowerBIMgmt

# Connect to the Power BI service using the new owner credentials and take over the SQL Endpoint

#the workspace guid for the lakehouse you want to have changed

$workspaceid = "xxx"

#the sqlendpoint guid for the lakehouse you want to have changed

$sqlendpoint = "xxx"

Connect-PowerBIServiceAccount

$url = 'groups/' + $workspaceid + '/lhdatamarts/' + $sqlendpoint + '/takeover'
write-host $url
Invoke-PowerBIRestMethod -Url $url -Method Post -Body ""-Verbose

[PhantomThread]

I would like to know if this is still the case and also where resolving this is on the roadmap.

One of our ex-colleagues' owned lakehouses had static data (from a closed system) that is nowhere else in our business and some of our reporting requires it to be available in order to refresh.

I find it astonishing that Microsoft can release a product where someone leaving can put data behind an "ACCESS DENIED" barrier and the ONLY way to resolve this is by raising a support ticket.

I will be raising a upport ticket to hopefully get our issue fixed but I would hope the ability to takeover any and all objects' ownership will be available through the front-end asap

[frithjof_v]

Copy pasting this from another post. Please vote:

Here are some related Ideas regarding ownership of items (please vote/comment inside the Ideas page to highlight the need):

An idea about transfer Lakehouse ownership: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=c507598c-0f44-ef11-b4ad-000d3a02b6d0

Here is a generic Fabric idea related to transferring ownership of Fabric items: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=4cb25a68-7d4d-ef11-b4ac-000d3a0e6066

Why not have option for multiple owners of an item? https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=0acce98c-7e4d-ef11-b4ac-000d3a0e6066 

Or just let the Workspace own the items, so it's not related to a user account.

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

Here is also an idea regarding ability to edit a shortcut's target path (just thought I'd throw that one in as well):

https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=c49f426c-8c4d-ef11-b4ac-000d3a0e6066

[Anonymous]

Hi @ag91375 ,

Thanks for using Fabric Community.

At this point in time the only way to do this is to open support ticket, Have this information ready and add to the ticket: 

1. The customer's Tenant Id
2. The object Id of the Lakehouse to take over
3. The User Object Id of an Administrator, Member, or Contributor of the workspace containing the Lakehouse to become the new owner
4. Approval from the customer's tenant administrator for us to perform a manual SQL script to change the owner on the Lakehouse

If you are looking for this feature in Fabric.

Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.

Hope this helps. Please let me know if you have any further queries.

[tschlidt]

When the creator of a data lakehouse leaves the company there is no way of transfering ownership?   This is a very large barrier for an enterprise company to use lakehouses.   Opening a support ticket for each lakehouse isn't efficient or feasible.

[Anonymous]

Hi @tschlidt ,

Yes I can understand your problem. But at present we have this limitation and only way to resolve this by opening a support ticket. In future we expect product team may develop some functionality to do this.

I appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.

Hope this helps. Please let me know if you have any further queries.

[Anonymous]

Hi @ag91375 ,

We haven’t heard from you on the last response and was just checking back to see if your query was answered. Otherwise, will respond back with the more details and we will try to help.

I would also like to check did you got any chance to create a support ticket? If yes, please provide the ticket number as it would help us to track for more information.

[tschlidt]

A support ticket was created - 2405130040013529 - and support cannot solve the ownership issue for Lake Houses - they keep getting confused between a Data Warehouse and a Lake House.    So the suggestion to open a support ticket hasn't worked.    

I also added the issue to feedback channel as suggested.

At the moment we have directed our organization not to use Lake Houses unless they completely script the data ingestion via notebook.   Which means no manual uploads of files to the lakehouse.   The expectation is that when the owner leaves, someone else will need to recreate the lakehouse.

[mbahonen]

This is a big issue. I can't believe this product was released without a way to easily transfer ownership without needing a support ticket. We are a large company so opening support tickets for things like this is not a simple process and is time consuming. Dataflows and other items are easily transferred/taken over. This should have been a requirement for releasing this product. We now are facing this problem. 

[tschlidt]

Sorry, we are working through our issues.   Currently we've decided to script and recreate lakehouses.   Don't want to be reliant on support tickets.

Similar question - which I did create a ticket for - Gen2 Dataflows use lakehouses for staging data.  All dataflows in a workspace use the same staging lakehouse - who has ownership of the staging lakehouses?   I assume this is the same ownership issue, or are staging lakehouses owned by some system id?

[Anonymous]

Hi @tschlidt ,

You can navigate to the OneLake data hub and search for the term DataflowsStaging and you'll see the Owner column. Often it's going to be based on the creator of the first Dataflow Gen2 within a workspace.

Hope this is helpful.

[Expiscornovus]

Hi @ag91375,

Fabric has a REST API, however it is still pretty new. I have found this method to update Lakehouse properties.

https://learn.microsoft.com/en-us/rest/api/fabric/lakehouse/items/update-lakehouse?tabs=HTTP

Unfortunately, ownership is not one of them.

Not sure if it is even possible via the interface: https://community.fabric.microsoft.com/t5/General-Discussion/How-to-change-owner-of-a-Lakehouse/m-p/...