Manage notification destinations

This page teaches you how to create and configure notification destinations for your workspace.

System notifications are messages that tell you when your workflow experiences a run event (start, success, and failure). By default, notifications are sent to user email addresses, but admins can configure alternate notification destinations using webhooks. This allows you to build event-driven integrations with Azure Databricks.

Admins can also configure notification destinations to receive access requests from workspace users, such as privilege requests on Unity Catalog objects.

You must be an Azure Databricks workspace admin to manage notification destinations. After a destination is configured, it is available to all users.

Networking requirements

For webhook-based destinations, the receiving endpoint must meet the following requirements:

  • Azure Databricks enforces the use of HTTPS for security. The notification destination must use Secure Sockets Layer (SSL) certificates signed by a trusted certificate authority.

  • The notification destination must add both the workspace control plane and data plane outbound IP addresses to its allowlist:

    • For control plane webapp IP addresses, see IP addresses and domains for Azure Databricks services and assets.

    • For data plane outbound IP addresses, see the ip-ranges.json file that Azure Databricks publishes. Search the file for your workspace's data plane region and allowlist the corresponding outbound IP addresses in your networking stack.

      Azure Databricks may update the outbound IPs as often as once every 30 days. Updated IPs become active as soon as 60 days after publication, so review the file regularly and update your allowlist before the activation window closes.

      To track changes between releases, save successive versions of the JSON file and compare the timestampSeconds value. Filter entries where:

      • The service field is Databricks

      • The platform field is azure

      • The type field is outbound

Create a new notification destination

To configure a new notification destination

  1. Click your username in the top bar of the workspace and select Settings from the dropdown.

  2. In the Workspace admin section, click the Notifications tab.

  3. Click the Manage button.

  4. Click +Add destination.

  5. Select a destination type. The following destinations are currently supported:

    • Email
    • Microsoft Teams

    • PagerDuty

  6. Configure the destination based on the type.

  7. Click Create.

Use different credentials for each destination

The configuration of a destination is securely stored encrypted in your Azure Databricks workspace. For destinations that require you to provide a URL or credentials, Azure Databricks recommends using different credentials for each configured destination. This limits the impact if a third-party endpoint is compromised. These include:

  • Microsoft Teams using a webhook: the URL to which the notification is sent.

  • PagerDuty: integration key used to uniquely route notifications to a PagerDuty service.

  • Webhook: a username and password for HTTP Basic authentication, or a client ID and client secret for OAuth authentication (Beta).

Using different secrets for each configured destination allows you to individually revoke access of individual notification destinations without impacting the operation of all other destinations in your Azure Databricks workspace.

PagerDuty destination

To set up a PagerDuty destination:

  1. In PagerDuty, add an integration to your service and select the Events API V2 integration type.

  2. Copy the integration key that PagerDuty generates for the integration.

  3. In Azure Databricks, paste the integration key into the PagerDuty notification destination.

Add a webhook to a job

After configuring destinations, you can access them in a job's Job notifications settings. For more information, see Add notifications on a job.

Each job supports up to three system destinations per event type. When configuring job notifications, email addresses must be entered manually.

Limitations

Notification destinations currently has the following limitations:

  • Email notification destinations have a 1,300-character limit on the recipient address length.

  • For custom notification bodies, non-email destinations such as Microsoft Teams do not support HTML formatting. Some notification destinations support markdown.

  • For jobs, email destinations must be manually set in the job's settings.