How to change owner of a Lakehouse?

[Anonymous]

Hello, i am currently struglling with the following situation. 

Within the team, we created a lakehouse solution consisting of tables, shortcuts to folders with parquet files, views, notebooks ,sql queries and Power BI Reports based on the lakehouse. 

The owner of the lakehouse is a colleague whose account was disabled and we are not able to run the sql queries or the reports anymore, the shortcuts connections are not working as well. 

We tried to find a way to change the ownership of the lakehouse but without luck. Anyone has any idea on how to fix the lakehouse without recreating it again from scratch? 

Thanks in advance for your answers!

[CMcDonald]

@Anonymous  I'm having the same issue as well. Will there be a solution to this issue? It seems to be a common action needed for all accounts to be able to change the ownership if a user's account is disabled.

[Anonymous]

Hi @CMcDonald 
Please create a support ticket. https://support.fabric.microsoft.com/en-US/support/
The support team can help you better in addressing this issue.
Thanks.

[wedmisto]

Hello, I am trying to put in a ticket. However, I am having a issue where it is perpetually loading. (15min)

[rcalebeek]

Same issue here
collegue was the power Bi guy and shared a lot of Power Bi dashboard in our organisation
Collegue left the company, user account disabled in AAD 
end of story, we cannot refresh our dashboard

how do we migrate the ownership from the left collegue to me ( the new Power BI GURU 😉 )

[Anonymous]

Hi @Anonymous 
Thanks for using Fabric Community.
Why did the Fabric account get disabled? Before the account got disabled did you get a chance to give the Lakehouse permission to any other user? If yes then you can access the SQL endpoint and also the shortcuts from the other account.
You can refer to these links:
Lakehouse sharing and permission management - Microsoft Fabric | Microsoft Learn
Workspace roles and permissions in lakehouse - Microsoft Fabric | Microsoft Learn

If you have not given permissions for other user and the account with the Lakehouse is now disabled, then we cannot access it anymore.
Hope this helps. Please let me know if you have any further queries.

[Anonymous]

Hello, the account get disabled because the person left the project.

I have already admin rights on the lakehouse but still i cannot run the queries, open the shortcuts or open the reports based on the lakehouse.

Thank you 

[Anonymous]

Hi @CMcDonald , @Anonymous , @rcalebeek 
Apologies for the issue you have been facing. Currently there is no solution for this issue. The possible workaround is to have someone else take ownership of the workspace prior the account gets disabled.
Eventhough the access is given to another person and still you are not able to access the artifacts then, I would suggest you to please go ahead with Microsoft support on this. 
https://support.fabric.microsoft.com/en-US/support/

Thanks.

[Padam06]

You need to get support from Microsoft to change the ownership of the lakehouse. Once it is changed, you have to run below power shell scirpt to change the SQL endpoint owner to Lakehouse owner.

# 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
$workspaceid = "xxx"
$sqlendpoint = "xxx"
Connect-PowerBIServiceAccount
$url = 'groups/' + $workspaceid + '/lhdatamarts/' + $sqlendpoint + '/takeover'
write-host $url
Invoke-PowerBIRestMethod -Url $url -Method Post -Body ""-Verbose

[nomadica]

I got the ugly error today on my lakehouse SQL EndPoint, and support says the only way to change owner of a lakehouse is from their end. The problem is I have tens of lakehouses, and they need the ID of each to do the change. While this API call is helpful: Items - List Lakehouses - REST API (Lakehouse) | Microsoft Learn,

it doesn't show me the current owner, so I will end up doing manual work to identify which ones are owned by the departed user.

While we bear the responsibility of used a named account (vs a service account) to create lakehouses, this is one really impacted our productivity as we had a sudden block that we need to escalate to support to fix.

FYI, SQL endpoint error is: Encountered Operating Sysetme Error 5/ (Access is denied) while attempted to read physical metadata.

[photographica]

I have the same problem. I'm the Lakehouse admin, but I can't access the data because the owner was removed from Active Directory. I tried to assign the role from SSMS using an SQL connection string, but it didn't work either

[evrise]

ooouch. this is still not re-designed ? really awfull concept. 

but, wait when you will want to automate something and overwirte this items via CI/CD 😄 😄  thats also " very funny 🙂 "

[evrise]

OK, @Anonymous I have all AAD accounts active and available. 

How to transfer an ownership from one to another ?  Thanks 🙂 

[Anonymous]

thank you for the response, i am already admin on the workspace where the lakehouse was created, i don't get why i cannot use the lakehouse anymore if i have all the rights, Adela