Microsoft 365 users around the world are struggling to access Outlook, Teams, and other services as Microsoft deals with a major outage.

Microsoft first reported problems with Exchange Online mailboxes in the Americas at around 10:54 PM PKT on Thursday. Shortly after, the company confirmed that the issue could affect Microsoft 365 users in any region.

Which Services Are Affected

According to the Microsoft 365 status page, the potentially affected services include:

  • Exchange Online (Outlook email)
  • Microsoft Teams
  • SharePoint Online
  • Microsoft 365 Copilot
  • Microsoft Defender XDR

Users may be unable to open their mailboxes through Outlook on the web, mobile email apps that use Exchange ActiveSync, and other connection methods.

What Caused the Outage

Microsoft said a portion of its infrastructure is facing elevated load across multiple regions, which is likely causing the connection errors. It is also reviewing an unexpected increase in a specific type of service traffic to see whether it added to the problem.

The company said it is "aggressively pursuing all pathways to reduce impact." It has paused all deployments, spread connection traffic across its worldwide infrastructure, moved more traffic away from the affected systems, and started restarting affected servers. It has not said how many users are affected or when service will be fully restored.

Earlier on Thursday, Microsoft also dealt with a separate Teams disruption in North America, which it said was fully resolved by around 10:09 PM PKT.

The outage comes weeks after a Google Cloud outage disrupted banks, courts, and businesses. Microsoft is sharing updates in the Microsoft 365 admin center under incident EX1550543.

Background: Why Microsoft 365 Outages Matter

Microsoft 365 is a cloud-based suite that powers email, collaboration, file storage and AI-driven assistance for millions of enterprises, schools and individual users. Exchange Online, the backbone of Outlook, handles billions of messages daily. Teams has become the default platform for video meetings, chat and remote work, especially after the pandemic accelerated digital transformation. SharePoint Online stores documents and intranet sites for organisations of all sizes, while Microsoft 365 Copilot, introduced in early 2024, adds generative AI to write drafts, summarise threads and automate routine tasks. Defender XDR provides integrated threat detection across Microsoft's security stack.

Because these services are delivered from a shared, multi-tenant cloud, a failure in one data-center or a spike in traffic can ripple across the entire ecosystem. Past incidents, such as the 2022 Exchange Online outage that lasted several hours and the 2023 Teams regional slowdown, have shown how dependent modern workplaces are on uninterrupted access.

How Microsoft Manages Service Health

Microsoft operates a global network of data centres grouped into regions (for example, US East, Europe West, Asia Pacific). Each region contains multiple availability zones, each with redundant power, cooling and networking. Services like Exchange Online are built on a micro-service architecture that automatically balances load across zones.

The company monitors health through the Microsoft 365 admin center, where administrators can see incident IDs, status updates and estimated resolution times. When an issue is detected, the internal Incident Response Team follows a defined playbook: isolate the faulty component, shift traffic to healthy zones, apply patches, and communicate status to customers.

Impact on Different User Groups

Corporate users rely on Outlook for internal and external communication; a prolonged outage can delay decision-making, affect customer service and interrupt supply-chain coordination. Small businesses that use Teams for client calls may lose revenue if meetings cannot be held. Educational institutions that host virtual classrooms on Teams face class cancellations. Developers and IT staff who use SharePoint for code repositories or documentation may be forced to revert to local copies, increasing risk of version drift.

For individual users, the loss of Copilot means AI-assisted drafting in Word, Excel and Teams is unavailable, reducing productivity for tasks such as report generation or email summarisation. Defender XDR users may experience a temporary gap in real-time threat telemetry, though the core security engine continues to run on edge devices.

What Microsoft Is Doing to Resolve the Issue

In its public statement, Microsoft outlined four immediate actions: pausing all new deployments, redistributing traffic across its global network, moving more traffic away from the affected systems, and restarting affected servers. Pausing deployments prevents new code changes from compounding the problem, while traffic redistribution reduces load on overloaded nodes.

The company also said it is reviewing an "unexpected increase in a specific type of service traffic." Such spikes can be caused by automated scripts, a sudden surge in user activity, or a misconfiguration that generates excessive API calls. By analysing telemetry, Microsoft hopes to identify whether the traffic was benign or malicious.

While the exact timeline for full restoration is not provided, Microsoft typically provides hourly updates on the admin centre incident page (EX1550543). Customers are advised to monitor that page, use the Service Health dashboard, and consider enabling fallback email routing or alternate communication channels where possible.

Comparisons with Recent Cloud Outages

The timing of this incident follows a high-profile Google Cloud outage in early March that impacted banks, courts and e-commerce platforms across multiple continents. That event highlighted the systemic risk of relying on a single cloud provider for mission-critical workloads. Industry analysts have called for diversified cloud strategies, including multi-cloud or hybrid-cloud architectures, to mitigate the impact of such disruptions.

Microsoft's response mirrors industry best practices: rapid communication, transparent incident IDs, and technical remediation steps. However, the lack of a public estimate for user impact or restoration time leaves some enterprises uncertain about business continuity planning.

Practical Steps for Users and Administrators

Administrators should log into the Microsoft 365 admin center to track the incident status and follow any recommended mitigation steps. Setting up alternative email routing (for example, forwarding to a secondary mail system) can reduce downtime for critical communications.

End users can try the following while services are degraded:

  • Clear browser cache and try a private/incognito window to rule out local session issues.
  • Use the Outlook desktop client instead of Outlook on the web, as it may retain cached mail.
  • Switch to a mobile device with a different network (cellular vs Wi-Fi) to test connectivity.
  • For Teams, consider using the web version or the mobile app as a fallback.

Organizations with high-availability requirements may explore redundant communication tools, such as Slack or Zoom, as temporary backups.

What to Watch for Next

Microsoft will continue to post updates under incident EX1550543. Key signals to monitor include a change in status from "Investigating" to "Mitigating" and then to "Resolved." Post-mortem reports are typically released within weeks and provide a detailed timeline, root-cause analysis and recommendations for preventing recurrence.

Enterprises should also watch for any follow-up advisories regarding the "specific type of service traffic" that contributed to the overload. If the traffic was identified as malicious, additional security guidance may be issued.

Finally, the broader cloud-services market will likely analyse this outage alongside the recent Google Cloud incident to assess the resilience of the industry's shared-responsibility model.