Is Databricks Azure down?

We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI. Symptoms • Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Recommendations No customer action is required at this time. Current Status We are actively investigating an incident on the cloud provider affecting Azure Databricks. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI. Symptoms • Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Recommendations No customer action is required at this time. Current Status We are actively investigating an incident on the cloud provider affecting Azure Databricks. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI. Symptoms • Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Recommendations No customer action is required at this time. Current Status We are actively investigating an incident on the cloud provider affecting Azure Databricks. For additional details, please check https://azure.status.microsoft/ Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI. Symptoms • Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Recommendations No customer action is required at this time. Current Status We are actively investigating an incident on the cloud provider affecting Azure Databricks. For additional details, please check https://azure.status.microsoft/ Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality due to an underlying network connectivity issue impacting the affected region. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI. Symptoms • Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Recommendations No customer action is required at this time. If feasible, customers with workloads that can be rerouted away from the affected region may see reduced impact until the network issue is resolved. Current Status We have identified the issue as a network-related disruption originating with our cloud provider affecting Azure Databricks, and we continue to work closely with the cloud provider to fully resolve it. For further details, please check https://azure.status.microsoft/ Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality due to an underlying network connectivity issue impacting the affected region. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI. Symptoms • Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Recommendations No customer action is required at this time. If feasible, customers with workloads that can be rerouted away from the affected region may see reduced impact until the network issue is resolved. Current Status We have identified the issue as a network-related disruption originating with our cloud provider affecting Azure Databricks, and we continue to work closely with the cloud provider to fully resolve it. For further details, please check https://azure.status.microsoft/ Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality due to an underlying network connectivity issue impacting the affected region. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI. Symptoms • Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Recommendations No customer action is required at this time. If feasible, customers with workloads that can be rerouted away from the affected region may see reduced impact until the network issue is resolved. Current Status We have identified the issue as a network-related disruption originating with our cloud provider affecting Azure Databricks, and the cloud provider has identified a potential cause and path to mitigation. For further details, please check https://azure.status.microsoft/ Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality due to an underlying network connectivity issue impacting the affected region. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI. Symptoms • Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Recommendations No customer action is required at this time. If feasible, customers with workloads that can be rerouted away from the affected region may see reduced impact until the network issue is resolved. Current Status We have identified the issue as a network-related disruption originating with our cloud provider affecting Azure Databricks, and the cloud provider has identified a potential cause and path to mitigation. For further details, please check https://azure.status.microsoft/ Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 14:51 UTC and 18:45 UTC on July 23, 2026, a subset of customers using Azure Databricks may have experienced errors or failures affecting services including Compute, Jobs, Notebooks, and Login, along with degraded availability across other affected services. Impacted users may have seen failures when starting compute resources, errors accessing notebooks or the workspace UI, issues submitting or running jobs, and intermittent login disruptions. Symptoms • Failures or errors when starting Classic, Serverless, or Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Current Status The cloud provider has mitigated the issue and services have been restored. (Refer to https://azure.status.microsoft/en-us/status) Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 14:51 UTC and 18:45 UTC on July 23, 2026, a subset of customers using Azure Databricks may have experienced errors or failures affecting services including Compute, Jobs, Notebooks, and Login, along with degraded availability across other affected services. Impacted users may have seen failures when starting compute resources, errors accessing notebooks or the workspace UI, issues submitting or running jobs, and intermittent login disruptions. Symptoms • Failures or errors when starting Classic, Serverless, or Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Current Status The cloud provider has mitigated the issue and services have been restored. (Refer to https://azure.status.microsoft/en-us/status) Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 14:51 UTC and 18:45 UTC on July 23, 2026, a subset of customers using Azure Databricks may have experienced errors or failures affecting services including Compute, Jobs, Notebooks, and Login, along with degraded availability across other affected services. Impacted users may have seen failures when starting compute resources, errors accessing notebooks or the workspace UI, issues submitting or running jobs, and intermittent login disruptions. Symptoms • Failures or errors when starting Classic, Serverless, or Dedicated Compute resources • 500 errors or failures loading the workspace UI and notebooks • Failures submitting or running Jobs, and intermittent login issues Current Status This incident has been resolved. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription

