Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Automatic cluster update ensures that all classic compute resources in a workspace are periodically updated to the latest host OS image and security updates. This update applies to all compute resources that run in the classic compute plane: classic all-purpose and jobs compute, pools, classic SQL warehouses, and legacy Model Serving. It does not apply to serverless compute resources.
By default, compute resources are only restarted when an image update is available. You can configure the feature to force a restart during every maintenance window instead. See Configure automatic cluster update.
Enabling this feature on a workspace automatically adds the Enhanced Security and Compliance add-on, as described on the pricing page, and requires the Premium pricing tier.
Who can configure automatic cluster update
You must be an account admin to configure automatic cluster update. Although the setting applies to each workspace individually, you configure it from the Azure Databricks account console, not the workspace admin console.
If the compliance security profile is enabled in your account, automatic cluster update is enabled by default in all of your workspaces. Account admins can still adjust the maintenance window and restart behavior from the account console.
Enable automatic cluster update on a workspace
To enable automatic cluster update on a workspace, see Use the Azure portal. Enabling the compliance security profile also enables automatic cluster update.
Configure automatic cluster update
By default, automatic cluster update is scheduled for the first Sunday of every month at 1:00 AM UTC. Account admins can change the maintenance window frequency, start date, and start time from the account console:
- Go to the Azure Databricks account console.
- In the sidebar, click Workspaces.
- Click the name of your workspace.
- Click Security and compliance.
- Next to Automatic cluster update, click the Configure button.
- Set the maintenance frequency.
- For monthly schedules, choose which numbered week, such as 1st or 3rd.
- For twice-monthly schedules, choose 1st and 3rd or 2nd and 4th.
- Set the day and time for your maintenance window.
- By default, compute resources only restart if updates are available. To force clusters and other compute resources to restart during this maintenance window regardless of the availability of a new update, select Always restart.
- Click Save.
Note
Updates may take up to 6 hours to propagate across all environments and downstream systems like billing. Workloads that are actively running continue with the settings that were active when the compute resource started, and new settings apply the next time the workload starts. If you make a change late in the day or on the last day of the month, you might still see usage reported with the old settings early the next day or month. To apply the latest updates immediately, restart the compute resource.