Forum Discussion
SQL-Endpoint not working anymore
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.
Hey Anonymous ,
Neither the Warehouse or Warehouse has been renamed. I double checked the linked DevOps git repo if it ever has been renamed just to be sure (because the folder will have the original name) but that is not the case.
I can basically reproduce this issue with any lakehouse or warehouse in one of the tenants i have access to. Unfortunately the issue still did not resolve. I've tested with another user in the tenant and that user is also experiencing the same issue on all SQL Endpoints.
I've tried updating the lakehouse and warehouse connections (tho it shouldnt matter) with ne Oatuh Tokens in the Connection Settings too but that didnt do anything as expected.
Im trying to restart the capacity right now if that fixes the issue but that somehow made it worse. Stuck pausing. Cant restart.
Help would be appreciated, thanks!
EDIT: Capacity did finally pause after ~15mins and has been restarted but the issue did not resolve.
Tim
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.
Hi Timal ,
Thank you for your reply, I am very glad you found the problem. Can I ask if your problem is solved at the moment, please feel free to ask me any questions you may have. If the problem has been resolved, I suggest you could mark your reply as a solution, it looks like it could help more people experiencing similar problems!
Best Regards,
Ada Wang