Databricks Azure Outage History

Started Aug 12, 2026, 06:11 PM UTC· resolved Aug 12, 2026, 07:44 PM UTC

1. investigating Aug 12, 2026, 06:11 PM UTC

   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.

2. investigating Aug 12, 2026, 06:11 PM UTC

   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.

3. investigating Aug 12, 2026, 06:21 PM UTC

   Starting at approximately 17:56 UTC on August 12, 2026, customers using Azure Databricks may be experiencing failures or terminations of Serverless Compute workloads, along with degraded availability. Symptoms • Serverless Compute clusters terminating unexpectedly • Errors when starting or running Serverless Compute workloads • Degraded availability of Serverless Compute Recommendations No customer action is required at this time. Current Status Databricks engineering teams are actively investigating a Sev1 incident impacting Serverless Compute availability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating Aug 12, 2026, 06:21 PM UTC

   Starting at approximately 17:56 UTC on August 12, 2026, customers using Azure Databricks may be experiencing failures or terminations of Serverless Compute workloads, along with degraded availability. Symptoms • Serverless Compute clusters terminating unexpectedly • Errors when starting or running Serverless Compute workloads • Degraded availability of Serverless Compute Recommendations No customer action is required at this time. Current Status Databricks engineering teams are actively investigating a Sev1 incident impacting Serverless Compute availability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring Aug 12, 2026, 06:42 PM UTC

   Between 17:56 UTC and 18:20 UTC on August 12, 2026, a subset of customers using Azure Databricks may have experienced failures or terminations of Serverless Compute workloads along with degraded availability. This disruption also affected related Jobs and Pipelines services during the same window. Symptoms • Serverless Compute clusters terminated unexpectedly • Errors occurred when starting or running Serverless Compute workloads • Jobs and Pipelines experienced degraded availability 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.

6. monitoring Aug 12, 2026, 06:42 PM UTC

   Between 17:56 UTC and 18:20 UTC on August 12, 2026, a subset of customers using Azure Databricks may have experienced failures or terminations of Serverless Compute workloads along with degraded availability. This disruption also affected related Jobs and Pipelines services during the same window. Symptoms • Serverless Compute clusters terminated unexpectedly • Errors occurred when starting or running Serverless Compute workloads • Jobs and Pipelines experienced degraded availability 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.

7. resolved Aug 12, 2026, 07:44 PM UTC

   Between 17:56 UTC and 18:20 UTC on August 12, 2026, a subset of customers using Azure Databricks may have experienced failures or terminations of Serverless Compute workloads, along with degraded availability. This disruption also affected related Jobs and Pipelines services during the same window. Symptoms • Serverless Compute clusters terminated unexpectedly • Errors occurred when starting or running Serverless Compute workloads • Jobs and Pipelines experienced degraded availability 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

Read the full incident report →

Started Aug 10, 2026, 04:33 AM UTC· resolved Aug 10, 2026, 06:41 AM UTC

1. monitoring Aug 10, 2026, 04:33 AM UTC

   Between 3:54 and 4:10 UTC on August 10, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Databricks SQL, Jobs, and Notebooks. The disruption was brief, lasting approximately 16 minutes, before normal service was restored. Symptoms • Errors or failures when running Databricks SQL queries • Delays or failures when executing Jobs • Notebooks may not have loaded or executed as expected 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.

2. monitoring Aug 10, 2026, 04:33 AM UTC

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

3. resolved Aug 10, 2026, 06:41 AM UTC

   Between 3:54 and 4:10 UTC on August 10, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Databricks SQL, Jobs, and Notebooks. The disruption lasted approximately 16 minutes before impact subsided. Symptoms • Errors or failures when running Databricks SQL queries • Delays or failures when executing Jobs • Notebooks may not have loaded or executed as expected Current Status This incident has been resolved. We apologise 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

Read the full incident report →

Started Aug 09, 2026, 03:23 AM UTC· resolved Aug 09, 2026, 05:16 AM UTC

1. investigating Aug 09, 2026, 03:23 AM UTC

   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.

2. investigating Aug 09, 2026, 03:23 AM UTC

   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.

3. monitoring Aug 09, 2026, 04:17 AM UTC

   Between 02:35 UTC and 03:35 UTC on August 9, 2026, a subset of customers using Azure Databricks may have experienced failures or errors with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected workloads may have seen unresponsive clusters, cluster connectivity issues, or failures when starting or running jobs and pipelines. Symptoms • Clusters became unresponsive or failed to launch • Jobs and pipelines failed due to lost cluster communication • Errors occurred when connecting to Databricks SQL endpoints or compute resources 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.

4. monitoring Aug 09, 2026, 04:17 AM UTC

   Between 02:35 UTC and 03:35 UTC on August 9, 2026, a subset of customers using Azure Databricks may have experienced failures or errors with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected workloads may have seen unresponsive clusters, cluster connectivity issues, or failures when starting or running jobs and pipelines. Symptoms • Clusters became unresponsive or failed to launch • Jobs and pipelines failed due to lost cluster communication • Errors occurred when connecting to Databricks SQL endpoints or compute resources 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.

5. resolved Aug 09, 2026, 05:16 AM UTC

   Between 02:35 UTC and 03:35 UTC on August 9, 2026, a subset of customers using Azure Databricks may have experienced failures or errors with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected workloads may have seen unresponsive clusters, cluster connectivity issues, or failures when starting or running jobs and pipelines. Symptoms • Clusters became unresponsive or failed to launch • Jobs and pipelines failed due to lost cluster communication • Errors occurred when connecting to Databricks SQL endpoints or compute resources 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

Read the full incident report →

Started Aug 05, 2026, 06:38 AM UTC· resolved Aug 05, 2026, 09:36 AM UTC

1. investigating Aug 05, 2026, 06:38 AM UTC

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

2. investigating Aug 05, 2026, 06:38 AM UTC

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

3. investigating Aug 05, 2026, 07:20 AM UTC

   Starting at approximately 04:23 UTC on August 5, 2026, customers using Azure Databricks may be experiencing failures or delayed startup of Serverless Compute workloads, along with degraded availability or errors affecting Databricks SQL queries and Jobs. Symptoms • Serverless Compute clusters failing to start or terminating unexpectedly • Errors indicating the compute driver is unreachable • Databricks SQL queries and Jobs may fail, be delayed, or run degraded Recommendations No customer action is required at this time. Current Status The team is actively investigating Serverless Compute, Databricks SQL, and Jobs disruptions related to driver unreachable errors and cluster terminations; a probable root cause has been identified but not yet confirmed. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating Aug 05, 2026, 07:20 AM UTC

   Starting at approximately 04:23 UTC on August 5, 2026, customers using Azure Databricks may be experiencing failures or delayed startup of Serverless Compute workloads, along with degraded availability or errors affecting Databricks SQL queries and Jobs. Symptoms • Serverless Compute clusters failing to start or terminating unexpectedly • Errors indicating the compute driver is unreachable • Databricks SQL queries and Jobs may fail, be delayed, or run degraded Recommendations No customer action is required at this time. Current Status The team is actively investigating Serverless Compute, Databricks SQL, and Jobs disruptions related to driver unreachable errors and cluster terminations; a probable root cause has been identified but not yet confirmed. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. identified Aug 05, 2026, 07:55 AM UTC

   Starting at approximately 04:23 UTC on August 5, 2026, customers using Azure Databricks may be experiencing failures or delayed startup of Serverless Compute workloads, along with degraded availability or errors affecting Databricks SQL queries and Jobs. Symptoms • Serverless Compute clusters failing to start or terminating unexpectedly • Errors indicating the compute driver is unreachable • Databricks SQL queries and Jobs may fail, be delayed, or run degraded Recommendations No customer action is required at this time. Current Status A cloud provider infrastructure issue has been identified as the likely cause, and the team is working with the provider to confirm and fully resolve the impact to Serverless Compute, Databricks SQL, and Jobs. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

