Share via

Change ownership of datalake/lakehouse

Kevin Ha 0 Reputation points
2025-11-27T16:18:35.4266667+00:00

Hello All,

We need help in changing the ownership of our datalake/lakehouse as the original user who created this has left the company.

We have already taken ownership of all the pipelines, artifacts, schedules and connections. However, when we disable the original user account, we start getting the following refresh errors.

Semantic model refresh execution failed, error message received from semantic model refresh operation - '{"errorCode":"ModelRefresh_ShortMessage_ProcessingError","errorDescription":"Retry attempts for failures while executing the refresh exceeded the retry limit set on the request.\n0x414700EF: {"RootActivityId":"E1EE5F96-2B48-492A-8736-1D51C3786C26"}\n0xC1450012: {"error":{"code":"DMTS_OAuthTokenRefreshFailedError","pbi.error":{"code":"DMTS_OAuthTokenRefreshFailedError","details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"AADSTS50057: The user account is disabled. Trace ID: 14342184-1bc1-4b0e-b166-b89bac3ba300 Correlation ID: e01e009b-0640-4c97-aae1-b0b025cdc583 Timestamp: 2025-11-26 16:01:27Z The returned error contains a claims challenge. For additional info on how to handle claims related to multifactor authentication, Conditional Access, and incremental consent, see https://aka.ms/msal-conditional-access-claims. If you are using the On-Behalf-Of flow, see https://aka.ms/msal-conditional-access-claims-obo for details."}}],"exceptionCulprit":1}}} Table: BI RJWOrdersMatched. Partition: BI RJWOrdersMatched.\n0xC14700F0: {"RootActivityId":"E1EE5F96-2B48-492A-8736-1D51C3786C26"}"}'

We have double and triple checked that we've moved ownership to a different account and can see that the refresh job gets executed by the new account. However, it is still referencing the old user account.

I believe, I read somewhere on the Fabric forums that we may need to migrate the ownership of the datalake/lakehouse away from the original user.

If anyone has any insight into this, that would be great.

Thanks,

Azure Service Fabric
Azure Service Fabric
An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-11-27T16:19:44.9533333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To change the ownership of a datalake or lakehouse in Azure, you need to ensure that all relevant permissions and configurations are updated after transferring ownership. Here are some steps to consider:

    1. Transfer Ownership: Ensure that the ownership of the datalake/lakehouse has been transferred to the new user account. This includes verifying that the new account has the necessary permissions to access and manage the datalake/lakehouse.
    2. Update Data Source Access: After transferring ownership, make sure that the new owner has access to the original data sources associated with the datalake/lakehouse. This is crucial to avoid refresh errors related to access issues.
    3. Check Incremental Refresh Settings: If you are using incremental refresh settings, these may need to be reset after the ownership transfer. Ensure that these settings are configured correctly for the new owner.
    4. Disable the Original User Account: When you disable the original user account, ensure that no processes or jobs are still referencing this account. If the refresh jobs are still attempting to run under the old account, it could lead to errors like the one you are experiencing.
    5. Refresh the Semantic Model: After making the ownership changes, try refreshing the semantic model to ensure that it is updated with the new configurations. If you continue to face issues, check the error logs for any specific details that might indicate what is still referencing the old account.
    6. Review Documentation: If issues persist, consider reviewing the relevant documentation or forums for additional insights on ownership migration and refresh errors specific to Azure Data Lake Storage.

    By following these steps, you should be able to resolve the refresh errors and ensure that the new account is fully operational with the datalake/lakehouse.

    0 comments
  2. Jaishree Taware 0 Reputation points
    2025-12-04T16:25:58.96+00:00
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.