@-werners- wrote:

That is strange,  I think something went wrong in the deployment of the Databricks environment.
We have 3 databricks workspaces and do not see such behavior.
Any resource deployed on a subscription owned by you is accessible by some kind of admin.  There should not be any locked down resource.


https://stackoverflow.com/questions/73064767/how-to-override-deny-assignment-so-that-i-can-access-th...

You can't do this on the managed resource group created by Azure Databricks even if you're owner - it's a resource managed by Databricks

@Alberto_Umana 

thanks