Microsoft users encountered several problems when attempting to access M365, Azure, GitHub, and other online services; the vendor attributed these problems on a “networking configuration error.”
Just after 6 p.m. AEDT, the problems started to show (7am UTC). At 9.35am UTC, Microsoft asserted that network connectivity has been restored.
Teams, Exchange Online, Outlook, SharePoint Online, OneDrive for Business, PowerBI, Microsoft 365 Admin Center, and Microsoft Graph, according to a status advisory, were either unavailable or inaccessible for the whole 2.5-hour period.
Issues with Azure Networking were reinforced by a different advisory, which made it difficult for customers to access a variety of Azure services.
Another GitHub status update mentioned “degraded performance” in relation to a number of applications and services, including Actions, Codespaces, API Requests, and Copilot.
Microsoft claimed to have found what it thought to be the underlying problem.
The firm warned that while trying to connect to Azure resources across various regions and other Microsoft services, customers “may experience issues with networking connectivity, manifesting as network delay and/or timeouts.”
“We have found that the network connectivity problem affects devices connected to the Microsoft wide area network (WAN).
“This affects connections made by clients to Azure over the internet, as well as connections made by services in data centres and through ExpressRoute.
The problem is having an impact in waves, with peaks happening roughly every 30 minutes.
Microsoft claimed that it had “taken steps to roll back this update” after identifying “a recent WAN update as the likely underlying cause.”
