01/23/2026
If you experienced issues with Outlook, Teams, or other Microsoft 365 tools this week, you weren’t alone.
Over the past two days (January 22–23, 2026), Microsoft 365 services across North America were hit with widespread disruptions. Multiple news outlets reported that a portion of Microsoft’s service infrastructure in the region wasn’t processing traffic correctly, causing load‑balancing failures across core apps like Outlook, Exchange Online, Teams, SharePoint/OneDrive search, Microsoft Defender, and Purview.
At the height of the outage, tens of thousands of users lost the ability to send or receive email, access files, hold meetings, or view their administrative/security dashboards. Downdetector (a real‑time outage monitoring platform) recorded more than 15,000–16,000 outage reports during peak hours on January 22.
What happened?
Microsoft traced the issue to an infrastructure component in North America that wasn’t handling traffic as expected. Their initial repair attempts even caused additional imbalances before engineers were able to begin restoring services and redirecting traffic to healthier infrastructure.
Where things stand now:
Microsoft has stated that the core impact has been resolved and that services have largely returned to normal, though many users are still seeing issues, and may still see intermittent hiccups as load balancing continues to settle.
What to Expect in the Near Term:
- Residual instability is possible. Some users may still face slow email delivery, brief connection drops, or admin portal errors while the environment finalizes recovery.
- More updates from Microsoft. Their status page and feed (Microsoft’s official public status channel on X) continue to post refinements and adjustments as they complete the stabilization process.
- No indication of a security breach. All reporting points to an internal infrastructure issue, not an external attack.
What you should do if your apps aren’t working yet:
- Restart Outlook/Teams or sign out and back in — this forces a fresh connection to working infrastructure.
- Check your organization’s message center or Microsoft’s status page for ongoing updates (and avoid assuming the issue is local to your device or network).
- Communicate with your team. Let colleagues know that any delays in email or Teams responsiveness may still be related to the outage.
- Avoid making configuration changes (DNS, MX records, Microsoft admin center settings) unless absolutely necessary, as instability on Microsoft’s side can make troubleshooting misleading.
- Document any business impact. If your organization needs to review SLAs or implement continuity plans, having a record helps.
- Check with your MSP to ensure consistent messaging similar to the points above And have them enable alternative applications if critical staff or deadlines are at risk of not being adequately supported.