Either make the workspace the owner of a lakehouse or give admin tools to overtake ownership

[Thomas_Schlidt]

Data Warehouses and Data Lake House are tied to the user account of their creator.

Which means, when the creator leaves an organization and the account is disabled/deleted, the lakehouse and data warehouse stop functioning.

This is not sustainable for enterprise organizations that may attempt to build solutions off lakehouses and data warehouses.

Either associate the lakehouse and warehouse ownership with the workspace (which means the workspace will need an identity for permission setting at the data lake) or allow administrators to reassign ownership of the lakehouse and data warehouse.

Currently there is a powershell script for data warehouse, there isn't for lakehouse. Which means that the lakehouse rebuilt and downsteam artifacts need to be modified.

[fbcideas_migusr]

This is a critical issue!

[Will_Trickett2]

This absolutely needs to be addressed. Lakehouse can't be adopted at an enterprise level until this is resolved.

[BEN_ROACHE]

bizarre that this is an issue.