databricks Platform · Updated Aug 4, 2026

Schema-level HTTP connections in Unity Catalog are now generally available

HTTP connections in Unity Catalog are now generally available at the schema level.

Public Preview Open docs ↗release note ↗

What it does

HTTP connections in Unity Catalog are now generally available at the schema level. You can create an HTTP connection inside a schema instead of only at the metastore level. A schema level connection uses the three level namespace (catalog.schema.connection) and inherits Unity Catalog privileges from its parent schema, so you can apply the same access controls and auditing that you use for other data assets.

Why it matters

An HTTP connection is a Unity Catalog securable object that stores endpoint and credential information for an external HTTP service.

Key capabilities

Bearer token: Obtain a bearer

Bearer token: Obtain a bearer token for simple token-based authentication.

Dynamic Client Registration (DCR): Automatically

Dynamic Client Registration (DCR): Automatically discover and register OAuth credentials using the RFC 7591 protocol. Each user…

OAuth 2.0 Machine-to-Machine: Create and

OAuth 2.0 Machine-to-Machine: Create and configure an app to enable machine-to-machine authentication.

OAuth 2.0 User-to-Machine Shared: Authenticate

OAuth 2.0 User-to-Machine Shared: Authenticate with user interaction to share access between service identity and machine.

Architecture

Databricks Platform → Platform

In short

HTTP connections in Unity Catalog are now generally available at the schema level. You can create an HTTP connection inside a schema instead of only at the metastore level.

Read the full documentation ↗

Key takeaway

HTTP connections in Unity Catalog are now generally available at the schema level.

2026-08-04-schema-level-http-connections-in-unity-catalog-are-now-generally-available Generated by the Databricks Updates Agent · browse all updates