Configure authentication to Verkada

Important

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.

This page shows how to configure Verkada to enable authentication from Azure Databricks for the Verkada connector. Use the credentials retrieved from the steps on this page to create a Unity Catalog connection in Azure Databricks.

Prerequisites

• A Verkada Command organization with API access, and a Verkada organization admin who can create an API key.
• The region that hosts your Verkada organization: us, eu, au, or gov. An API key works only in the region its organization was created in, and the region cannot be changed. See Verkada: Service regions.

Configure Verkada

In this step, create a Verkada API key in Verkada Command and grant it the read permissions the connector requires. For more information, see Verkada: API key setup and authentication.

Grant the key Read-only access to the products that the tables you plan to ingest read from:

Permission	Grants access to
Core (Read-only)	The audit_log table.
Access Control (Read-only)	The users table.

To create the key:

1. Sign in to Verkada Command as an organization admin.
2. Go to Organization Settings > Verkada API.
3. Click + New API Key.
4. Enter a name for the key.
5. Set the permission scope to Read-only for Core and Access Control. GET endpoints require at least Read-only access, and API key permissions cannot be edited after the key is created.
6. Set the key expiration.
7. Click Generate Key, then copy the generated key. Store it securely — Verkada shows the key only once. Use this key to create a Unity Catalog connection in Azure Databricks.

The connector exchanges the API key for a short-lived API token automatically. Provide only the API key and region when you create the connection.

Next steps

Create a Verkada connection in Azure Databricks. See Create a Verkada connection.