We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 09:03 UTC on July 16, 2026, a subset of customers using Azure Databricks may be experiencing errors, timeouts, or failures when using AI Gateway, Databricks Apps, Jobs, Model Serving, Notebooks, and Serverless Compute. Affected activities include making requests through AI Gateway, running app workflows, creating or terminating compute clusters, and authenticating to workspaces. Symptoms • Errors or timeouts when using AI Gateway, Databricks Apps, Model Serving, or Notebooks • Failures or delays creating or terminating Serverless Compute clusters • Authentication failures preventing access to workspaces Recommendations No customer action is required at this time. Current Status The root cause has been identified as a backend database connectivity issue, and the team is actively working to restore full service while continuing to assess the scope of impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 09:03 UTC on July 16, 2026, a subset of customers using Azure Databricks may be experiencing errors, timeouts, or failures when using AI Gateway, Databricks Apps, Jobs, Model Serving, Notebooks, and Serverless Compute. Affected activities include making requests through AI Gateway, running app workflows, creating or terminating compute clusters, and authenticating to workspaces. Symptoms • Errors or timeouts when using AI Gateway, Databricks Apps, Model Serving, or Notebooks • Failures or delays creating or terminating Serverless Compute clusters • Authentication failures preventing access to workspaces Recommendations No customer action is required at this time. Current Status The root cause has been identified as a backend database connectivity issue, and the team is actively working to restore full service while continuing to assess the scope of impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between approximately 09:03 UTC and 10:35 UTC on July 16, 2026, a subset of customers using Azure Databricks may have experienced errors, timeouts, or failures when using AI Gateway, Databricks Apps, Jobs, Model Serving, Notebooks, and Serverless Compute. Affected activities included making requests through AI Gateway, running app workflows, creating or terminating compute clusters, and authenticating to workspaces. Symptoms • Errors or timeouts when using AI Gateway, Databricks Apps, Model Serving, or Notebooks • Failures or delays creating or terminating Serverless Compute clusters • Authentication failures preventing access to workspaces Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between approximately 09:05 UTC and 10:35 UTC on July 16, 2026, a subset of customers using Azure Databricks may have experienced errors, timeouts, or failures when using AI Gateway, Databricks Apps, Jobs, Model Serving, Notebooks, and Serverless Compute. Affected activities included making requests through AI Gateway, running app workflows, creating or terminating compute clusters, and authenticating to workspaces. Symptoms • Errors or timeouts when using AI Gateway, Databricks Apps, Model Serving, or Notebooks • Failures or delays creating or terminating Serverless Compute clusters • Authentication failures preventing access to workspaces Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 09:03 UTC on July 16, 2026, a subset of customers using Azure Databricks may be experiencing errors, timeouts, or failures when using AI Gateway, Databricks Apps, Jobs, Model Serving, Notebooks, and Serverless Compute. Affected activities include making requests through AI Gateway, running app workflows, creating or terminating compute clusters, and authenticating to workspaces. Symptoms • Errors or timeouts when using AI Gateway, Databricks Apps, Model Serving, or Notebooks • Failures or delays creating or terminating Serverless Compute clusters • Authentication failures preventing access to workspaces Recommendations No customer action is required at this time. Current Status The team is actively working to restore full service while continuing to assess the scope of impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 09:03 UTC on July 16, 2026, a subset of customers using Azure Databricks may be experiencing errors, timeouts, or failures when using AI Gateway, Databricks Apps, Jobs, Model Serving, Notebooks, and Serverless Compute. Affected activities include making requests through AI Gateway, running app workflows, creating or terminating compute clusters, and authenticating to workspaces. Symptoms • Errors or timeouts when using AI Gateway, Databricks Apps, Model Serving, or Notebooks • Failures or delays creating or terminating Serverless Compute clusters • Authentication failures preventing access to workspaces Recommendations No customer action is required at this time. Current Status The team is actively working to restore full service while continuing to assess the scope of impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between approximately 09:03 UTC and 11:35 UTC on July 16, 2026, a subset of customers using Azure Databricks may have experienced errors, timeouts, or failures when using AI Gateway, Databricks Apps, Jobs, Model Serving, Notebooks, and Serverless Compute. Affected activities included making requests through AI Gateway, running app workflows, creating or terminating compute clusters, and authenticating to workspaces. While a partial recovery was observed around 10:35 UTC with a subset of requests, full recovery of all affected components was confirmed at 11:35 UTC Symptoms • Errors or timeouts when using AI Gateway, Databricks Apps, Model Serving, or Notebooks • Failures or delays in creating or terminating Serverless Compute clusters • Authentication failures preventing access to workspaces Current Status The issue has been mitigated, and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between approximately 09:03 UTC and 11:35 UTC on July 16, 2026, a subset of customers using Azure Databricks may have experienced errors, timeouts, or failures when using AI Gateway, Databricks Apps, Jobs, Model Serving, Notebooks, and Serverless Compute. Affected activities included making requests through AI Gateway, running app workflows, creating or terminating compute clusters, and authenticating to workspaces. While a partial recovery was observed around 10:35 UTC with a subset of requests, full recovery of all affected components was confirmed at 11:35 UTC Symptoms • Errors or timeouts when using AI Gateway, Databricks Apps, Model Serving, or Notebooks • Failures or delays in creating or terminating Serverless Compute clusters • Authentication failures preventing access to workspaces Current Status The issue has been mitigated, and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 09:03 UTC and 11:35 UTC on July 16, 2026, a subset of customers using Azure Databricks may have experienced errors, timeouts, or failures when using AI Gateway, Databricks Apps, Jobs, Model Serving, Notebooks, and Serverless Compute. Affected activities included authenticating to workspaces, running app workflows, and creating or provisioning compute resources. Some customers may also have experienced unavailability of Databricks Apps or delays in provisioning Serverless Compute resources during this period. Symptoms • Errors, timeouts, or failures when using AI Gateway, Databricks Apps, Model Serving, or Notebooks • Failures or delays in creating, terminating, or provisioning Serverless Compute clusters • Authentication failures preventing workspace access, and intermittent unavailability of Databricks Apps Current Status This incident has been resolved. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription

