DataBricks best practice to manage resource correspond deleted user

[Trung]

currently I have some prblem about my DataBricks workspace when an user was deleted and it cause some issue:

1. Applications or scripts that use the tokens generated by the user will no longer be able to access the Databricks API
2. Jobs owned by the user will fail
3. Clusters owned by the user will stop
4. Queries or dashboards created by the user and shared using the Run as Owner credential will have to be assigned to

How can I keep these resources operate normally?

[Vivian_Wilfred · Accepted solution]

Hi @trung nguyen​ All of the above are consequences of a user getting deleted. This cannot be avoided and it is expected. Before deleting the user, transfer ownership, clone the clusters, clone the jobs, and make necessary changes to keep the resources prepared for user/owner deletion.

https://docs.databricks.com/workflows/jobs/jobs.html#clone-a-job

https://docs.databricks.com/clusters/clusters-manage.html#clone-a-cluster

https://docs.databricks.com/sql/user/security/access-control/query-acl.html

You could also create a service account for managing important resources instead of using a user account.

Let me know if this helps. Please mark this comment as "best answer" to resolve the query.

[Trung]

@Vivian Wilfred​ it really useful for my case, many thanks!