More than 4,500 users flooded Downdetector on Wednesday morning as Microsoft Teams suffered a widespread presence-status failure, leaving workers uncertain whether colleagues were actually online. The glitch, which peaked at 10:23 a.m. ET, caused the app’s telltale green dot—the universal signal for “available”—to lie to users across the globe, showing individuals as offline when they were active, or painting entire teams as green when they were, in fact, away.

The incident quickly became the top trending topic on IT help desks and social media, with hashtags like #TeamsDown and #GreenDotLies gaining traction. For a platform that has become the digital watercooler for over 300 million monthly active users, the presence breakdown struck at the heart of remote collaboration: the ability to know if someone is reachable.

Incident Overview

Reports began surfacing around 9:00 a.m. ET, with users noticing that colleague statuses appeared frozen or contradictory. By 10:23 a.m., Downdetector had logged 4,523 reports, and the number continued to climb throughout the late morning. The issue was not limited to a single region; complaints poured in from North America, Europe, and parts of Asia-Pacific.

Users described a range of symptoms: the green “Available” dot showed for people who were clearly in meetings or offline, the yellow “Away” status stuck on active users, and the “Offline” label appearing for team members who were actively chatting. One frustrated IT manager on a Windows-focused forum wrote, “I just got a frantic call from a VP who thought half her team was no-call-no-show—turns out they were all online but invisible. This is a nightmare for distributed teams.”

Microsoft’s own Service Health Dashboard initially showed no alerts, but within an hour, the company acknowledged the problem via its @MSFT365Status Twitter account: “We’re investigating an issue impacting Microsoft Teams presence status. Users may see inaccurate availability indicators across Teams clients. More details to follow under TM123456.” The lack of immediate transparency drew criticism, as many organizations had to rely on third-party outage trackers like Downdetector before Microsoft confirmed the incident.

User Impact and Reactions

The presence glitch eroded trust in one of Teams’ most basic features. For professionals who manage distributed teams, the green dot is a quick visual cue that eliminates the need for constant check-ins like “are you there?” When that cue fails, communication loops break down.

“I wasted 15 minutes waiting for a colleague to reply, only to find out later she was online the whole time and thought I was away,” said Mark Chen, a product designer in Seattle. “It’s not just an inconvenience—when deadlines are tight, delays like that cascade.”

In many organizations, the false offline status meant that automatic call routing and queue systems that rely on presence data also misfired. Contact center agents who were actively available appeared as “Offline,” causing an unbalanced distribution of calls and longer wait times for customers. One managed service provider reported a 30% spike in unanswered internal calls during the outage window.

The incident also highlighted the psychological reliance on presence indicators. Research from Microsoft itself has shown that visibility into colleagues’ availability reduces the cognitive load of remote work. When that visibility evaporates, workers experience a phenomenon known as “collaboration anxiety”—the stress of not knowing when or how to engage teammates. Several users echoed this sentiment on social media, describing a feeling of isolation despite being virtually surrounded by a fully staffed org chart.

Microsoft’s Response and Resolution

Microsoft’s engineering team traced the issue to a configuration change in the backend service that processes presence signals. The company said in a preliminary incident report that a recent update intended to improve presence accuracy for users with multiple endpoints inadvertently introduced a race condition that caused stale or conflicting states to persist.

By 1:30 p.m. ET, Microsoft had deployed a fix to its presence aggregation service, and by 3:00 p.m. the company declared the incident mitigated. However, some users reported residual issues well into the evening, requiring them to manually toggle their status or restart their Teams clients to force a refresh.

“We understand the critical nature of accurate presence information for real-time collaboration,” Microsoft stated in a follow-up tweet. “We are conducting a full root-cause analysis and will publish a Post-Incident Review within 72 hours to share our findings and preventive measures.”

IT administrators were advised to clear the Teams client cache or run the “Microsoft Teams diagnostic” tool in the Microsoft 365 admin center to speed recovery for affected users. The Microsoft 365 Service Health entry TM123456 provided ongoing updates, though many admins noted the lag between the initial problem and official acknowledgment.

The Technology Behind Presence

Understanding why this glitch was so disruptive requires a look under the hood. Microsoft Teams presence is not a simple binary toggle; it’s a sophisticated aggregation of signals from multiple sources: user activity in Teams (typing, mouse movements), calendar data from Exchange Online, call state from Azure Communication Services, and manual status overrides. All these signals are processed by the “Unified Presence Service,” a cloud-based component that reconciles conflicts and publishes the final presence state to every client connected to the user’s account.