6. identified Aug 05, 2026, 07:55 AM UTC

   Starting at approximately 04:23 UTC on August 5, 2026, customers using Azure Databricks may be experiencing failures or delayed startup of Serverless Compute workloads, along with degraded availability or errors affecting Databricks SQL queries and Jobs. Symptoms • Serverless Compute clusters failing to start or terminating unexpectedly • Errors indicating the compute driver is unreachable • Databricks SQL queries and Jobs may fail, be delayed, or run degraded Recommendations No customer action is required at this time. Current Status A cloud provider infrastructure issue has been identified as the likely cause, and the team is working with the provider to confirm and fully resolve the impact to Serverless Compute, Databricks SQL, and Jobs. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

7. monitoring Aug 05, 2026, 08:48 AM UTC

   Between 04:23 UTC and 08:30 UTC on August 5, 2026, a subset of customers using Azure Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability or errors affecting Databricks SQL and Jobs. Symptoms • Serverless Compute clusters failed to start or terminated unexpectedly • Errors indicating the compute driver was unreachable • Databricks SQL queries and Jobs experienced failures, delays, or degraded performance 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.

8. monitoring Aug 05, 2026, 08:48 AM UTC

   Between 04:23 UTC and 08:30 UTC on August 5, 2026, a subset of customers using Azure Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability or errors affecting Databricks SQL and Jobs. Symptoms • Serverless Compute clusters failed to start or terminated unexpectedly • Errors indicating the compute driver was unreachable • Databricks SQL queries and Jobs experienced failures, delays, or degraded performance 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.

9. resolved Aug 05, 2026, 09:36 AM UTC

   Between 04:23 UTC and 08:30 UTC on August 5, 2026, a subset of customers using Azure Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability or errors affecting Databricks SQL and Jobs. During this window, some cluster launches failed or terminated unexpectedly, and dependent query and job execution was impacted. Service behavior returned to normal by the end of the impact window. Symptoms • Serverless Compute clusters failed to start or terminated unexpectedly • Errors indicating the compute driver was unreachable • Databricks SQL queries and Jobs experienced failures, delays, or degraded performance 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

Read the full incident report →

Started Aug 04, 2026, 08:26 PM UTC· resolved Aug 04, 2026, 10:08 PM UTC

1. investigating Aug 04, 2026, 08:26 PM UTC

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

2. investigating Aug 04, 2026, 08:26 PM UTC

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

3. investigating Aug 04, 2026, 08:32 PM UTC

   Starting at approximately 20:00 UTC on August 4, 2026, customers using Azure Databricks may be experiencing failures or errors when using Classic Compute or Notebooks services. Some operations may fail, time out, or be delayed. We are actively investigating the issue. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks may fail to load, execute commands, or respond slowly • Intermittent API request failures affecting compute and notebook operations Recommendations No customer action is required at this time. Current Status The incident is in the Investigating stage; teams have identified a likely correlated deployment and are actively rolling it back while confirming root cause. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating Aug 04, 2026, 08:32 PM UTC

   Starting at approximately 20:00 UTC on August 4, 2026, customers using Azure Databricks may be experiencing failures or errors when using Classic Compute or Notebooks services. Some operations may fail, time out, or be delayed. We are actively investigating the issue. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks may fail to load, execute commands, or respond slowly • Intermittent API request failures affecting compute and notebook operations Recommendations No customer action is required at this time. Current Status The incident is in the Investigating stage; teams have identified a likely correlated deployment and are actively rolling it back while confirming root cause. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring Aug 04, 2026, 09:08 PM UTC

   Between 20:00 UTC and 20:56 UTC on August 4, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Classic Compute, Jobs, and Notebooks services. Affected customers may have seen failures, timeouts, or delays when starting or running compute clusters, executing notebook commands, or running jobs dependent on clusters. The disruption has since been mitigated. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks failed to load, execute commands, or responded slowly • Jobs experienced failures due to their dependency on affected clusters 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.

6. monitoring Aug 04, 2026, 09:08 PM UTC

   Between 20:00 UTC and 20:56 UTC on August 4, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Classic Compute, Jobs, and Notebooks services. Affected customers may have seen failures, timeouts, or delays when starting or running compute clusters, executing notebook commands, or running jobs dependent on clusters. The disruption has since been mitigated. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks failed to load, execute commands, or responded slowly • Jobs experienced failures due to their dependency on affected clusters 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.

7. resolved Aug 04, 2026, 10:08 PM UTC

   Between 20:00 UTC and 20:56 UTC on August 4, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Classic Compute, Jobs, and Notebooks services. Affected customers may have seen failures, timeouts, or delays when starting or running compute clusters, executing notebook commands, or running jobs dependent on clusters. The disruption was resolved by the end of the impact window. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks failed to load, execute commands, or responded slowly • Jobs experienced failures due to their dependency on affected clusters 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

Read the full incident report →

Started Aug 03, 2026, 04:56 PM UTC· resolved Aug 03, 2026, 07:23 PM UTC

1. investigating Aug 03, 2026, 04:56 PM UTC

   Impact Summary Starting at 03 August 2026 16:24 UTC], Notebooks, Jobs, SQL queries in Azure West Central US and East Asia may fail to execute. Recommendations No customer action is required at this time. Next Update We are working with our provider to investigate and restore services. The next update will be provided within one hour, or sooner as warranted.

2. investigating Aug 03, 2026, 04:56 PM UTC

   Impact Summary Starting at 03 August 2026 16:24 UTC], Notebooks, Jobs, SQL queries in Azure West Central US and East Asia may fail to execute. Recommendations No customer action is required at this time. Next Update We are working with our provider to investigate and restore services. The next update will be provided within one hour, or sooner as warranted.

3. identified Aug 03, 2026, 05:49 PM UTC

   Impact Summary Starting at 3 August 2026 16:24 UTC, Unity Catalog, Lakeflow Jobs, and workspace and account access in Azure West Central US and East Asia may fail to complete requests. Symptoms Customers may observe: - Requests to Unity Catalog failing or timing out - Lakeflow Jobs failing to start, or failing during execution - SQL queries failing or timing out - Notebook and Workspace UI actions that require a permission check failing to complete - Sign-in, workspace administration, and account administration actions not completing Recommendations No customer action is required at this time. We recommend avoiding repeated retries of failed operations while remediation continues. Customers with time-sensitive workloads may wish to evaluate their existing disaster recovery or high-availability plans while remediation continues. Current Status The cloud provider has identified the source of impact and remediation is in progress. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. identified Aug 03, 2026, 05:49 PM UTC

   Impact Summary Starting at 3 August 2026 16:24 UTC, Unity Catalog, Lakeflow Jobs, and workspace and account access in Azure West Central US and East Asia may fail to complete requests. Symptoms Customers may observe: - Requests to Unity Catalog failing or timing out - Lakeflow Jobs failing to start, or failing during execution - SQL queries failing or timing out - Notebook and Workspace UI actions that require a permission check failing to complete - Sign-in, workspace administration, and account administration actions not completing Recommendations No customer action is required at this time. We recommend avoiding repeated retries of failed operations while remediation continues. Customers with time-sensitive workloads may wish to evaluate their existing disaster recovery or high-availability plans while remediation continues. Current Status We have identified the source of impact and remediation is in progress. We are actively monitoring service health, and recovery may take a considerable amount of time. W Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring Aug 03, 2026, 06:21 PM UTC

   Between 16:24 and 18:01 UTC on August 3, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors affecting Databricks SQL, Declarative Pipelines, Jobs, Notebooks, and Unity Catalog, along with intermittent login or authentication failures. These issues affected services that depend on identity and access management functions. Symptoms • Failures or errors when submitting or running Jobs • Errors or delays when accessing Notebooks, Databricks SQL, or Unity Catalog • Intermittent login, authentication, or access-management failures 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.

