Problem with Lakehouse SQL Endpoint permission after employee leaving

[Badalabandalad]

Hi,

In our company, we started using a fabric in preview. One employee created all data, scripts, pipelines,lakehouse on company workspace. At the end of November, he left the job. He gave us (another IT persons) admin access to this workspace. Yesterday his MS Account was delated, and the SQL Endpoint crashed 😞 Do you have the same idea how to repair that? To Lakehouse we have a permission, problem is only with SQL Endpoint.

[Anonymous]

Hi @Badalabandalad ,

Thanks for using Fabric Community.

At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.

[Anonymous]

Hi @Badalabandalad ,

Apologies for the delay in response.

Internal Team felt this might require a deeper investigation from our engineering team about your workspace and the logic behind it to properly understand what might be happening. 

Please go ahead and raise a support ticket to reach our support team: support-ticket and also attach the details of the error you are receiving when you access SQL Analytics endpoint.
Please provide the ticket number here as we can keep an eye on it.

Thank you.

[Anonymous]

Hi @Badalabandalad ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond back with the more details and we will try to help .

[Anonymous]

Hi @Badalabandalad ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond back with the more details and we will try to help .

[AndrzejKro]

The response from MS Support is:
"Currently there is no way in Fabric to assign ownership of a Lakehouse artifact."

This greatly complicates the usability of this solution.

[DennesTorres]

Hi,

I don't have the exact answer, but I think I may add my two cents to the problem:

The objects created in Fabric are set with the owner as the user who created them. And my experience with Notebooks is that it's not possible to change ownership. On the notebooks scenario, in order to change the owner, I had to export the notebooks, delete and import again.

On your scenario with the SQL Endpoint, I don't have any idea. Maybe you will end up in need of a support ticket.

Kind Regards,

Dennes