Forum Discussion
SQL-Endpoint not working anymore
- 2 years ago
I've found the issue. The user who created the Warehouses/Lakehouses has been deactivated.
Du to the Warehouses using delegate Permissions from the Owner for other users to access the Data, the User cannot be removed from the Workspace or Access will break.
According to the following Guide PowerShell can be used to change Ownership.
Change ownership of Fabric Warehouse - Microsoft Fabric | Microsoft Learn
However so far this only worked with Warehouses and NOT Lakehouses for me.
Hope this helps! ... and i find out how to fix the Lakehouses
EDIT:
Microsoft confirmed that the Owner of Lakehouses currently can only be changed by them. So you'll have to open a Ticket. They plan to allow the end user to change that in the future.
I don't understand why the Access to the Warehouses is not managed via Service Principal (like other Services) instead of User Delegation but it is what it is.
Since you're admin you could try adding the owner to the workspace as Contributor or Higher and see it it resolves the issue. It's not a 100% shot but since technically the Owner does't have Permissions on the Lakehouse it could cause the issue i suppose.
If it works when re-adding it then you either have to keep it like that (if thats possible) or change the owner, yeah.
You could check if there may be a way for us to change Owners ourselves now since it's been a while since my issue, otherwise you'd have to create a Ticket like i had to then.
Heya,
So I added the owner back to the workspace. Got them to go into the SQL enpoint & refresh the warehouse. This has solved the issue! While less than ideal, i will be taking this as a temporary solution and changing the owner further down the line!
Thanks for your support 🙂
L