6. monitoring Aug 03, 2026, 06:21 PM UTC

   Between 16:24 and 18:01 UTC on August 3, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors affecting Databricks SQL, Declarative Pipelines, Jobs, Notebooks, and Unity Catalog, along with intermittent login or authentication failures. These issues affected services that depend on identity and access management functions. Symptoms • Failures or errors when submitting or running Jobs • Errors or delays when accessing Notebooks, Databricks SQL, or Unity Catalog • Intermittent login, authentication, or access-management failures 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.

7. resolved Aug 03, 2026, 07:23 PM UTC

   Between 16:24 and 18:01 UTC on August 3, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors affecting Databricks SQL, Declarative Pipelines, Jobs, Notebooks, and Unity Catalog, along with intermittent login or authentication failures. These issues affected services that depend on identity and access management functions. Symptoms • Failures or errors when submitting or running Jobs • Errors or delays when accessing Notebooks, Databricks SQL, or Unity Catalog • Intermittent login, authentication, or access-management failures 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

Read the full incident report →

Started Aug 03, 2026, 02:07 AM UTC· resolved Aug 03, 2026, 05:27 AM UTC

1. investigating Aug 03, 2026, 02:07 AM UTC

   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.

2. investigating Aug 03, 2026, 02:07 AM UTC

   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.

3. identified Aug 03, 2026, 02:31 AM UTC

   Starting at approximately 00:42 UTC on August 3, 2026, customers using Azure Databricks may be experiencing failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services include Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures and job termination errors. We are actively investigating the issue. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Recommendations No customer action is required at this time. Current Status We are actively investigating the incident affecting Classic Compute, Serverless Compute, and Jobs, caused by an issue with our cloud provider, and are working closely with them to restore full service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. identified Aug 03, 2026, 02:31 AM UTC

   Starting at approximately 00:42 UTC on August 3, 2026, customers using Azure Databricks may be experiencing failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services include Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures and job termination errors. We are actively investigating the issue. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Recommendations No customer action is required at this time. Current Status We are actively investigating the incident affecting Classic Compute, Serverless Compute, and Jobs, caused by an issue with our cloud provider, and are working closely with them to restore full service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. identified Aug 03, 2026, 03:27 AM UTC

   Starting at approximately 00:42 UTC on August 3, 2026, some customers using Azure Databricks in the regions may be experiencing failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services include Classic Compute, Serverless Compute, and Jobs. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Recommendations No customer action is required at this time. Current Status We have identified the issue affecting some customers in the regions and are working closely with our cloud provider to restore full service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

6. identified Aug 03, 2026, 03:27 AM UTC

   Starting at approximately 00:42 UTC on August 3, 2026, some customers using Azure Databricks in the regions may be experiencing failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services include Classic Compute, Serverless Compute, and Jobs. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Recommendations No customer action is required at this time. Current Status We have identified the issue affecting some customers in the regions and are working closely with our cloud provider to restore full service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

7. monitoring Aug 03, 2026, 04:05 AM UTC

   Between 0:42 UTC and 3:43 UTC on August 3, 2026, a subset of customers using Azure Databricks may have experienced failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services included Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures, job termination errors, and delayed startup of Serverless Compute workloads. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads 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.

8. monitoring Aug 03, 2026, 04:05 AM UTC

   Between 0:42 UTC and 3:43 UTC on August 3, 2026, a subset of customers using Azure Databricks may have experienced failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services included Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures, job termination errors, and delayed startup of Serverless Compute workloads. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads 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.

9. resolved Aug 03, 2026, 05:27 AM UTC

   Between 0:42 UTC and 3:43 UTC on August 3, 2026, a subset of customers using Azure Databricks may have experienced failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services included Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures, job termination errors, and delayed startup of Serverless Compute workloads. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads 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

Read the full incident report →

Started Jul 23, 2026, 03:16 PM UTC· resolved Jul 23, 2026, 08:07 PM UTC

1. investigating Jul 23, 2026, 03:16 PM UTC

   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.

2. investigating Jul 23, 2026, 03:16 PM UTC

   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.

3. investigating Jul 23, 2026, 03:39 PM UTC

   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.

4. investigating Jul 23, 2026, 03:39 PM UTC

   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.

5. identified Jul 23, 2026, 04:05 PM UTC

   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.

6. identified Jul 23, 2026, 04:05 PM UTC

   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.

7. identified Jul 23, 2026, 05:10 PM UTC

   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.

8. identified Jul 23, 2026, 05:10 PM UTC

   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.

9. identified Jul 23, 2026, 06:01 PM UTC

   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.

10. identified Jul 23, 2026, 06:01 PM UTC

    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.

11. monitoring Jul 23, 2026, 06:52 PM UTC

    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.

12. monitoring Jul 23, 2026, 06:52 PM UTC

    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.

13. resolved Jul 23, 2026, 08:07 PM UTC

    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

Read the full incident report →

Started Jul 16, 2026, 09:53 AM UTC· resolved Jul 16, 2026, 01:41 PM UTC

1. investigating Jul 16, 2026, 09:53 AM UTC

   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.

2. investigating Jul 16, 2026, 09:53 AM UTC

   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.

3. identified Jul 16, 2026, 10:29 AM UTC

   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.

4. identified Jul 16, 2026, 10:29 AM UTC

   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.

5. monitoring Jul 16, 2026, 10:43 AM UTC

   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.

6. monitoring Jul 16, 2026, 10:43 AM UTC

   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.

7. identified Jul 16, 2026, 11:44 AM UTC

   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.

8. identified Jul 16, 2026, 11:44 AM UTC

   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.

9. monitoring Jul 16, 2026, 12:14 PM UTC

   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.

10. monitoring Jul 16, 2026, 12:14 PM UTC

    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.

11. resolved Jul 16, 2026, 01:41 PM UTC

    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

Read the full incident report →

Started Jul 16, 2026, 12:53 AM UTC· resolved Jul 16, 2026, 02:52 AM UTC

1. monitoring Jul 16, 2026, 12:53 AM UTC

   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.

2. monitoring Jul 16, 2026, 12:53 AM UTC

   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.

3. resolved Jul 16, 2026, 02:52 AM UTC

   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

Read the full incident report →

Started Jul 15, 2026, 10:14 PM UTC· resolved Jul 16, 2026, 12:25 AM UTC

1. investigating Jul 15, 2026, 10:14 PM UTC

   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.

2. investigating Jul 15, 2026, 10:14 PM UTC

   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.

3. identified Jul 15, 2026, 10:30 PM UTC

   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.

