ES-1636144

We are actively investigating an issue with the Databricks service.

Further updates will be provided within the next hour, or as events warrant.

Starting at approximately 16:00 UTC October 29, 2025, customers may experience inability to access Azure Databricks services or run jobs.

The issue has been identified. Please see: https://azure.status.microsoft/en-us/status

We are working with the cloud provider on potential mitigation paths. Further updates will be provided in 1 hour, or as events warrant.

Starting at approximately 16:00 UTC October 29, 2025, customers may experience inability to access Azure Databricks services or run jobs.

The issue has been identified. Please see https://azure.status.microsoft/en-us/status

Many Azure Databricks services have recovered, however clusters and jobs that execute init scripts with dependencies on the packages.microsoft.com repository are failing during the cluster provisioning phase. The failures are due to the ongoing incident affecting Azure Front Door service which is affecting packages.microsoft.com. We recommend switching to alternate mirrors, e.g. archive.ubuntu.com. Note that this will not address all failures because some packages may only be available on packages.microsoft.com

We are working with the cloud provider on potential mitigation paths. Further updates will be provided in 1 hour, or as events warrant.

Starting at approximately 16:00 UTC October 29, 2025, customers may experience inability to access Azure Databricks services or run jobs.

The issue has been identified. Please see https://azure.status.microsoft/en-us/status

Many Azure Databricks services have recovered, however clusters and jobs that execute init scripts with dependencies on packages.microsoft.com repository are failing during the cluster provisioning phase. The failures are due to an ongoing incident affecting Azure Front Door service which is affecting packages.microsoft.com. If you are using packages.microsoft.com for packages that are also hosted on other mirrors (e.g. archive.ubuntu.com), we recommend switching to the other mirrors. At this point there's no mitigation for packages which are only present on packages.microsoft.com, e.g. msodbcsql17 and msodbcsql18.

We are working with the cloud provider on potential mitigation paths. Further updates will be provided in 1 hour, or as events warrant.

Starting at approximately 16:00 UTC October 29, 2025, customers may experience inability to access Azure Databricks services or run jobs.

The issue has been identified. Please see https://azure.status.microsoft/en-us/status

Many Azure Databricks services have recovered, however clusters and jobs that execute init scripts with dependencies on packages.microsoft.com repository are failing during the cluster provisioning phase. The failures are due to an ongoing incident affecting Azure Front Door service which is affecting packages.microsoft.com. If you are using packages.microsoft.com for packages that are also hosted on other mirrors (e.g. archive.ubuntu.com), we recommend switching to the other mirrors. At this point there's no mitigation for packages which are only present on packages.microsoft.com, e.g. msodbcsql17 and msodbcsql18.

We are working with the cloud provider on potential mitigation paths. Further updates will be provided in 1 hour, or as events warrant.

Starting at approximately 16:00 UTC October 29, 2025, customers may experience inability to access Azure Databricks services or run jobs.

The issue has been identified. Please see azure.status.microsoft/en-us/status

As of 17:09 UTC most Azure Databricks services have recovered, however a limited number of clusters and jobs that execute init scripts with dependencies on packages.microsoft.com repository are failing during the cluster provisioning phase. The failures are due to an ongoing incident affecting Azure Front Door service which is affecting packages.microsoft.com. If you are using packages.microsoft.com for packages that are also hosted on other mirrors (e.g. archive.ubuntu.com), we recommend switching to the other mirrors. At this point there's no mitigation for packages which are only present on packages.microsoft.com, e.g. msodbcsql17 and msodbcsql18.

We are working with the cloud provider on potential mitigation paths. Further updates will be provided in 2 hours, or as events warrant.

Starting at approximately 16:00 UTC October 29, 2025, customers may experience inability to access Azure Databricks services or run jobs.

The issue has been identified. Please see azure.status.microsoft/en-us/status

As of 17:09 UTC most Azure Databricks services have recovered, however a limited number of clusters and jobs that execute init scripts with dependencies on packages.microsoft.com repository are failing during the cluster provisioning phase. The failures are due to an ongoing incident affecting Azure Front Door service which is affecting packages.microsoft.com. If you are using packages.microsoft.com for packages that are also hosted on other mirrors (e.g. archive.ubuntu.com), we recommend switching to the other mirrors. At this point there's no mitigation for packages which are only present on packages.microsoft.com, e.g. msodbcsql17 and msodbcsql18.

We are working with the cloud provider on potential mitigation paths. Further updates will be provided in 2 hours, or as events warrant.