Thousands of Microsoft Teams users started their Wednesday workday only to discover that the collaboration platform’s status indicator—the green dot that signals availability—had turned into a source of confusion. Instead of accurately reflecting their online presence, the app showed them or their colleagues as offline, away, or simply ‘unknown’ throughout the morning of June 17, 2026.
First reports surfaced around 8:00 AM UTC on social media platforms like X (formerly Twitter) and Reddit, as remote and hybrid workers found themselves unable to determine whether teammates were reachable. The glitch quickly drew the attention of IT administrators, who noted a spike in help desk tickets related to presence malfunctions. Within two hours, the phrase “Teams presence broken” was trending in technology circles, with thousands of posts describing identical symptoms.
How the Presence Glitch Unfolded
Microsoft Teams presence is designed to be an intelligent, automated feature that relies on multiple signals: keyboard and mouse activity, calendar appointments, meeting join status, and manual user settings. Under normal conditions, a user actively typing or in a call will automatically appear as “Available” (green), while idle users transition to “Away” after a period of inactivity. The system also respects out-of-office and “Do not disturb” states, providing a real-time snapshot of a colleague’s availability.
On June 17, however, this logic failed catastrophically. Users who were demonstrably signed into Teams, actively in chat conversations, or presenting in online meetings were displayed to their contacts with a gray “Offline” badge or a yellow “Away” tag. Some saw their own status flicker between offline and busy without any corresponding change in their activity. The issue affected all major platforms—Windows, macOS, iOS, Android, and the web client—indicating a server-side problem rather than a flaw in any specific app version.
Early reports from the U.S. East Coast, Western Europe, and parts of Asia Pacific suggest the incident was global in scope. Downdetector, the third-party outage monitoring site, recorded a sharp uptick in user-submitted problem reports starting at 09:12 AM EDT, with a peak of over 14,000 complaints by noon. The reported problems were overwhelmingly concentrated in the “status” and “presence” categories.
The Ripple Effect on Hybrid Work
For organizations that rely on Teams as their primary communication backbone, the presence failure was more than a minor annoyance. It eroded the real-time visibility that underpins agile workflows. Managers could not see if their direct reports were at their desks; colleagues hesitated to ping someone who appeared offline; urgent messages were delayed because senders assumed recipients were unavailable. In many hybrid environments, where physical “shoulder taps” are a thing of the past, presence is the digital equivalent of an open office door. When that door slams shut without warning, productivity grinds to a halt.
Several enterprise users told Windows News that the outage caused missed deadlines and botched handoffs. “I needed quick sign-off from a legal reviewer who was shown as offline all morning. I eventually walked to her desk only to find her in back-to-back video calls,” said a project manager at a Fortune 500 firm in Chicago. “The whole point of presence is to avoid that kind of waste.”
Educational institutions also felt the sting. Professors conducting online office hours found that students couldn’t see their green status, leading to confusion about whether the session was still on. Some university IT departments sent campus-wide advisories urging people to ignore Teams presence and use email or phone calls for time-sensitive matters.
A Look Under the Hood: What May Have Gone Wrong
While Microsoft has not yet publicly confirmed the root cause, the pattern of the outage points strongly toward a failure in the back-end presence microservice that aggregates and distributes state information. In Microsoft 365’s architecture, the presence service ingests signals from Outlook, Exchange, SharePoint, and endpoint clients, then publishes the consolidated status to all connections in near real time. A disruption in this pipeline can cause stale or incorrect status data to propagate across the ecosystem.
Similar incidents in the past were traced to misconfigurations in Azure Active Directory, deployment of a flawed configuration update, or capacity exhaustion in a regional data center. For instance, a Teams outage in November 2023 saw presence inaccuracies alongside chat delays, and it was ultimately attributed to a routing table error in Microsoft’s networking layer. The June 17 episode, however, appeared to affect only presence—chat messages, meeting audio, and video all functioned normally according to user reports. That isolation suggests the problem lay strictly in the service responsible for state computation and distribution.
Microsoft operates a distributed presence infrastructure with regional failover capabilities. The fact that the incident spanned multiple geographies simultaneously hints at a global configuration change that went awry—perhaps a feature update intended to improve accuracy or reduce latency that inadvertently introduced a regression. Service health notifications, when they appear, will likely cite an “incorrect configuration” or “deployment error.”
User Reactions: A Social Media Storm
The outage triggered an immediate flood of frustrated and often humorous commentary. On X, the hashtag #TeamsOutage garnered over 120,000 mentions in the first three hours. One widely shared post read: “Teams: You are offline. Also Teams: You have 14 unread messages and a meeting in 5 minutes. Make it make sense.” Another user posted a screenshot of their Teams interface displaying a gray dot while simultaneously giving a pop-up notification that they were “currently in a call”—an impossible status combination under normal operation.
IT professionals took to Reddit’s r/sysadmin and the Microsoft Tech Community to swap diagnostic tips. “Our CEO thought half the engineering team had skipped work. The poor VP of engineering had to manually email everyone to prove they were online,” recounted one sysadmin. Others shared workarounds, noting that manually setting status to “Available” via the profile dropdown sometimes stuck but often reverted to offline after a few minutes.
The conversation also revealed a deeper frustration: many users feel that Teams presence has never been entirely reliable. “It’s 2026 and we still can’t trust the little green dot? This is a solved problem for every consumer chat app, but somehow Microsoft can’t get it right in an enterprise product costing us $20 per user per month,” complained a business analyst on LinkedIn.
Microsoft’s Silence and Historical Precedents
At the time of writing—approximately 4:00 PM UTC on June 17—Microsoft had not posted an official incident on its Microsoft 365 Service Health Dashboard, nor had the Microsoft 365 Status Twitter account acknowledged the problem. This lack of communication stoked anxiety among IT admins who depend on the dashboard for automated incident response workflows. Without an advisory, many organizations were left guessing whether the issue was global or limited to their tenant.
Microsoft’s communication protocols for service incidents have been a point of contention for years. While the company has made improvements—such as the introduction of the Service Health Dashboard in the Microsoft 365 admin center and a companion mobile app—initial delays in confirmation remain common during widespread outages. In March 2024, a similar presence glitch affecting only the web client went unacknowledged for nearly five hours before a bulletin appeared. Industry observers attribute these delays to internal triage processes that require gathering telemetry and coordinating across multiple engineering teams before a public statement is released.
Past presence-related outages have typically been resolved within 12 to 24 hours. The November 2023 incident required a full rollback of a configuration change and was mitigated in approximately 8 hours. If the June 17 issue follows a similar trajectory, affected users can expect a gradual return to normal functionality by late evening UTC, with lingering propagation delays in some regions.
Workarounds Emerge as IT Teams Scramble
While waiting for an official fix, users and administrators devised makeshift solutions to keep critical communications moving. The simplest and most effective short-term fix was to have everyone manually set their status to “Available” and then disable automatic presence in settings—though this option is hidden in Teams’ deep settings menu. To find it, users had to navigate to Settings → Privacy → Manage presence and toggle off the “Automatically change my presence” switch. Once disabled, the status remains static until manually changed, effectively bypassing the broken auto-detection.
Another common workaround involved using Outlook Calendar as a proxy for availability. Because Teams integrates presence with calendar data, many teams instructed members to check a colleague’s calendar for a green “Available” bar before initiating a chat or call. While clunky, this approach at least gave some indication of whether a person was in a meeting or free.
For organizations with advanced IT tooling, setting up a temporary chatbot that periodically polled users and broadcast a status list via a channel tab proved effective. One creative admin shared a PowerShell script that used the Teams Graph API to query user activity and override the displayed presence, though this required admin consent and was only suitable for a small subset of power users.
Crucially, none of these workarounds restored the seamless, cross-application presence syncing that teams depend on for real-time coauthoring in Word, Excel, and PowerPoint. In shared documents, the presence dots that indicate who else is editing vanished, leaving collaborators blind to others’ activity. This collateral damage extended the outage’s impact well beyond chat and calling.
The Bigger Picture: Reliability in the Era of Remote Work
The June 17 incident is the latest in a string of high-profile Teams outages that have tested user trust in Microsoft’s cloud infrastructure. As remote work evolves from a temporary measure to a permanent fixture, the expectations for always-on collaboration tools have risen sharply. A presence failure in 2026 is no longer merely an inconvenience; it is a business continuity issue. Enterprises that have invested heavily in Microsoft 365 expect five-nines reliability (99.999% uptime) for core services, and a half-day outage represents a significant breach of that SLA.
Analysts point out that presence, while seemingly simple, is one of the most technically challenging features to get right at scale. It must handle millions of concurrent state changes per second, synchronize them across multiple device endpoints, and respect complex policies like coexistence with on-premises Skype for Business. Even minor synchronization delays can cascade into the kind of global inconsistency seen today.
“The real problem isn’t the technology—Microsoft has solved the distributed state problem before with Services like Azure SignalR. The challenge is the sheer number of interdependencies in the Microsoft 365 graph,” explained an independent cloud architecture consultant. “A presence update might touch Exchange, SharePoint, Teams, and Viva Insights simultaneously. One misaligned schema change in any of those systems can cause the whole thing to crumble.”
User advocacy groups are calling for Microsoft to provide more granular outage notifications and to empower end users with better troubleshooting tools. Suggestions include a dedicated presence health checker built into Teams that can alert users when the service is degraded, and more accessible manual override options that do not require delving into settings.
What Happens Next?
As the clock ticks toward the end of the European business day, all eyes are on Microsoft’s next move. Engineering teams are undoubtedly poring over telemetry streams and rolling back recent deployments. Once a fix is validated, it will likely be deployed gradually to avoid further destabilization. Users should watch the Service Health Dashboard (admin.microsoft.com/servicestatus) and the @MSFT365Status handle for official updates.
In the meantime, the incident serves as a stark reminder that even the most robust cloud platforms are susceptible to failures in their most fundamental features. For the millions who rely on that little green dot to navigate their workday, June 17 was a lesson in fragility—and an impetus to have a backup plan ready for the next time presence goes dark.
Windows News will update this story as more information becomes available. If you were affected by the outage, share your experience in the comments below.