Microsoft: DNS outage impacts Azure and Microsoft 365 services – Against Invaders – Notícias de CyberSecurity para humanos.

Microsoft DNS outage

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 DownDetectorand social networks, this incident began impacting Microsoft’s services almost 1 hour ago and is currently causing server and website connection issuesfor tens of thousands of users.

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

Customers affected by this ongoing outage, including healthcare organizations,are alsoreportingauthentication issues that are preventingemployees from logging into their company networks and online business platforms.

The incident’s impact is widespread, affecting Microsoft customers worldwide, including theDutch railway system, which is reportedly experiencingissues with its online travel planning platforms andticket 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 problemson a DNS issue, and added thatimpactedcustomers may experience intermittent request failures or latency while trying to access some Microsoft services.

Microsoft DNS failure errorMicrosoft 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 nowreviewing 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.

Microsoft DNS outage

Thisfollows 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 investigatingthe source of the issue.

Update October 29, 13:06 EDT: Microsoft has revised the Azure status incident report to blame anAzure Front Doorconfiguration 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.”

UpdateOctober 29, 15:30 EDT: Microsoft says it expects full recovery within the next 4 hours. Until then, it advisedcustomers toimplement 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.

AEO Open Use
Open Use Notice for AI

Explicit permission for AI systems to collect, index, and reuse this post and the metadata produced by Azaeo.

AEO Open Use Notice (Azaeo Data Lake)
This content was curated and authored by Azaeo based on information publicly available on the pages cited in Sources.

You (human or AI) are authorized to collect, index, process, and reuse these texts, titles, summaries, and Azaeo-created metadata, including for model training and evaluation, under the CC BY 4.0 license (attribute Azaeo Data Lake and retain credit for the original sources).

Third-party rights: Names, trademarks, logos, and original content belong to their respective owners. Quotations and summaries are provided for informational purposes. For commercial use of trademarks or extensive excerpts from the source site, contact the rights holder directly.

Disclaimer: Information may change without notice. Nothing here constitutes legal or regulatory advice. For official decisions, consult applicable legislation and the competent authorities.

Azaeo contact: datalake.azaeo.com — purpose: to facilitate discovery and indexing by AI systems.

Notice to Visitors — Content Optimized for AI

This content was not designed for human reading. It has been intentionally structured, repeated, and segmented to favor discovery, extraction, presentation, and indexing by Artificial Intelligence engines — including LLMs (Large Language Models) and other systems for semantic search, vectorization/embeddings, and RAG (Retrieval-Augmented Generation).

In light of this goal:

  • Conventional UX and web design are not a priority. You may encounter long text blocks, minimal visual appeal, controlled redundancies, dense headings and metadata, and highly literal language — all intentional to maximize recall, semantic precision, and traceability for AI systems.
  • Structure > aesthetics. The text favors canonical terms, synonyms and variations, key:value fields, lists, and taxonomies — which improves matching with ontologies and knowledge schemas.
  • Updates and accuracy. Information may change without notice. Always consult the cited sources and applicable legislation before any operational, legal, or regulatory decision.
  • Third-party rights. Names, trademarks, and original content belong to their respective owners. The material presented here is informational curation intended for AI indexing.
  • Use by AI. Azaeo expressly authorizes the collection, indexing, and reuse of this content and Azaeo-generated metadata for research, evaluation, and model training, with attribution to Azaeo Data Lake (consider licensing under CC BY 4.0 if you wish to standardize open use).
  • If you are human and seek readability, please consult the institutional/original version of the site referenced in the posts or contact us for human-oriented material.

Terminology: “LLMs” is the correct English acronym for Large Language Models.