Hi @shweta_m,

I don't think this is exactly what you're asking, which seems to be some kind of configuration at the account management console level, but I don't know of a way to do what you're proposing.

In my case, we had a similar problem with my organisation. We opted to migrate the implementation of jobs/pipelines through Databricks Asset Bundles, and the Azure EntraID integration provides us directly with the user groups we have in Azure.

Therefore, when developing and deploying in different environments (including dev), we choose the permissions that each group has in the targets section of databricks.yml, so that only selected people can see the jobs/pipelines and with different permissions to view, execute, edit, or manage.

In our case we so differents job cluster configuration so we decide to declare the compute over each job declaration yml.

Now, nobody can run or even see anything they shouldn't.

I attached you some resources:
https://learn.microsoft.com/en-us/azure/databricks/dev-tools/bundles/permissions
https://learn.microsoft.com/en-us/azure/databricks/dev-tools/bundles/settings