Share via

Manage permissions

Important

This feature is in Public Preview in the following regions: westus, westus2, eastus, eastus2, centralus, southcentralus, northeurope, westeurope, australiaeast, brazilsouth, canadacentral, centralindia, southeastasia, uksouth.

This page describes when and how to grant Azure Databricks users and identities permissions to a database instance.

To allow other users to use PostgreSQL to access the database instance, the databricks_superuser must create corresponding Postgres roles for them. For details on how to create Postgres roles, see Manage Postgres roles.

When and how permissions are checked

When you use Postgres syntax or connect through a PostgreSQL interface, Lakebase enforces PostgreSQL-specific access controls by using the following:

  • Postgres roles
  • Role memberships
  • Postgres-granted permissions

In all other scenarios, Lakebase enforces Databricks-specific access controls:

  • Azure Databricks identities (users, groups and service principals)
  • Azure Databricks group memberships
  • Workspace access control lists (ACLs)
  • Unity Catalog privileges

Note

There is no automatic sync between Azure Databricks identities and memberships, and Postgres roles and memberships.

Use case / Permission or identity Manage database instances Create or delete synced tables Manage synced table pipeline Query Postgres tables from a SQL warehouse Query online features in feature and model serving Query Postgres tables in PostgreSQL
Azure Databricks identities ✅ ✅ ✅ ✅ ✅ Requires a corresponding Postgres role
Databricks group memberships ✅ ✅ ✅ ✅ ✅ Only checked on login when logging in as a group
Instance ACLs ✅ ✅
Pipeline ACLs Need to be a pipeline owner when reusing an existing pipeline or deleting a synced table (which edits the pipeline) ✅
UC permissions ✅ ✅ ✅
Postgres roles ✅
Postgres role memberships ✅
Postgres permissions ✅

Grant instance permissions to Azure Databricks identities

A user must have specific permissions on the database instance to manage the instance and perform table operations. Workspace admins and the instance creator can assign additional permissions to any desired users, groups, or service principals in the Database instances overview page.

  1. Click Compute in the workspace sidebar.
  2. Click OLTP Database.
  3. Click the Permissions tab.
  4. Click Manage instance permissions in the upper-right.
  5. Enter a user, group, or service principal to grant additional permissions to.
  6. Select the permission you want to grant to the identity. See Database instance ACLs.
  7. Click + Add.
  8. Any workspace user can view or list database instances. Database catalog and synced table permissions are further governed by Unity Catalog metastore, catalog, schema, and table permissions. For more details, see Manage privileges in Unity Catalog.
  9. Click Save.
  • Last updated on