Between 23:04 UTC on July 15, 2026 and 00:07 UTC on July 16, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Unity Catalog, along with downstream impact to Jobs and Declarative Pipelines. The disruption resulted in intermittent failures or delays when accessing affected services during this window. Symptoms • Errors or failures when accessing Unity Catalog resources • Failures or delays when running Jobs • Failures or delays in Declarative Pipelines executions Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 2 hour, or sooner if there is a material change in service status.

Between 23:04 UTC on July 15, 2026 and 00:07 UTC on July 16, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Unity Catalog, along with downstream impact to Jobs and Declarative Pipelines. The disruption resulted in intermittent failures or delays when accessing affected services during this window. Symptoms • Errors or failures when accessing Unity Catalog resources • Failures or delays when running Jobs • Failures or delays in Declarative Pipelines executions Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 2 hour, or sooner if there is a material change in service status.

Between 23:04 UTC on July 15, 2026 and 00:07 UTC on July 16, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Unity Catalog, along with downstream impact to Jobs and Declarative Pipelines. This resulted in intermittent failures or delays when accessing affected services during this window. Symptoms • Errors or failures when accessing Unity Catalog resources • Failures or delays when running Jobs • Failures or delays in Declarative Pipelines executions Current Status This incident has been resolved. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription

We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 21:37 UTC on July 15, 2026, customers using Azure Databricks may be experiencing degraded availability or errors when accessing Unity Catalog. Symptoms • Failures or errors when accessing Unity Catalog • Delays or timeouts when performing catalog or metadata operations Recommendations No customer action is required at this time. Current Status The incident is currently under active investigation as engineering teams work to identify the root cause and restore full Unity Catalog availability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 21:37 UTC on July 15, 2026, customers using Azure Databricks may be experiencing degraded availability or errors when accessing Unity Catalog. Symptoms • Failures or errors when accessing Unity Catalog • Delays or timeouts when performing catalog or metadata operations Recommendations No customer action is required at this time. Current Status The incident is currently under active investigation as engineering teams work to identify the root cause and restore full Unity Catalog availability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 21:37 UTC on July 15, 2026, customers using Azure Databricks may be experiencing degraded availability or errors when accessing Unity Catalog, Jobs, and Declarative Pipelines. Symptoms • Failures or errors when accessing Unity Catalog • Delays or timeouts when performing catalog or metadata operations • Failures or delays when running Jobs or Declarative Pipelines Recommendations No customer action is required at this time. Current Status The root cause has been identified and mitigation actions have been taken; engineering teams are monitoring recovery and continuing to work toward full restoration of Unity Catalog, Jobs, and Declarative Pipelines availability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 21:37 UTC on July 15, 2026, customers using Azure Databricks may be experiencing degraded availability or errors when accessing Unity Catalog, Jobs, and Declarative Pipelines. Symptoms • Failures or errors when accessing Unity Catalog • Delays or timeouts when performing catalog or metadata operations • Failures or delays when running Jobs or Declarative Pipelines Recommendations No customer action is required at this time. Current Status The root cause has been identified and mitigation actions have been taken; engineering teams are monitoring recovery and continuing to work toward full restoration of Unity Catalog, Jobs, and Declarative Pipelines availability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

