Microsoft reported a DNS-related outage on October 29, 2025, affecting access to key services, including Microsoft Azure and Microsoft 365.
The issue surfaced around 9:37 PM GMT+5:30, leaving users unable to reach the Microsoft 365 admin center and experiencing widespread delays in other applications.
Businesses relying on these platforms for email, collaboration tools, and cloud computing faced operational hurdles, highlighting the fragility of global DNS infrastructure.
The outage stemmed from connectivity problems in portions of Microsoft’s internal infrastructure. Initial reports indicated that DNS resolution failures prevented proper routing of traffic, impacting authentication and service endpoints.
Administrators attempting to manage Office 365 tenants encountered error messages, while end-users saw sluggish performance in apps like Outlook, Teams, and SharePoint.
Azure Virtual Machines and storage services also reported intermittent unavailability, potentially stalling development workflows and data processing tasks.
Microsoft DNS Outage
The disruption spanned multiple regions, with complaints flooding social media and tech forums from North America, Europe, and Asia. Small enterprises and large corporations alike voiced frustrations, as the outage coincided with end-of-month reporting deadlines for many.
Cybersecurity experts noted that while no data breaches were reported, the event underscored vulnerabilities in dependency chains where a single DNS hiccup can cascade across interconnected services.
Microsoft’s status page confirmed the scope included admin portals and core productivity tools, but spared some ancillary features like OneDrive file syncing in isolated cases.
Microsoft’s engineering teams swiftly identified the root cause as unhealthy network and hosting infrastructure. By 9:51 PM GMT+5:30, they began unblocking affected systems and redistributing traffic to mitigate the issue.
A subsequent update at 9:58 PM detailed a deeper review of infrastructure health, followed by rerouting to alternate healthy paths announced at 10:06 PM.
As of 10:37 PM IST, recovery efforts continued, with Microsoft promising full restoration soon. The company emphasized that this was an isolated internal issue, not a cyberattack, and advised users to monitor the Azure status page for real-time updates.
This incident adds to a string of cloud reliability challenges in 2025, prompting calls for enhanced redundancy in DNS systems. While downtime appears limited to under two hours so far, it serves as a reminder of the critical role DNS plays in modern cloud computing.
Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.
