Redazione RHC : 29 October 2025 21:34
A DNS service outage was detected by Microsoft on October 29, 2025, impacting access to critical services such as Microsoft Azure and Microsoft 365. An anomaly was detected at 21:37 GMT+5:30, causing widespread delays in various applications and blocking users from accessing the Microsoft 365 admin area.
According to initial reports, DNS resolution difficulties were hindering proper traffic management, negatively impacting authentication and service endpoints. The reliance on these platforms for email, collaboration, and cloud computing services led to service unavailability issues.
The outage affected numerous regions, sparking widespread complaints on social media and tech forums in North America, Europe, and Asia. Office 365 tenant managers faced errors, while users experienced delays in applications like SharePoint, Teams, and Outlook.
Azure storage services and virtual machines have experienced intermittent outages, which may disrupt development workflows and data processing operations.
Cybersecurity specialists noted that despite the lack of reported data breaches, the event highlighted weaknesses in cloud dependency chains, where a single DNS anomaly can have widespread repercussions across interconnected services.
Microsoft’s status page confirmed that the scope included the admin portals and core productivity tools, but spared some ancillary features like OneDrive file sync in isolated cases.
Microsoft engineering teams quickly identified the root cause of the issue: a malfunctioning network and hosting infrastructure. At 9:51 PM GMT+5:30, they began unblocking the affected systems and redistributing traffic to mitigate the issue.
A subsequent update at 9:58 PM provided details of a more in-depth analysis of the infrastructure’s health, followed by the rerouting to safe alternative routes announced at 10:06 PM.
So, it was an isolated internal issue, not a cyberattack . Recovery efforts were still ongoing as of this writing, and Microsoft urged users to monitor the Azure status page for real-time updates. The company confirmed that recovery efforts were continuing unabated.
In the last few days we have witnessed a series of problems to which this incident is now added; blockages and outages on AWS (as happened a few days ago) or on Azure (as now) easily cause predictable and controllable cascading problems.
Redazione