Discover · databricks.com

No picture published by databricks.com

OAuth authentication for webhook destinations will soon be available by default for workspaces with the compliance security profile enabled

docs.databricks.com databricks.com

Starting on or after December 20, 2026, OAuth authentication for webhook destinations will be available by default for workspaces with the compliance security profile enabled, subject to the requirements for regions and compliance standards.

Use OAuth 2.0 client credentials to send notifications to an endpoint that requires an access token. Databricks obtains the token from the configured OAuth token endpoint and uses it to authenticate the notification request. Existing webhook destinations retain their configured authentication.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Names and references

  1. Security — person

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

More like this

Also from docs.databricks.com

  1. Genie Code analysis for alerts is in Betadatabricks.com
  2. Lakebase now supports Postgres 19databricks.com
  3. Gemini 3.6 Flash is retireddatabricks.com
  4. ai_forecast version 2 is now generally availabledatabricks.com
  5. Configurable retention for system tables is generally availabledatabricks.com
  6. Configure materialization TTLs for individual OpenSharing recipientsdatabricks.com