Platform release process
In order to minimize disruption to Azure Databricks users, releases are deployed on a regular cadence. During a deployment, Azure Databricks services may be temporarily disrupted.
Release deployments are scheduled outside of normal business hours for the region in which they occur.
Notification types
There are multiple types of notifications that appear before a deployment starts, depending on your deployment model.
The following sections highlight the most common methods.
Status Page
The Azure Databricks Status Page is updated to indicate which regions a deployment impacts. When a deployment ends, the Status Page is updated to show normal operation. See Status Page.
Status Page automatic notification
If you subscribe to automatic notifications, Azure Databricks sends an alert before a deployment begins, and a second alert when the deployment has concluded. To learn how to configure your notification subscription, see Subscribe.
Example email notification
The following is an example email notification that is sent to subscribers when a scheduled deployment begins.
Title: Maintenance Notification from Azure Databricks
Affected Infrastructure
Components: Authentication, Compute Service, Jobs Service, ODBC/JDBC Service, User Interface,API Service
Locations: us: eastus: East US
Update:
Databricks has initiated scheduled maintenance in the listed regions. Review the release notes for more information on recent platform updates. An additional notification will be sent when maintenance is completed.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for