A widespread Microsoft Teams outage on Wednesday, June 17, 2026, left thousands of users across the United Kingdom and Europe grappling with a deceptive collaboration breakdown: the platform’s presence indicators—those tiny green, yellow, and red dots that signal availability—began displaying completely incorrect statuses. Microsoft quickly confirmed the service incident via its Microsoft 365 admin center, acknowledging that presence data had become unreliable for a significant portion of the European working day.
The problem first surfaced during the mid-morning hours British Summer Time, with users reporting that colleagues who were actively working appeared as "Offline" or "Away," while others who were out of office or in meetings displayed a misleading "Available" status. This sudden unreliability in a feature as foundational as presence created immediate chaos for teams dependent on real-time awareness to initiate chats, calls, or video meetings. For remote and hybrid workers who rely on presence as a digital substitute for a visual sweep of the office, the outage turned even simple coordination into a guessing game.
By 10:00 BST, the volume of complaints on social media platforms and community forums had spiked dramatically. "I thought my entire team was off sick until I walked down the hall and saw them all at their desks," one London-based project lead told WindowsNews.ai, encapsulating the bizarre nature of the glitch. Another user from Berlin described receiving an urgent call from a manager who had been showing as "Busy" for over an hour, only to learn the status was never accurate. The disconnect between virtual presence and physical reality not only eroded trust in the tool but also led to missed deadlines and fractured communication chains.
Microsoft’s official communication came through the Microsoft 365 admin center’s Service Health Dashboard, where a new incident was posted under the category "Microsoft Teams." While the company did not disclose an incident number in its initial posting, it confirmed that "users may see incorrect presence information for other users in Microsoft Teams" and that the issue was primarily impacting organizations located in the UK and parts of continental Europe. An update followed shortly, stating that engineers were investigating a potential fault in the back-end service that aggregates and synchronizes presence data across the Teams ecosystem.
As the hours progressed, additional updates indicated that Microsoft had identified a component failure within the presence aggregation layer—a subsystem responsible for collecting signals from multiple endpoints (desktop clients, mobile apps, calendar entries, manual status settings) and distributing a unified presence state to all contacts. This layer, which operates across different geographical data centers, likely experienced a synchronization failure specific to the European region. At 14:35 BST, Microsoft reported that the fix was being applied and that users should begin seeing correct presence data within 30 minutes. Full restoration was confirmed by 16:00 BST, roughly six hours after the first signs of trouble.
The outage serves as a stark reminder of how deeply embedded real-time presence has become in modern workplace culture. First introduced in the 2000s with instant messengers, presence evolved into a critical component of collaboration platforms like Teams, Slack, and Zoom. In Microsoft Teams, presence is not just a status icon; it triggers notification behaviors, determines whether an incoming call rings or goes to voicemail, and influences whether a user appears in the "People" suggestions when starting a new chat. When presence signals go awry, it’s not merely an annoyance—it actively disrupts the workflow.
A technical breakdown of Teams’ presence architecture reveals why this type of outage is both impactful and difficult to prevent. The system continuously polls the Teams client on each device for aggregated activity indicators, including keyboard and mouse activity, active application usage, and scheduled meetings from Outlook or Exchange. It then runs a complex algorithm to infer a user’s state—Available, Busy, Away, Do Not Disturb, or Offline—and propagates that state instantly to all co-authoring and contact endpoints. Because presence is inherently tied to real-time events and requires low-latency distribution, caching mechanisms are fragile; a regional cache corruption or a misrouted signal can cascade into the kind of false-state reporting seen on June 17.
This is not the first time that Microsoft Teams has suffered a presence-related incident. In February 2023, a global outage caused presence to become completely non-functional for several hours, with all users appearing as "Unknown" or "Offline." That event was traced to a configuration change in the presence database that led to cascading authentication failures. In March 2020, as remote work surged during the early pandemic lockdowns, Teams presence intermittently failed across Europe due to strained capacity in the Azure region hosting the service. While Microsoft has since invested heavily in geo-redundancy and failover mechanisms, the recurrence of a region-specific presence issue suggests that the underlying synchronization framework still has brittleness that can be exposed under certain operational conditions.
For IT administrators caught in the middle on June 17, the immediate advice from Microsoft was to monitor the Service Health Dashboard for updates and to communicate the incident status to their user base. Many admins turned to the Microsoft 365 Admin Center’s message center and the official @MSFT365Status Twitter account for real-time updates. Some organizations deployed their own workarounds: managers instructed staff to manually set their status via the Teams client (e.g., manually selecting "Available" or "Busy") and to use the "Notify when available" feature to queue messages until real statuses returned. Others resorted to backing up critical communications through email or phone calls, effectively bypassing Teams altogether for the duration of the incident.
The operational response from Microsoft was relatively swift by historical standards, but the lack of an immediate root cause analysis left many questioning the resilience of the platform. In the hours after service restoration, no detailed post-incident report had been published, although such a document is typically made available to customers with Premier support or via the Admin Center within five business days. Enterprises with stringent service-level agreements will likely probe deeper into what mitigation strategies Microsoft will implement to prevent a repeat.
From a user experience standpoint, the incident highlights a broader challenge facing all unified communications platforms: the unwavering trust users place in presence indicators, often without realizing that these icons are fallible computational inferences, not absolute truths. When presence fails, it’s not just a technical hiccup—it alters team dynamics. Colleagues are mistakenly overlooked, messages are sent at inopportune times, and the subtle etiquette of digital availability breaks down. In an era where asynchronous work and flexible hours are the norm, the veracity of presence becomes even more critical; a single glitch can amplify the isolation of remote workers or disrupt careful workflows designed around "heads-down" time.
Looking ahead, Microsoft is likely to double down on regional resilience for its presence services. The trend among cloud providers is to adopt active-active architectures where traffic can be instantly rerouted without user-perceptible latency. Teams already leverages Azure’s global footprint, but presence synchronization may still rely on a primary-region model that could be a single point of failure for a given geographic area. The upcoming year’s roadmap, which Microsoft typically unveils at its annual Ignite conference, is expected to feature improvements in Teams’ core infrastructure, including presence reliability.
In the interim, businesses reliant on Microsoft 365 are revisiting their continuity plans for communication tools. Some are evaluating third-party backup solutions that can provide an alternate presence channel, though few integrate as deeply as Teams. The June 17 outage may also prompt a fresh look at Microsoft’s service level commitments, which guarantee 99.9% uptime for Teams but have historically been met despite such isolated failures. For now, the incident serves as a real-world stress test that, while resolved within a workday, left a lasting impression on the fragility of digital office life.
As the sun set on London and Paris, Teams’ green dots finally came back to life, and the frantic calls subsided. But for many, the memory of a day when their colleagues seemed to vanish into digital thin air will linger, reinforcing a simple truth: in the modern workplace, presence is power, and when it disappears, so does the connection that binds distributed teams.