4. identified Jul 15, 2026, 10:30 PM UTC

   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.

5. identified Jul 15, 2026, 10:55 PM UTC

   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.

6. identified Jul 15, 2026, 10:55 PM UTC

   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.

7. monitoring Jul 15, 2026, 11:01 PM UTC

   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.

8. monitoring Jul 15, 2026, 11:01 PM UTC

   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.

9. monitoring Jul 15, 2026, 11:04 PM UTC

   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.

10. monitoring Jul 15, 2026, 11:04 PM UTC

    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.

11. monitoring Jul 16, 2026, 12:05 AM UTC

    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.

12. monitoring Jul 16, 2026, 12:05 AM UTC

    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.

13. resolved Jul 16, 2026, 12:25 AM UTC

    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

Read the full incident report →

Started Jul 10, 2026, 11:30 PM UTC· resolved Jul 11, 2026, 12:30 AM UTC

1. monitoring Jul 10, 2026, 11:30 PM UTC

   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.

2. monitoring Jul 10, 2026, 11:30 PM UTC

   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.

3. resolved Jul 11, 2026, 12:30 AM UTC

   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

Read the full incident report →

Started Jul 07, 2026, 12:09 PM UTC· resolved Jul 07, 2026, 03:52 PM UTC

1. investigating Jul 07, 2026, 12:09 PM UTC

   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.

2. investigating Jul 07, 2026, 12:09 PM UTC

   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.

3. investigating Jul 07, 2026, 12:35 PM UTC

   Starting at approximately 11:00 UTC on July 7, 2026, customers using Azure Databricks may be experiencing failures when creating apps, along with errors or failures affecting workspace creation and other workspace management operations. Symptoms • Failures when attempting to create new apps • Workspace creation requests failing or stalled • Errors affecting other workspace management operations (create, read, update, delete) Recommendations No customer action is required at this time. Current Status The incident is under active investigation as the team works to identify the root cause and restore full functionality to Databricks Apps and Workspace operations. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating Jul 07, 2026, 12:35 PM UTC

   Starting at approximately 11:00 UTC on July 7, 2026, customers using Azure Databricks may be experiencing failures when creating apps, along with errors or failures affecting workspace creation and other workspace management operations. Symptoms • Failures when attempting to create new apps • Workspace creation requests failing or stalled • Errors affecting other workspace management operations (create, read, update, delete) Recommendations No customer action is required at this time. Current Status The incident is under active investigation as the team works to identify the root cause and restore full functionality to Databricks Apps and Workspace operations. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring Jul 07, 2026, 01:18 PM UTC

   Between approximately 11:00 UTC and 13:00 UTC on July 7, 2026, a subset of customers using Azure Databricks may have experienced failures when creating apps, along with errors or failures affecting workspace creation and other workspace management operations. Some customers may also have experienced delayed or failed creation of endpoints for related serverless products during this window. Symptoms • Failures when attempting to create new Databricks Apps • Workspace creation requests failing or stalled • Errors affecting other workspace management operations (create, read, update, delete) 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.

6. monitoring Jul 07, 2026, 01:18 PM UTC

   Between approximately 11:00 UTC and 13:00 UTC on July 7, 2026, a subset of customers using Azure Databricks may have experienced failures when creating apps, along with errors or failures affecting workspace creation and other workspace management operations. Some customers may also have experienced delayed or failed creation of endpoints for related serverless products during this window. Symptoms • Failures when attempting to create new Databricks Apps • Workspace creation requests failing or stalled • Errors affecting other workspace management operations (create, read, update, delete) 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.

7. resolved Jul 07, 2026, 03:52 PM UTC

   Between approximately 11:00 UTC and 13:00 UTC on July 7, 2026, a subset of customers using Azure Databricks may have experienced failures when creating apps, along with errors or failures affecting workspace creation and other workspace management operations. Some customers may also have experienced delayed or failed creation of endpoints for related serverless products during this window. Symptoms • Failures when attempting to create new Databricks Apps • Workspace creation requests failing or stalled • Errors affecting other workspace management operations (create, read, update, delete) Current Status This incident has been fully resolved as of

Read the full incident report →

Started Jun 26, 2026, 05:48 PM UTC· resolved Jun 26, 2026, 08:43 PM UTC

1. investigating Jun 26, 2026, 05:48 PM UTC

   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.

2. investigating Jun 26, 2026, 05:48 PM UTC

   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.

3. investigating Jun 26, 2026, 05:58 PM UTC

   Starting at approximately 6:46 UTC on June 26, 2026, a subset of customers using Azure Databricks may be experiencing errors or failures when using Model Serving, specifically when accessing served model build logs and related endpoints. Symptoms • Errors or timeouts when attempting to retrieve build logs for served model entities in Model Serving • Requests to Model Serving endpoints failing or taking an extended time before returning an error • Degraded availability of Model Serving served-entity operations Recommendations No customer action is required at this time. Current Status We are actively investigating an issue causing errors and timeouts for a subset of customers using Model Serving, and our engineering teams are engaged. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating Jun 26, 2026, 05:58 PM UTC

   Starting at approximately 6:46 UTC on June 26, 2026, a subset of customers using Azure Databricks may be experiencing errors or failures when using Model Serving, specifically when accessing served model build logs and related endpoints. Symptoms • Errors or timeouts when attempting to retrieve build logs for served model entities in Model Serving • Requests to Model Serving endpoints failing or taking an extended time before returning an error • Degraded availability of Model Serving served-entity operations Recommendations No customer action is required at this time. Current Status We are actively investigating an issue causing errors and timeouts for a subset of customers using Model Serving, and our engineering teams are engaged. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. investigating Jun 26, 2026, 07:00 PM UTC

   Starting at approximately 6:46 UTC on June 26, 2026, a subset of customers using Azure Databricks may be experiencing errors or failures when using Model Serving, specifically when accessing served model build logs and related endpoints. Symptoms • Errors or timeouts when attempting to retrieve build logs for served model entities in Model Serving • Requests to Model Serving endpoints failing or taking an extended time before returning an error • Degraded availability of Model Serving served-entity operations Recommendations No customer action is required at this time. Current Status We are actively investigating an issue causing errors and timeouts for a subset of customers using Model Serving, and our engineering teams are engaged. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

6. investigating Jun 26, 2026, 07:00 PM UTC

   Starting at approximately 6:46 UTC on June 26, 2026, a subset of customers using Azure Databricks may be experiencing errors or failures when using Model Serving, specifically when accessing served model build logs and related endpoints. Symptoms • Errors or timeouts when attempting to retrieve build logs for served model entities in Model Serving • Requests to Model Serving endpoints failing or taking an extended time before returning an error • Degraded availability of Model Serving served-entity operations Recommendations No customer action is required at this time. Current Status We are actively investigating an issue causing errors and timeouts for a subset of customers using Model Serving, and our engineering teams are engaged. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

7. monitoring Jun 26, 2026, 07:43 PM UTC

   Between approximately 1:20 UTC and 19:34 UTC on June 26, 2026, a subset of customers using Azure Databricks may have experienced errors or failures when using Model Serving. Specifically, attempts to deploy or update served model endpoints may have failed, and requests to retrieve build logs for served model entities may have timed out or returned errors. This disruption affected Model Serving availability across multiple regions. Symptoms • Errors or failures when attempting to deploy or update served model endpoints in Model Serving • Timeouts or errors when attempting to retrieve build logs for served model entities • Degraded availability of Model Serving served-entity operations 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.

