Microsoft on Friday warned Azure cloud service users may continue to experience "intermittent errors," blaming the problem on a US East regional networking service configuration change.

The outage, which began around 2200 UTC on January 8, was "limited to a single zone in the East US 2 region," according to Redmond. "A network configuration issue in one of the zones resulted in three of the Storage partitions going unhealthy," reads an [1]Azure status alert .

As a result, customers experienced "intermittent Virtual Machine connectivity issues, failures in allocating resources or communicating with resources in the region."

[2]

Affected services include Azure Databricks, Azure Container Apps, Azure Function Apps, Azure App Service, SQL Managed Instances, Azure Data Factory, Azure Container Instances, PowerBI, VMSS, PostgreSQL flexible servers, and others, plus customers using resources with Private Endpoint Network Security Groups to communicate with other services.

[3]Microsoft investigating 365 Office activation gremlin

[4]Major ISP bungles settings, causing Microsoft 365, Azure outage

[5]Can't get Minecraft, MongoDB Cloud, others to work today? Blame that Azure outage

[6]Microsoft's Azure networking takes a worldwide tumble

In an attempt to remediate the problem, Microsoft said it rerouted traffic away from the affected zone, "which brought some relief to the non-zonal services." However, as of Friday morning, "services that sent zonal requests to the impacted zone remained unhealthy."

As of 1639 UTC on January 10, all three of the impacted partitions had been brought back online, and Microsoft had patched the Private Link issues, noting that all Private Link dependent services were up and running.

[7]

While Redmond noted "significant signs of recovery," it added that "individual services are still recovering, and some customers may continue to see intermittent errors and degraded performance" while the recovery continues. It did not provide an expected time or date for full recovery.

The tech giant promised to provide more details on its progress in hourly updates, and urged customers to execute disaster recovery for their impacted cloud services. ®

Get our [8]Tech Resources



[1] https://azure.status.microsoft/en-gb/status

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Z4GmjoV9VxBt4bCF0GoJegAAAII&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://www.theregister.com/2024/12/20/microsoft_office_activation_issue/

[4] https://www.theregister.com/2024/09/12/att_microsoft_365_outage/

[5] https://www.theregister.com/2024/07/30/azure_outage_impact/

[6] https://www.theregister.com/2024/07/30/microsofts_azure_portal_outage/

[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Z4GmjoV9VxBt4bCF0GoJegAAAII&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[8] https://whitepapers.theregister.com/