Hi,
some of our folks are using Databricks in Azure. The deployment of this service is extremely bad as it is creating a second locked resource group.
Even we as subscription and tenant admins cant delete this read-only lock? Is there really ANY reason why this is prohibited? A simple application shouldn't be able to lock itself down in a way even the tenant admin cannot undo this.
This resource-locking-thing breaks down ALL policies we carefully deployed, including resource owner tags we use to divide the occuring costs.
Did I miss something or is there really no solution to this?
Best regards,
Hendrik