Loading story…
Microsoft is investigating a Teams service incident that is preventing some users from making or receiving calls. The company directed Microsoft 365 administrators to incident TM1475580 in the admin center; its public status update does not identify affected regions, customer segments, call types, root cause, or a restoration timeframe.
Organizations should confirm tenant-specific impact through Microsoft 365 service-health updates, preserve relevant network, endpoint, and identity telemetry, and use approved alternative communications channels while the issue is investigated. Microsoft has not characterized the disruption as a cyberattack or account compromise, but defenders should remain alert for phishing and unsanctioned collaboration-tool use during the outage.
See attribution, scope, and your downstream exposure.
1 event from the most recent confirmed update back to the earliest known activity.
Microsoft disclosed that it was investigating a service incident preventing some Microsoft Teams users from placing or receiving calls. The company directed administrators to incident TM1475580 in the Microsoft 365 admin center; the public advisory did not provide affected regions, root cause, or a restoration timeline.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See attribution, scope, and whether this vendor sits anywhere in your supply chain.
2 references tracked. Mallory keeps watching after this page renders.
cryptika.com
Open sourcecybersecuritynews.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Microsoft Teams experienced widespread outages, with users across the United States, Europe, and other regions reporting delays in sending messages and problems with other service functions. Microsoft acknowledged the issue publicly, stating that they were investigating the cause and observing signs of recovery, but did not initially provide a root cause or timeline for full restoration. The outage disrupted communication for many organizations relying on Teams for collaboration and messaging. Separately, a significant outage affected Microsoft 365 services—including Teams, Outlook, OneDrive, and the Copilot AI assistant—in Japan and China. This disruption was traced to a critical routing misconfiguration in Microsoft's infrastructure, which isolated healthy systems and led to intermittent login failures, degraded performance, and app loading errors. Microsoft confirmed that the incident was not the result of a cyberattack and reported that engineers had rebalanced traffic to restore service, with no data loss or security breaches identified. The outages caused notable business disruption in the affected regions, particularly for organizations dependent on Microsoft’s cloud ecosystem for daily operations.
Jun 29, 2026
Microsoft experienced a broad service disruption that affected **SharePoint**, **Teams**, **Excel**, the **Microsoft 365 Admin Center**, and Azure-hosted workloads, with users also reporting failures in **Dynamics 365**, **Dataverse**, Entra join operations, and administrative portals. Administrators said SharePoint timeouts, Teams image-loading failures, and unreachable Azure virtual machines were especially visible in **West US**, **Canada West**, and parts of **US East**, while Downdetector recorded a sharp spike in complaints. Microsoft acknowledged the incident and directed customers to service health alert `MO1437424`, saying it was investigating increased reports and reviewing telemetry to determine scope and impact. The disruption appeared to extend beyond core collaboration services into dependent platforms and Microsoft-backed update infrastructure. Sysadmins reported **Windows Media Creation Tool** failures with error `0x80072EE4 - 0x20000`, Windows feature enablement errors such as `0x80244022`, and **Windows Update** failures returning `0x801901f7` on newly imaged systems. A separate outage report also indicated **KaseyaOne** login issues that users linked to the Azure problems, suggesting downstream impact on third-party services hosted on Microsoft infrastructure as customers saw intermittent outages, degraded functionality, and some signs of partial recovery.
Jul 24, 2026
Microsoft reported a Microsoft 365 security-service failure in which **Exchange Online** anti-phishing heuristics incorrectly classified thousands of legitimate URLs as credential-phishing, leading to quarantined emails, blocked link access, and removal of messages via automated actions (including ZAP) across **email and Microsoft Teams**. The incident (tracked as `EX1227432`) ran from Feb 5 to Feb 12 and generated false XDR-style alerts such as “potentially malicious URL click was detected”; Microsoft attributed the impact to a **logic error** in newly updated heuristic detection, with additional tooling and a separate signature-system bug compounding and delaying rollback. Separately, Microsoft also worked an active **Microsoft Teams** outage/service degradation (tracked as `TM1233974`) affecting some users in the **United States and Europe**, with delays/failures sending and receiving chats that include inline media and issues joining meetings or signing in. A third item—abuse of **Atlassian Jira Cloud** notification emails to deliver localized scam lures and redirect victims to casino/investment fraud—describes a distinct threat campaign unrelated to the Microsoft 365 incidents and should be treated as a separate story.
Jun 29, 2026