Microsoft is suffering an ongoing DNS outage affecting customers worldwide, preventing them from logging into company networks and accessing Microsoft Azure and Microsoft 365 services.

According to reports on DownDetector and social networks, this incident began impacting Microsoft’s services almost 1 hour ago and is currently causing server and website connection issues for tens of thousands of users.

Some of those affected are having issues accessing the Intune and Azure portals, as well as the Exchange admin center, while others report that Microsoft’s Azure Front Door Content Delivery Network (CDN) service is also down.

Customers affected by this ongoing outage, including healthcare organizations, are also reporting authentication issues that are preventing employees from logging into their company networks and online business platforms.

The incident’s impact is widespread, affecting Microsoft customers worldwide, including the Dutch railway system, which is reportedly experiencing issues with its online travel planning platforms and ticket machines.

“We’re aware that the Provider Portal login is currently unavailable due to a Microsoft outage affecting authentication services,” one affected customer says. “Our team is actively working to restore anything impacted and monitoring progress closely as Microsoft Azure systems recover.”

At the moment, Microsoft is blaming these ongoing service access problems on a DNS issue, and added that impacted customers may experience intermittent request failures or latency while trying to access some Microsoft services.

“Starting at approximately 16:00 UTC, we began experiencing DNS issues resulting in availability degradation of some services. Customers may experience issues accessing the Azure Portal. We have taken action that is expected to address the portal access issues here shortly,” Microsoft said on the Azure status page.

“Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services. Additionally, admins are reporting issues when attempting to access some Microsoft Purview and Microsoft Intune functions. Users are also seeing issues with add-ins and network connectivity in Outlook,” it added in a separate service alert (MO1181369) on the Microsoft 365 admin portal.

Microsoft directed users to find more information about this outage on the status.cloud.microsoft page; however, like many of the company’s online platforms and services, this page is also down.

Microsoft is now reviewing all reports of issues affecting Microsoft Azure and Microsoft 365 services, including those related to problems accessing the Microsoft 365 admin center and other services.

“We’re reviewing corresponding service telemetry to isolate the cause of the issue and determine our next troubleshooting steps,” Microsoft said.

This follows a massive AWS (Amazon Web Services) outage last week that brought down millions of online services and websites due to a major DNS failure.

Update October 29, 12:59 EDT: Microsoft confirmed that its Azure Front Door CDN service and the Azure Portal are down and advised customers to use programmatic methods (PowerShell, CLI, etc.) to access resources if they are unable to access the portal directly.

“We are actively assessing failover options of internal services from our AFD infrastructure. Our investigation into the contributing factors and additional recovery workstreams continues,” it said in an Azure status update.

According to a separate Microsoft 365 admin center update, the company is also rerouting affected traffic to alternate healthy infrastructure as a short-term solution while investigating the source of the issue.

Update October 29, 13:06 EDT: Microsoft has revised the Azure status incident report to blame an Azure Front Door configuration change for the outage.

“Starting at approximately 16:00 UTC, we began experiencing Azure Front Door issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue,” it said.

“We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state.”

Update October 29, 15:30 EDT: Microsoft says it expects full recovery within the next 4 hours. Until then, it advised customers to implement failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers by following the guidance available HERE.

“This means we expect recovery to happen by 23:20 UTC on 29 October 2025. We will provide another update on our progress within two hours, or sooner if warranted,” Microsoft stated.