8. monitoring Jun 26, 2026, 07:43 PM UTC

   Between approximately 1:20 UTC and 19:34 UTC on June 26, 2026, a subset of customers using Azure Databricks may have experienced errors or failures when using Model Serving. Specifically, attempts to deploy or update served model endpoints may have failed, and requests to retrieve build logs for served model entities may have timed out or returned errors. This disruption affected Model Serving availability across multiple regions. Symptoms • Errors or failures when attempting to deploy or update served model endpoints in Model Serving • Timeouts or errors when attempting to retrieve build logs for served model entities • Degraded availability of Model Serving served-entity operations 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.

9. resolved Jun 26, 2026, 08:43 PM UTC

   Between approximately 1:20 UTC and 19:34 UTC on June 26, 2026, a subset of customers using Azure Databricks may have experienced errors or failures when using Model Serving. Specifically, attempts to deploy or update served model endpoints may have failed, and requests to retrieve build logs for served model entities may have timed out or returned errors. This disruption affected Model Serving availability across multiple regions. Symptoms • Errors or failures when attempting to deploy or update served model endpoints in Model Serving • Timeouts or errors when attempting to retrieve build logs for served model entities • Degraded availability of Model Serving served-entity operations 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

Read the full incident report →

Started Jun 24, 2026, 04:38 AM UTC· resolved Jun 24, 2026, 08:18 AM UTC

1. investigating Jun 24, 2026, 04:38 AM UTC

   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.

2. investigating Jun 24, 2026, 04:38 AM UTC

   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.

3. identified Jun 24, 2026, 05:39 AM UTC

   Starting at approximately 4:12 UTC on June 24, 2026, a subset of customers using Azure Databricks may be experiencing degraded availability or errors with Unity Catalog, Databricks SQL, AI/BI, and Jobs services. Customers may be encountering failures or elevated error rates when accessing or querying data assets, running jobs, or interacting with Unity Catalog resources. Symptoms • Errors or failures when accessing Unity Catalog resources such as tables, volumes, or metadata • Degraded availability or timeouts when running Databricks SQL queries or Jobs workloads • Failures or elevated error rates when using AI/BI features Recommendations No customer action is required at this time. Current Status We have identified degraded availability affecting Unity Catalog, Databricks SQL, AI/BI, and Jobs services, and our teams are actively working with our cloud provider to investigate and confirm full resolution. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. identified Jun 24, 2026, 05:39 AM UTC

   Starting at approximately 4:12 UTC on June 24, 2026, a subset of customers using Azure Databricks may be experiencing degraded availability or errors with Unity Catalog, Databricks SQL, AI/BI, and Jobs services. Customers may be encountering failures or elevated error rates when accessing or querying data assets, running jobs, or interacting with Unity Catalog resources. Symptoms • Errors or failures when accessing Unity Catalog resources such as tables, volumes, or metadata • Degraded availability or timeouts when running Databricks SQL queries or Jobs workloads • Failures or elevated error rates when using AI/BI features Recommendations No customer action is required at this time. Current Status We have identified degraded availability affecting Unity Catalog, Databricks SQL, AI/BI, and Jobs services, and our teams are actively working with our cloud provider to investigate and confirm full resolution. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring Jun 24, 2026, 06:35 AM UTC

   Between 4:12 UTC and 6:03 UTC on June 24, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Unity Catalog, Databricks SQL, AI/BI, and Jobs services. Customers may have encountered failures, elevated error rates, or degraded performance when accessing data assets, running queries, or executing jobs that depend on these services. Symptoms • Errors or failures when accessing Unity Catalog resources such as tables, volumes, or metadata • Degraded availability or timeouts when running Databricks SQL queries or Jobs workloads • Failures or elevated error rates when using AI/BI features 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.

6. monitoring Jun 24, 2026, 06:35 AM UTC

   Between 4:12 UTC and 6:03 UTC on June 24, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Unity Catalog, Databricks SQL, AI/BI, and Jobs services. Customers may have encountered failures, elevated error rates, or degraded performance when accessing data assets, running queries, or executing jobs that depend on these services. Symptoms • Errors or failures when accessing Unity Catalog resources such as tables, volumes, or metadata • Degraded availability or timeouts when running Databricks SQL queries or Jobs workloads • Failures or elevated error rates when using AI/BI features 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.

7. resolved Jun 24, 2026, 08:18 AM UTC

   Between 4:12 UTC and 6:03 UTC on June 24, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Unity Catalog, Databricks SQL, AI/BI, and Jobs services. Customers may have encountered failures, elevated error rates, or degraded performance when accessing data assets, running queries, or executing jobs that depend on these services. Symptoms • Errors or failures when accessing Unity Catalog resources such as tables, volumes, or metadata • Degraded availability or timeouts when running Databricks SQL queries or Jobs workloads • Failures or elevated error rates when using AI/BI features Current Status This incident has been fully resolved as of 24 June 2026 6:03 UTC. Normal service operation has been restored. 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

Read the full incident report →

Started Jun 14, 2026, 04:45 AM UTC· resolved Jun 14, 2026, 06:28 AM UTC

1. investigating Jun 14, 2026, 04:45 AM UTC

   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.

2. investigating Jun 14, 2026, 04:45 AM UTC

   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.

3. monitoring Jun 14, 2026, 05:22 AM UTC

   Between 04:07 UTC and 04:40 UTC on June 14, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors when using Unity Catalog and Jobs. During this period, customers may have encountered failures or disruptions when accessing Unity Catalog or running Jobs that depend on Unity Catalog. Symptoms • Errors or failures when accessing or performing operations in Unity Catalog • Jobs dependent on Unity Catalog may have failed or experienced degraded availability 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.

4. monitoring Jun 14, 2026, 05:22 AM UTC

   Between 04:07 UTC and 04:40 UTC on June 14, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors when using Unity Catalog and Jobs. During this period, customers may have encountered failures or disruptions when accessing Unity Catalog or running Jobs that depend on Unity Catalog. Symptoms • Errors or failures when accessing or performing operations in Unity Catalog • Jobs dependent on Unity Catalog may have failed or experienced degraded availability 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.

5. resolved Jun 14, 2026, 06:28 AM UTC

   Impact Summary Between 04:07 UTC and 04:40 UTC on June 14, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors when using Unity Catalog and Jobs. During this period, customers may have encountered failures or disruptions when accessing Unity Catalog or running Jobs that depend on Unity Catalog. Symptoms • Errors or failures when accessing or performing operations in Unity Catalog • Jobs dependent on Unity Catalog may have failed or experienced degraded availability Current Status This incident has been fully resolved as of 14 June 2026 04:40 UTC. Normal service operation has been restored. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Next Update No further updates are planned unless conditions change. 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

Read the full incident report →

Started Jun 11, 2026, 05:50 PM UTC· resolved Jun 11, 2026, 08:28 PM UTC

1. investigating Jun 11, 2026, 05:50 PM UTC

   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.

2. investigating Jun 11, 2026, 05:50 PM UTC

   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.

3. investigating Jun 11, 2026, 06:30 PM UTC

   Impact Summary Starting at 11 June 2026 17:28 UTC, customers using Unity Catalog in Azure West US may experience service failures or timeouts. Lakeflow Spark Declarative Pipelines, Lakeflow Jobs, and login and authentication operations that depend on Unity Catalog are also affected. Symptoms Customers may observe: - Unity Catalog operations failing or timing out - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly - Lakeflow Jobs failures involving Unity Catalog operations - Login and authentication failures, including inability to create access tokens Recommendations No customer action is required at this time. Current Status The cause of this incident has been identified. Our engineering team is actively working to restore service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating Jun 11, 2026, 06:30 PM UTC

   Impact Summary Starting at 11 June 2026 17:28 UTC, customers using Unity Catalog in Azure West US may experience service failures or timeouts. Lakeflow Spark Declarative Pipelines, Lakeflow Jobs, and login and authentication operations that depend on Unity Catalog are also affected. Symptoms Customers may observe: - Unity Catalog operations failing or timing out - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly - Lakeflow Jobs failures involving Unity Catalog operations - Login and authentication failures, including inability to create access tokens Recommendations No customer action is required at this time. Current Status The cause of this incident has been identified. Our engineering team is actively working to restore service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring Jun 11, 2026, 06:47 PM UTC

   Impact Summary From 11 June 2026 17:28 UTC to 11 June 2026 18:09 UTC, customers using Unity Catalog in Azure West US experienced service failures or timeouts. Service has been restored. Symptoms Customers experienced: - Unity Catalog operations failing or timing out - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly - Lakeflow Jobs failures involving Unity Catalog operations - Login and authentication failures, including inability to create access tokens Recommendations No customer action is required at this time. Current Status Service has been restored as of 11 June 2026 18:09 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status

6. monitoring Jun 11, 2026, 06:47 PM UTC

   Impact Summary From 11 June 2026 17:28 UTC to 11 June 2026 18:09 UTC, customers using Unity Catalog in Azure West US experienced service failures or timeouts. Service has been restored. Symptoms Customers experienced: - Unity Catalog operations failing or timing out - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly - Lakeflow Jobs failures involving Unity Catalog operations - Login and authentication failures, including inability to create access tokens Recommendations No customer action is required at this time. Current Status Service has been restored as of 11 June 2026 18:09 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status

7. resolved Jun 11, 2026, 08:28 PM UTC

   Impact Summary Between 11 June 2026 17:28 UTC and 11 June 2026 18:09 UTC, customers using Unity Catalog in Azure West US experienced service failures or timeouts. Symptoms Customers experienced: - Unity Catalog operations failing or timing out - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly - Lakeflow Jobs failures involving Unity Catalog operations - Login and authentication failures, including inability to create access tokens Current Status This incident has been fully resolved as of 11 June 2026 18:09 UTC. Normal service operation has been restored. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Next Update No further updates are planned unless conditions change. 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

Read the full incident report →

Started Jun 10, 2026, 07:00 AM UTC· resolved Jun 10, 2026, 10:27 AM UTC

1. investigating Jun 10, 2026, 07:00 AM UTC

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

2. investigating Jun 10, 2026, 07:00 AM UTC

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

3. identified Jun 10, 2026, 07:11 AM UTC

   Starting at approximately 3:54 UTC on June 10, 2026, a subset of customers using Azure Databricks may be experiencing failures and errors when attempting to launch or restart Classic Compute clusters. Affected customers may find that their clusters are unable to start successfully, with startup attempts resulting in errors or prolonged failures. This disruption is affecting Classic Compute workloads, and the issue remains ongoing as our engineering teams continue to work toward a resolution. Symptoms • Cluster launch or restart attempts are failing, with errors indicating that the compute instance is unreachable after bootstrap completes • Classic Compute clusters cannot be started or restarted, leaving dependent workloads unavailable • Degraded availability of Classic Compute resources, with cluster startup errors being reported during normal operations Recommendations No customer action is required at this time. Current Status We have identified the root cause and are working on a fix. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. identified Jun 10, 2026, 07:11 AM UTC

   Starting at approximately 3:54 UTC on June 10, 2026, a subset of customers using Azure Databricks may be experiencing failures and errors when attempting to launch or restart Classic Compute clusters. Affected customers may find that their clusters are unable to start successfully, with startup attempts resulting in errors or prolonged failures. This disruption is affecting Classic Compute workloads, and the issue remains ongoing as our engineering teams continue to work toward a resolution. Symptoms • Cluster launch or restart attempts are failing, with errors indicating that the compute instance is unreachable after bootstrap completes • Classic Compute clusters cannot be started or restarted, leaving dependent workloads unavailable • Degraded availability of Classic Compute resources, with cluster startup errors being reported during normal operations Recommendations No customer action is required at this time. Current Status We have identified the root cause and are working on a fix. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring Jun 10, 2026, 08:30 AM UTC

   Between 3:54 UTC and 7:53 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced failures or errors when attempting to launch or restart Classic Compute clusters. Affected customers may have found that cluster startup attempts resulted in errors or prolonged failures, with degraded availability of Classic Compute workloads during this period. Symptoms • Classic Compute cluster launch or restart attempts failed with errors indicating the compute instance was unreachable after bootstrap completed. • Customers were unable to start or restart Classic Compute clusters, leaving dependent workloads unavailable. • Cluster startup errors were reported during normal operations, with some clusters failing intermittently after initial recovery. 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.

6. monitoring Jun 10, 2026, 08:30 AM UTC

   Between 3:54 UTC and 7:53 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced failures or errors when attempting to launch or restart Classic Compute clusters. Affected customers may have found that cluster startup attempts resulted in errors or prolonged failures, with degraded availability of Classic Compute workloads during this period. Symptoms • Classic Compute cluster launch or restart attempts failed with errors indicating the compute instance was unreachable after bootstrap completed. • Customers were unable to start or restart Classic Compute clusters, leaving dependent workloads unavailable. • Cluster startup errors were reported during normal operations, with some clusters failing intermittently after initial recovery. 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.

7. resolved Jun 10, 2026, 10:27 AM UTC

   Between 3:54 UTC and 7:53 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced failures or errors when attempting to launch or restart Classic Compute clusters. Affected customers may have found that cluster startup attempts resulted in errors or prolonged failures, with degraded availability of Classic Compute workloads during this period. Symptoms • Classic Compute cluster launch or restart attempts failed with errors indicating the compute instance was unreachable after bootstrap completed. • Customers were unable to start or restart Classic Compute clusters, leaving dependent workloads unavailable. • Cluster startup errors were reported during normal operations, with some clusters failing intermittently after initial recovery. 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

Read the full incident report →

Started Jun 10, 2026, 03:57 AM UTC· resolved Jun 10, 2026, 08:26 AM UTC

1. investigating Jun 10, 2026, 03:57 AM UTC

   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.

2. investigating Jun 10, 2026, 03:57 AM UTC

   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.

3. investigating Jun 10, 2026, 04:19 AM UTC

   Starting at approximately 00:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Recommendations No customer action is required at this time. Current Status We are actively investigating incident causing errors and failures for customers using the Notebooks service, and our engineering team is working to identify and apply a resolution. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating Jun 10, 2026, 04:19 AM UTC

   Starting at approximately 00:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Recommendations No customer action is required at this time. Current Status We are actively investigating incident causing errors and failures for customers using the Notebooks service, and our engineering team is working to identify and apply a resolution. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. identified Jun 10, 2026, 05:13 AM UTC

   Starting at approximately 0:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Recommendations No customer action is required at this time. Current Status Our engineering team has identified the root cause of the incident impacting the Notebooks service and has implemented a mitigation. We are continuing to investigate and closely monitor the situation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

6. identified Jun 10, 2026, 05:13 AM UTC

   Starting at approximately 0:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Recommendations No customer action is required at this time. Current Status Our engineering team has identified the root cause of the incident impacting the Notebooks service and has implemented a mitigation. We are continuing to investigate and closely monitor the situation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

7. monitoring Jun 10, 2026, 05:30 AM UTC

   Between 00:43 UTC and 04:01 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced errors and failures when attempting to use the Notebooks service. Affected customers may have been unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters 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.

8. monitoring Jun 10, 2026, 05:30 AM UTC

   Between 00:43 UTC and 04:01 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced errors and failures when attempting to use the Notebooks service. Affected customers may have been unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters 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.

9. resolved Jun 10, 2026, 08:26 AM UTC

   Between 00:43 UTC and 04:01 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced errors and failures when attempting to use the Notebooks service. Affected customers may have been unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters 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

Read the full incident report →

Started Jun 08, 2026, 06:56 PM UTC· resolved Jun 08, 2026, 11:16 PM UTC

1. identified Jun 08, 2026, 06:56 PM UTC

   Lakebase project creation is temporarily unavailable in the East US Region. Existing Lakebase projects will continue to operate normally.

2. identified Jun 08, 2026, 06:56 PM UTC

   Lakebase project creation is temporarily unavailable in the East US Region. Existing Lakebase projects will continue to operate normally.

3. monitoring Jun 08, 2026, 11:10 PM UTC

   Lakebase Project creation had been temporarily unavailable in the East US Region. Pre-existing Lakebase Projects continued to operate normally. Project creation is now re-enabled. We will continue to monitor the platform for 1 hour to verify normal operation.

4. resolved Jun 08, 2026, 11:16 PM UTC

   As of 23:00 UTC June 8 2026, Lakebase Project creation has been re-enabled in the East US Region. 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

Read the full incident report →

Started Jun 05, 2026, 07:29 PM UTC· resolved Jun 05, 2026, 09:06 PM UTC

1. investigating Jun 05, 2026, 07:29 PM UTC

   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.

2. investigating Jun 05, 2026, 07:29 PM UTC

   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.

3. investigating Jun 05, 2026, 07:41 PM UTC

   Starting at approximately 18:51 UTC on June 5, 2026, customers using Azure Databricks may be experiencing failures or errors when attempting to create, update, or delete Databricks workspaces. Workspace management operations may be unavailable or returning errors during this period. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations not completing or returning error responses Recommendations No customer action is required at this time. Our engineering team is actively investigating and working to restore full service. Please retry workspace operations once the incident is resolved. Current Status Our engineering team is actively investigating failures affecting Workspace CRUD operations and working to restore service as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating Jun 05, 2026, 07:41 PM UTC

   Starting at approximately 18:51 UTC on June 5, 2026, customers using Azure Databricks may be experiencing failures or errors when attempting to create, update, or delete Databricks workspaces. Workspace management operations may be unavailable or returning errors during this period. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations not completing or returning error responses Recommendations No customer action is required at this time. Our engineering team is actively investigating and working to restore full service. Please retry workspace operations once the incident is resolved. Current Status Our engineering team is actively investigating failures affecting Workspace CRUD operations and working to restore service as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring Jun 05, 2026, 08:06 PM UTC

   Between 18:51 UTC and 19:55 UTC on June 5, 2026, customers using Azure Databricks may have experienced failures or errors when attempting to create, update, or delete Databricks workspaces. A subset of customers may have experienced Workspace management operations being unavailable or returning errors during this period. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations not completing or returning error responses 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.

6. monitoring Jun 05, 2026, 08:06 PM UTC

   Between 18:51 UTC and 19:55 UTC on June 5, 2026, customers using Azure Databricks may have experienced failures or errors when attempting to create, update, or delete Databricks workspaces. A subset of customers may have experienced Workspace management operations being unavailable or returning errors during this period. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations not completing or returning error responses 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.

7. resolved Jun 05, 2026, 09:06 PM UTC

   Between 18:51 UTC and 19:55 UTC on June 5, 2026, customers using Azure Databricks may have experienced failures or errors when attempting to create, update, or delete Databricks workspaces. During this period, a subset of customers using Azure Databricks may have found workspace management operations unavailable or returning errors. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations did not complete or returned error responses Current Status This incident has been resolved as of 19:55 UTC June 5 2026. 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

Read the full incident report →

Started May 29, 2026, 09:10 PM UTC· resolved May 29, 2026, 10:40 PM UTC

1. investigating May 29, 2026, 09:10 PM UTC

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

2. investigating May 29, 2026, 09:10 PM UTC

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

3. monitoring May 29, 2026, 09:42 PM UTC

   Impact Summary From 29 May 2026 21:00 UTC to 29 May 2026 21:18 UTC, customers using Serverless Compute and Lakeflow Spark Declarative Pipelines in the Canada Central region experienced interruptions to running workloads. Service has been restored. Symptoms Customers experienced: - Serverless Compute clusters terminating unexpectedly - Jobs and pipeline runs failing or not starting Recommendations No customer action is required. Current Status Service has been restored as of 29 May 2026 21:18 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour.

4. monitoring May 29, 2026, 09:42 PM UTC

   Impact Summary From 29 May 2026 21:00 UTC to 29 May 2026 21:18 UTC, customers using Serverless Compute and Lakeflow Spark Declarative Pipelines in the Canada Central region experienced interruptions to running workloads. Service has been restored. Symptoms Customers experienced: - Serverless Compute clusters terminating unexpectedly - Jobs and pipeline runs failing or not starting Recommendations No customer action is required. Current Status Service has been restored as of 29 May 2026 21:18 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour.

5. resolved May 29, 2026, 10:40 PM UTC

   Impact Summary From 29 May 2026 21:00 UTC to 29 May 2026 21:18 UTC, customers using Serverless Compute and Lakeflow Spark Declarative Pipelines in the Canada Central region experienced interruptions to running workloads. Service has been restored. Symptoms Customers experienced: - Serverless Compute clusters terminating unexpectedly - Jobs and pipeline runs failing or not starting Current Status This incident has been fully resolved as of 29 May 2026 21:18 UTC. We apologize for the disruption. If you require further details about this incident, please submit an Azure support ticket. Next Update No further updates are planned for this incident. 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

Read the full incident report →

Started May 29, 2026, 05:59 AM UTC· resolved May 29, 2026, 08:35 PM UTC

1. investigating May 29, 2026, 05:59 AM UTC

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

2. investigating May 29, 2026, 05:59 AM UTC

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

3. investigating May 29, 2026, 06:19 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We are actively investigating failures affecting Classic Compute, Serverless Compute, and Databricks Apps in collaboration with our cloud provider, and are working to restore full service availability as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating May 29, 2026, 06:19 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We are actively investigating failures affecting Classic Compute, Serverless Compute, and Databricks Apps in collaboration with our cloud provider, and are working to restore full service availability as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. identified May 29, 2026, 07:37 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. For live updates on the underlying infrastructure status, customers can refer to the Azure status page at https://azure.status.microsoft/en-us/status. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

6. identified May 29, 2026, 07:37 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. For live updates on the underlying infrastructure status, customers can refer to the Azure status page at https://azure.status.microsoft/en-us/status. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

7. identified May 29, 2026, 08:49 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

8. identified May 29, 2026, 08:49 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

9. identified May 29, 2026, 09:57 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

10. identified May 29, 2026, 09:57 AM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

