Several Galaxy accounts are having issues to start clusters on Azure

Several Galaxy accounts are experiencing issues restarting Azure clusters across multiple regions. The team is actively investigating the root cause and working to restore normal operations as quickly as possible.

According to Azure status page https://azure.status.microsoft/en-us/status

"Active - Virtual Machine service management issues - Multiple regions

Impact statement: We are aware of an ongoing issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs). These issues are also causing impact to services with dependencies on these operations, including Azure Arc Enabled Servers, Azure Batch, Azure DevOps, and GitHub. For details on the latter, please see https://www.githubstatus.com. Current status: We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working on mitigation, including updating configuration to restore relevant access permissions. Our next update will be provided by 22:30 UTC, approximately 60 minutes from now.

This message was last updated at 21:35 UTC on 02 February 2026"

Current status from Azure team( https://azure.status.microsoft/en-us/status) : "We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working to mitigate impact, by updating our configuration to restore relevant access permissions. After applying this update in one region, we validated that it mitigates the issues customers were experiencing - we are making good progress applying this same mitigation across all impacted regions, in parallel where possible. We still expect that this will be completed across all impacted regions by approximately 00:00 UTC, approximately one hour from now. Our next update will be provided by then, or sooner if we have progress to share.

This message was last updated at 22:59 UTC on 02 February 2026"

We are continuing to work on a fix for this issue.

This incident has been resolved.