ES-2079471

We are actively investigating an issue with the Databricks service.

Next Update

We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI.

Symptoms
• Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources
• 500 errors or failures loading the workspace UI and notebooks
• Failures submitting or running Jobs, and intermittent login issues

Recommendations
No customer action is required at this time.

Current Status
We are actively investigating an incident on the cloud provider affecting Azure Databricks.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI.

Symptoms
• Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources
• 500 errors or failures loading the workspace UI and notebooks
• Failures submitting or running Jobs, and intermittent login issues

Recommendations
No customer action is required at this time.

Current Status
We are actively investigating an incident on the cloud provider affecting Azure Databricks. For additional details, please check https://azure.status.microsoft/

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality due to an underlying network connectivity issue impacting the affected region. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI.

Symptoms
• Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources
• 500 errors or failures loading the workspace UI and notebooks
• Failures submitting or running Jobs, and intermittent login issues

Recommendations
No customer action is required at this time. If feasible, customers with workloads that can be rerouted away from the affected region may see reduced impact until the network issue is resolved.

Current Status
We have identified the issue as a network-related disruption originating with our cloud provider affecting Azure Databricks, and we continue to work closely with the cloud provider to fully resolve it. For further details, please check https://azure.status.microsoft/

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 14:51 UTC on July 23, 2026, customers using Azure Databricks may be experiencing errors or failures affecting Compute, Jobs, Notebooks, and Login functionality due to an underlying network connectivity issue impacting the affected region. Impacted users may see failures when starting compute resources, errors when accessing notebooks, issues submitting or running jobs, and disruptions when logging in or loading the workspace UI.

Symptoms
• Errors or failures when starting Classic Compute or Serverless/Dedicated Compute resources
• 500 errors or failures loading the workspace UI and notebooks
• Failures submitting or running Jobs, and intermittent login issues

Recommendations
No customer action is required at this time. If feasible, customers with workloads that can be rerouted away from the affected region may see reduced impact until the network issue is resolved.

Current Status
We have identified the issue as a network-related disruption originating with our cloud provider affecting Azure Databricks, and 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.