We detected an issue affecting the Databricks service for the listed component. The issue has been mitigated, and services are now operating normally. Next Update We are continuing to monitor the platform and will provide an update within the next hour.

We detected an issue affecting the Databricks service for the listed component. The issue has been mitigated, and services are now operating normally. Next Update We are continuing to monitor the platform and will provide an update within the next hour.

Between 21:37 UTC and 22:44 UTC on July 15, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors when accessing Unity Catalog, Jobs, and Declarative Pipelines. Impacted customers may have seen failures or timeouts performing catalog or metadata operations, as well as failures or delays running Jobs or Declarative Pipelines. Symptoms • Failures or errors when accessing Unity Catalog • Delays or timeouts when performing catalog or metadata operations • Failures or delays when running Jobs or Declarative Pipelines Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 21:37 UTC and 22:44 UTC on July 15, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors when accessing Unity Catalog, Jobs, and Declarative Pipelines. Impacted customers may have seen failures or timeouts performing catalog or metadata operations, as well as failures or delays running Jobs or Declarative Pipelines. Symptoms • Failures or errors when accessing Unity Catalog • Delays or timeouts when performing catalog or metadata operations • Failures or delays when running Jobs or Declarative Pipelines Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 21:37 UTC and 22:44 UTC on July 15, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors when accessing Unity Catalog, Jobs, and Declarative Pipelines. Impacted customers may have seen failures or timeouts performing catalog or metadata operations, as well as failures or delays running Jobs or Declarative Pipelines. Symptoms • Failures or errors when accessing Unity Catalog • Delays or timeouts when performing catalog or metadata operations • Failures or delays when running Jobs or Declarative Pipelines Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 21:37 UTC and 22:44 UTC on July 15, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors when accessing Unity Catalog, Jobs, and Declarative Pipelines. Impacted customers may have seen failures or timeouts performing catalog or metadata operations, as well as failures or delays running Jobs or Declarative Pipelines. Symptoms • Failures or errors when accessing Unity Catalog • Delays or timeouts when performing catalog or metadata operations • Failures or delays when running Jobs or Declarative Pipelines Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 21:37 UTC and 22:44 UTC on July 15, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors when accessing Unity Catalog, Jobs, and Declarative Pipelines. Impacted customers may have seen failures or timeouts when performing catalog or metadata operations, as well as failures or delays when running Jobs or Declarative Pipelines. Symptoms • Experienced failures or errors when accessing Unity Catalog • Experienced delays or timeouts when performing catalog or metadata operations • Experienced failures or delays when running Jobs or Declarative Pipelines Current Status This incident has been resolved. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription

Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic Compute and Jobs, with customers encountering errors related to cluster startup or configuration, and some workspace console pages failing to load. The issue has since been mitigated and normal service has been restored. Symptoms • Clusters failed to start or experienced significant startup delays • Jobs failed to launch or were delayed • Errors related to cluster configuration or startup, and some workspace console pages failed to load Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic Compute and Jobs, with customers encountering errors related to cluster startup or configuration, and some workspace console pages failing to load. The issue has since been mitigated and normal service has been restored. Symptoms • Clusters failed to start or experienced significant startup delays • Jobs failed to launch or were delayed • Errors related to cluster configuration or startup, and some workspace console pages failed to load Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic Compute and Jobs, with customers encountering errors related to cluster startup or configuration, and some workspace console pages failing to load. The issue was resolved and normal service was restored by the end of the impact window. Symptoms • Clusters failed to start or experienced significant startup delays • Jobs failed to launch or were delayed • Some workspace console pages failed to load, showing errors related to cluster configuration or startup Current Status This incident has been resolved. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription