Is there a way that admins can restrict users to install libraries on clusters and notebooks?

[-werners-]

you can assign permissions to (existing) clusters.

There are 4 kinds of permissions:

• no permission (says enough I think)
• Can Attach To: attach a notebook (and display logs)
• Can Restart: same as above with stop/start/restart
• Can Manage: same as Restart but with cluster resize and library install

So basically if you assign Attach or Restart permissions, the user is not allowed to install libraries.

That is only allowed with the Manage permission.

https://docs.microsoft.com/en-us/azure/databricks/security/access-control/cluster-acl#cluster-level-...

[morganmazouchi · Accepted solution]

I found the answer to my question for how to restrict library installation both on clusters and notebooks and posting it here for others reference: we can restrict outbound access to the public pypi at the workspace level using these instructions https://docs.databricks.com/administration-guide/cloud-configurations/aws/customer-managed-vpc.html#...

[Chris_Shehu]

With it being restricted at the cluster level as well how are you installing libraries that need to be added adhoc? Did you block the entire pypi domain?

[morganmazouchi]

Admin can set up a connection to Azure Artifactory/Jfrog Artifactory or other artifactories of required libraries for the workloads.

[Anonymous]

@Mojgan Mazouchi​ - I'm so glad you found the answer and shared it with us. Thank you!

[Sebastian]

one way to manage is make the cluster permission only to can restart and then use an init script to install libraries on start up so that users wont install libraries on the fly.