Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Microsoft Teams Outage History

Every past Microsoft Teams outage tracked by IsDown, with detection times, duration, and resolution details.

There were 10 Microsoft Teams outages since October 2025. The 10 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major April 28, 2026

April 2026: Some users are unable to search, chat or call users in Microsoft Teams Free

Detected Apr 28, 2026 10:27 AM EDT · Resolved May 20, 2026 12:22 PM EDT · Duration 22 days

Microsoft Teams Free experienced a major outage lasting approximately 22 days where new users who signed up during the incident window were unable to search for other users, send chats, or make calls due to a backend deployment issue that caused them to bypass required onboarding steps. The problem resulted in affected user profiles appearing as "Unknown users" to others and left accounts in an incomplete state that prevented normal functionality. Microsoft deployed a fix after extensive validation and gradually rolled it out to the affected environment, with monitoring to ensure complete resolution.

Major March 18, 2026

March 2026: Users may intermittently be unable to join meetings or access Microsoft Teams Free for Windows

Detected Mar 18, 2026 2:53 PM EDT · Resolved Mar 20, 2026 2:12 PM EDT · Duration 2 days

A Windows update introduced a regression that caused Microsoft Teams Free users to intermittently be unable to join meetings or access the service, with users seeing authentication error messages stating "We couldn't authenticate you, This could be due to a device or network problem, or Teams could be experiencing a Technical issue." The issue affected multiple Windows versions (25H2, 24H2, 23H2, and 22H2) and lasted 47.3 hours. Microsoft developed a fix to address the regression after determining that configuration changes were not viable, while users could temporarily resolve the issue by restarting their computers.