Microsoft Teams users across the globe found themselves in a state of digital limbo on Wednesday, June 17, 2026, as presence statuses failed to update correctly, leaving contacts stuck on offline or away despite active usage. The disruption, which primarily hit during the critical morning work window, sparked a rapid spike on outage monitoring platforms and flooded social media with complaints.
Downdetector, the popular real-time outage tracker, recorded a sharp surge in problem reports starting around 9:15 AM Eastern Time, with the tally reaching 226 user-submitted issues by late morning. The majority of affected users cited presence indication failures—the little green or yellow dots that signal whether a colleague is available—as the main culprit, rendering Teams a guessing game for anyone trying to reach a coworker quickly.
What Broke: Presence Isn’t Just Cosmetic
The presence feature in Microsoft Teams is far more than a decorative icon. It underpins real-time collaboration by showing whether a user is available, busy, in a meeting, or offline. When it breaks, the entire communication flow of an organization can grind to a halt. Users reported seeing colleagues permanently marked as “Offline” or “Away,” even when they were actively chatting in channels or sending messages. Others experienced erratic flipping between statuses, making it impossible to trust the displayed availability.
“My entire team looked like ghosts on Teams this morning,” said one user on a community forum. “We had to resort to text messages to figure out who was actually working.” The outage seemed to affect both desktop and mobile clients, though some web app users reported fewer issues—a pattern that often points to a backend service misconfiguration rather than a client-side bug.
Microsoft’s service health dashboard did not immediately reflect a formal incident report, but the volume of external reports left little doubt about a widespread problem. The outage tracking site DownDetector showed the most reported problems in the “Presence” category, followed by “Messaging” and “Login” issues—the latter likely secondary symptoms as users tried to sign out and back in to fix the glitch.
A Morning of Confusion and Workarounds
By 10:30 AM ET, IT administrators began advising users to rely on alternative communication methods, including email and direct Teams messages, which still functioned for many despite the presence display failure. Some organizations switched to emergency VoIP lines or reverted to Slack or Webex if they had backup contracts in place.
The outage’s timing magnified its impact. Mid-morning on a Wednesday is peak collaboration time for many global teams, with back-to-back meetings and deadline-driven projects. For businesses that depend on Teams for client calls and vendor coordination, even a partial outage translated into missed connections and delayed decisions.
Microsoft has not yet issued a statement on the root cause, but unofficial signals suggest a possible configuration update to the presence service that rolled out earlier in the day. Presence in Teams is powered by a combination of machine learning and real-time activity tracking, and such systems can sometimes produce a cascade of errors if a single component misbehaves. Past comparable incidents with other communication platforms have been tied to expired certificates, database timeouts, or load balancer failures.
The Ripple Effect on Remote and Hybrid Work
The incident underscores how deeply embedded Microsoft Teams has become in modern work infrastructure. With over 320 million monthly active users, any degradation in its core features carries immediate business consequences. Remote workers, who rely on presence status to gauge when to reach out to distributed teams, were particularly hindered.
“Presence is the new handshake,” said an IT consultant specializing in Microsoft 365 deployments. “When it stops working, it’s like walking into an office and not being able to tell who is at their desk.” The psychological impact on trust and workflow can be significant, as teams lose the ability to quickly assess who is approachable.
For now, users and administrators are awaiting Microsoft’s post-incident review. The company typically publishes a Preliminary Root Cause Analysis (PRCA) within hours of major service incidents, followed by a detailed Incident Post-Mortem within five business days. These reports often reveal surprising triggers for large-scale failures—ranging from a single misconfigured network switch to a flawed feature flag rollout.
Advice for Affected Organizations
While Microsoft works on a fix, IT teams have several levers to mitigate the disruption. The first is to push out a notification via email or an intranet post, advising staff of the issue and suggesting workarounds. Some organizations have found that switching users to the Teams web app or forcing a client cache clear can restore presence temporarily, though this is not a guaranteed solution.
If the outage persists, administrators can check the Microsoft 365 admin center for official updates and consider enabling the “Notify me about outages” toggle to receive real-time alerts. Microsoft’s service health dashboard will display an incident ID once the company acknowledges the problem—a signal that engineers are actively engaged. In the meantime, affected companies might review their business continuity plans and ensure that alternative collaboration tools are listed in employee handbooks for such scenarios.
Looking Ahead: Resilience in a Single-Vendor World
This outage is a stark reminder of the risks inherent in relying on a single platform for all communications. While Microsoft Teams offers seamless integration with the broader Microsoft 365 suite, a central failure like a presence glitch can ripple across the entire productivity stack. Organizations may want to evaluate multi-vendor strategies for real-time communication, even if only as a failover for critical downtime.
As of this writing, Microsoft’s status page still shows a green checkmark for Teams, but the wave of user reports suggests that the issue may not yet be fully recognized or resolved. We will continue to monitor the situation and update this article when more information becomes available.
In the meantime, users can contribute to the collective troubleshooting by filing reports on Downdetector or using the “Report a problem” feature in the Teams client, which provides diagnostic data directly to Microsoft’s engineering teams. For the millions of office workers glued to their Teams screens this morning, a simple green dot never felt so valuable.