11. identified May 29, 2026, 11:37 AM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute appears to be showing partial recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

12. identified May 29, 2026, 11:37 AM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute appears to be showing partial recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

13. identified May 29, 2026, 01:07 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

14. identified May 29, 2026, 01:07 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

15. identified May 29, 2026, 03:38 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

16. identified May 29, 2026, 03:38 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

17. identified May 29, 2026, 04:39 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, and other Databricks services appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

18. identified May 29, 2026, 04:39 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, and other Databricks services appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at 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.

19. monitoring May 29, 2026, 06:16 PM UTC

    Impact Summary From 29 May 2026 05:00 UTC to 29 May 2026 16:40 UTC, customers using Databricks in the West US 2 region experienced disruptions to compute startup, query execution, and data access. Service has been restored. Symptoms Customers experienced: • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, and other Databricks services appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

20. monitoring May 29, 2026, 06:16 PM UTC

    Impact Summary From 29 May 2026 05:00 UTC to 29 May 2026 16:40 UTC, customers using Databricks in the West US 2 region experienced disruptions to compute startup, query execution, and data access. Service has been restored. Symptoms Customers experienced: • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, and other Databricks services appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

21. resolved May 29, 2026, 08:35 PM UTC

    Impact Summary From 29 May 2026 05:00 UTC to 29 May 2026 16:40 UTC, customers using Databricks in the West US 2 region experienced disruptions to compute startup, query execution, and data access. Service has been restored. Symptoms Customers experienced: • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Current Status This incident has been fully resolved as of 29 May 2026 16:40 UTC. We apologize for the disruption. This incident was related to a cloud provider issue. Additional information is available on the cloud provider's status page: https://azure.status.microsoft.com/en-us/status/ If you require further details about this incident, please submit an Azure support ticket. Next Update No further updates are planned for this incident. 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

Read the full incident report →

Started May 26, 2026, 07:02 PM UTC· resolved May 26, 2026, 10:11 PM UTC

1. investigating May 26, 2026, 07:02 PM UTC

   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.

2. investigating May 26, 2026, 07:02 PM UTC

   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.

3. investigating May 26, 2026, 08:04 PM UTC

   Impact Summary Starting at 26 May 2026 17:14 UTC, customers using Lakeflow Spark Declarative Pipelines may experience pipeline start and restart failures. Symptoms Customers may observe: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations Manually stopping and restarting Pipelines is expected to succeed. Current Status Our engineering team is actively investigating the issue and working to identify the cause. We will share more information as it becomes available. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating May 26, 2026, 08:04 PM UTC

   Impact Summary Starting at 26 May 2026 17:14 UTC, customers using Lakeflow Spark Declarative Pipelines may experience pipeline start and restart failures. Symptoms Customers may observe: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations Manually stopping and restarting Pipelines is expected to succeed. Current Status Our engineering team is actively investigating the issue and working to identify the cause. We will share more information as it becomes available. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring May 26, 2026, 09:11 PM UTC

   Impact Summary Between 26 May 2026 17:14 UTC and 26 May 2026 20:53 UTC, customers using Lakeflow Spark Declarative Pipelines may have experienced pipeline start and restart failures. Symptoms Customers may have observed: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations No customer action is required at this time. Current Status A fix has been applied and service has been restored. We are actively monitoring to confirm stability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

6. monitoring May 26, 2026, 09:11 PM UTC

   Impact Summary Between 26 May 2026 17:14 UTC and 26 May 2026 20:53 UTC, customers using Lakeflow Spark Declarative Pipelines may have experienced pipeline start and restart failures. Symptoms Customers may have observed: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations No customer action is required at this time. Current Status A fix has been applied and service has been restored. We are actively monitoring to confirm stability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

7. resolved May 26, 2026, 10:11 PM UTC

   Impact Summary Between 26 May 2026 17:14 UTC and 26 May 2026 20:53 UTC, customers using Lakeflow Spark Declarative Pipelines experienced pipeline start and restart failures. Symptoms Customers may have observed: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Current Status This incident has been fully resolved as of 26 May 2026 20:53 UTC. We apologize for the disruption. If you require further details about this incident, please submit an Azure support ticket. Next Update No further updates are planned for this incident. 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

Read the full incident report →

Started May 21, 2026, 06:55 AM UTC· resolved May 21, 2026, 09:56 AM UTC

1. investigating May 21, 2026, 06:55 AM UTC

   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.

2. investigating May 21, 2026, 06:56 AM UTC

   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.

3. investigating May 21, 2026, 06:56 AM UTC

   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.

4. identified May 21, 2026, 08:08 AM UTC

   Starting at approximately 06:07 UTC on May 21, 2026, a subset of customers using Azure Databricks may be experiencing errors or failures when launching or running workloads on Classic Compute, Serverless Compute, and Jobs. Affected customers may observe cluster start failures, job run failures, or degraded availability across these services. Symptoms • Cluster launches failing with errors when attempting to start Classic Compute or Serverless Compute workloads • Job runs failing or not completing due to compute provisioning errors • Degraded availability or errors when starting or scaling compute resources Recommendations No customer action is required at this time. Current Status We have identified the cause of degraded availability affecting Classic Compute, Serverless Compute, and Jobs, and are monitoring recovery across all impacted services. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. monitoring May 21, 2026, 08:19 AM UTC

   Between 06:07 UTC and 07:05 UTC on May 21, 2026, a subset of customers using Azure Databricks may have experienced degraded availability, cluster launch failures, or job run failures affecting Classic Compute, Serverless Compute, and Jobs. Serverless Compute began recovering earlier, with availability confirmed restored by approximately 06:35 UTC, while Classic Compute was fully mitigated by 07:05 UTC. Symptoms • Cluster launches failed or returned errors when attempting to start Classic Compute or Serverless Compute workloads • Job runs failed or did not complete successfully due to compute provisioning errors • Degraded availability or timeouts when attempting to start or scale compute resources 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.

6. monitoring May 21, 2026, 08:19 AM UTC

   Between 06:07 UTC and 07:05 UTC on May 21, 2026, a subset of customers using Azure Databricks may have experienced degraded availability, cluster launch failures, or job run failures affecting Classic Compute, Serverless Compute, and Jobs. Serverless Compute began recovering earlier, with availability confirmed restored by approximately 06:35 UTC, while Classic Compute was fully mitigated by 07:05 UTC. Symptoms • Cluster launches failed or returned errors when attempting to start Classic Compute or Serverless Compute workloads • Job runs failed or did not complete successfully due to compute provisioning errors • Degraded availability or timeouts when attempting to start or scale compute resources 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.

7. resolved May 21, 2026, 09:56 AM UTC

   Between 06:07 UTC and 07:05 UTC on May 21, 2026, a subset of customers using Azure Databricks may have experienced degraded availability, cluster launch failures, or job run failures affecting Classic Compute, Serverless Compute, and Jobs. Serverless Compute began recovering earlier, with availability confirmed restored by approximately 06:35 UTC, while Classic Compute was fully mitigated by 07:05 UTC. Symptoms • Cluster launches failed or returned errors when attempting to start Classic Compute or Serverless Compute workloads • Job runs failed or did not complete successfully due to compute provisioning errors • Degraded availability or timeouts when attempting to start or scale compute resources Recommendations No customer action is required at this time. Current Status This incident has been fully resolved as of 21 May 2026 07:05 UTC We apologize for the disruption. 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

Read the full incident report →