The service uses a variety of heuristics. For example, if a user has a meeting scheduled in Outlook, their presence should automatically shift to “In a meeting” at the start time. If they’re actively typing in a Teams chat, that overrides idle timers. The system must also handle multiple endpoints—a user logged into Teams on a Windows desktop, a mobile phone, and a web browser simultaneously—by selecting the most active endpoint as the primary presence source.

When that reconciliation logic fails, as it did on June 17, the cascading effects are immediate: statuses across the organization become unreliable. The race condition Microsoft described likely caused the service to favor an outdated or inactive endpoint’s signal over the active one, freezing presence in a past state. Because presence data is cached client-side for performance, the stale information persisted even after the backend issue was resolved, hence the recommendation to clear caches.

A History of Teams Outages

This is not the first time Teams has stumbled on its march to enterprise dominance. Since its launch in 2017, the platform has experienced several high-profile outages:

  • March 2020: A global outage lasting nearly two hours occurred just as lockdowns drove millions to remote work. Microsoft blamed a DNS misconfiguration.
  • July 2023: Message delivery delays and authentication issues impacted users for several hours due to a failed database update.
  • January 2024: A five-hour disruption in Europe and the Middle East stemmed from a surge in certificate expiration that broke call routing.
  • November 2025: Presence and chat functions flickered for a day due to a capacity bottleneck in the notification pipeline.

Compared to those incidents, the June 17 presence glitch was relatively short-lived but particularly insidious because it provided false signal rather than no signal—misleading users into making incorrect assumptions about availability. This “silent failure” mode is harder to detect immediately because the app otherwise appears functional.

Best Practices for IT Admins During Outages

The incident serves as a reminder that even cloud-native platforms are fallible. While IT teams cannot prevent a Microsoft-side issue, they can adopt strategies to minimize disruption:

  • Establish Communication Channels: Have a predefined, out-of-band communication method (email distribution lists, SMS alerts, or an alternate messaging app) to notify staff of known outages and workarounds.
  • Monitor Service Health Proactively: Use tools like the Microsoft 365 Admin Center, Downdetector, and Microsoft’s Graph API service health endpoints to detect issues early.
  • Prepare Client-Side Fixes: Document steps for clearing the Teams cache, restarting the client, and using the web app as a fallback. Share these guides with your service desk.
  • Leverage Direct Routing for Calls: If presence impacts telephony, ensure your direct routing configuration can bypass Teams presence for call routing during declared outages.
  • Advocate for Transparency: Encourage your Microsoft account team to prioritize rapid notification of incidents. In this case, user reports preceded official acknowledgment by over an hour.

Many organizations have also begun building internal dashboards that aggregate presence data from alternative sources, such as badge-in systems or VPN logs, to cross-check Teams status during critical periods. While heavy-handed, such measures underscore the mission-critical nature of presence accuracy.

The Fragile Collaboration Stack

Teams’ presence glitch is more than a temporary annoyance; it’s a symptom of a broader vulnerability in the modern collaboration stack. As organizations replace physical office cues with digital equivalents, any reliability gap sends shockwaves through daily workflows. The green dot has become the virtual equivalent of seeing someone at their desk—when that indicator malfunctions, the entire premise of remote availability crumbles.

Microsoft has been investing heavily in the intelligent workplace concept, where AI-driven insights (such as Viva Insights) depend on accurate presence data to generate productivity recommendations. If the underlying signal is untrustworthy, the AI’s utility is compromised. This outage may accelerate calls for a more resilient, decentralized presence model—perhaps using blockchain-like consensus or peer-to-peer verification—to prevent a single backend misconfiguration from taking down the entire system.

In the short term, however, the onus is on Microsoft to shore up its change management and deployment practices. The company has historically struggled with the dual mandate of rapid innovation and rock-solid stability. For the hundreds of millions of Teams users who rely on the little green dot to navigate their workday, the false signal was a stark reminder that what appears simple is often the most fragile part of the system.

As remote and hybrid work patterns solidify, the expectation for always-accurate presence will only intensify. Microsoft’s next Post-Incident Review will be scrutinized not just for what went wrong, but for how the company plans to prevent a repeat. Until then, many users will likely give that green dot a skeptical squint before hitting “call.”