All Microsoft products are operational, and two planned service updates are announced for December 2026.
Microsoft Teams (MC1556088): New Teams releases will require iOS 18 or later on iPhone and iPadOS 18 or later on iPad. The rollout runs from mid December 2026 to early January 2027, worldwide. Teams already installed on iOS 17 or iPadOS 17 keeps working but will not receive newer versions.
OneDrive (MC1558030): From 14 December 2026, OneDrive on Windows and Mac will exclude newly created folders named "node_modules" from syncing by default, to improve sync performance and reduce storage and bandwidth use. The rollout is expected to finish in mid January 2027, worldwide. Existing folders keep syncing. Excluded folders stay on the device but are not available on other devices or the web. Administrators can turn off the exclusion through OneDrive sync policies.
Advisory only. This page is provided for information and analytics. Decisions on fixes rest with the authorised decision makers of each organisation, guided by their subject matter experts. Read the full disclaimer.
Need help?
Your Azosis Support Team
Microsoft 365 usage by country dashboard
Share of user reports by country, last 24 hours
Top countries by Microsoft Office 365 companies
| # | Country | Latest public figure | Reported impact |
|---|---|---|---|
| 1 | United StatesAzosis region | About 110 million users | Largest market in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
| 2 | IndiaAzosis region | About 32 million users | Second in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
| 3 | United Kingdom | About 24 million users | Third in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
| 4 | Germany | About 22 million users | Fourth in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
| 5 | Canada | About 14 million users | Fifth in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
| 6 | France | About 13 million users | Sixth in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
| 7 | Australia | About 11 million users | Seventh in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
| 8 | Netherlands | About 7 million users | Eighth in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
| 9 | United Arab EmiratesAzosis region | About 3 million users | Ninth in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
| 10 | SingaporeAzosis region | About 2.5 million users | Tenth in this estimateUnverified estimate, not Microsoft data, Nov 2026 |
Live trackers
Live dashboard
Advisory details
Affected services
- Microsoft Teams on iPhone (iOS 17)
- Microsoft Teams on iPad (iPadOS 17)
- Microsoft OneDrive on Windows
- Microsoft OneDrive on Mac
Recommended actions
Microsoft Teams on iOS 17 and iPadOS 17 (MC1556088)
- Check which iPhones and iPads in your organisation still run iOS 17 or iPadOS 17.
- Upgrade them to iOS 18 or iPadOS 18 where the device supports it.
- After upgrading, update Microsoft Teams from the App Store.
- Check that Intune or other device management policies do not block the upgrade.
OneDrive node_modules folders (MC1558030)
- Identify developers who use OneDrive for JavaScript and Node.js projects.
- Notify affected users about the new sync behaviour.
- Review OneDrive sync policies and configure exceptions if these folders need to sync.
- Update internal IT support documentation.
Update log
| Time (UTC) | Update |
|---|---|
| 18 Nov, 07:23 | Microsoft advisory MC1558030 published: OneDrive will exclude newly created node_modules folders from sync by default from 14 December 2026. (Microsoft Message Center) |
| 18 Nov, 04:54 | Microsoft advisory MC1556088 published: Teams will require iOS 18 or iPadOS 18 or later from mid December 2026. (Microsoft Message Center) |
| 14 Nov, 06:31 | All the Microsoft Products are operational (Latest Update from Microsoft) |
| 14 Nov, 06:31 | All the Microsoft Products are operational (Latest update from Microsoft) |
| 14 Nov, 05:43 | Microsoft update: This site is updated when service issues are preventing tenant administrators from accessing Service health in the Microsoft 365 admin center. Alternatively, customers can reference https://www.twitter.com/MSFT365Status for additional insights into widespread, active incidents. |
| 13 Nov, 22:00 | Microsoft update: We continue to observe sustained service recovery across the previously affected environments. Due to the severity of impact this incident caused, we're monitoring for an extended period to ensure no additional mitigative actions are required. In parallel, we're monitoring the backlog of email messages accrued during this event to ensure all process successfully before considering the issue resolved. |
| 13 Nov, 20:02 | Microsoft update: As infrastructure stabilizes, we're still draining queued messages and rebalancing traffic, so customers may see improved sign in/access while delivery and processing continue to catch up. We do not have an ETA for full recovery yet. Service access can recover before mail flow fully normalizes. |
| 13 Nov, 17:57 | Microsoft update: We are deeply sorry for the disruption this incident has caused you and your business. We know the trust you place in our services and take that responsibility extremely seriously. We are seeing broad recovery and stability across our services. This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. |
| 13 Nov, 15:56 | Microsoft update: We remain focused on addressing residual impact and ensuring reliable service restoration. We continue to assess recovery across various connection methods and are closely monitoring service health to verify sustained stability. At this time, we have no evidence of malicious activity associated with this incident. |
| 13 Nov, 12:00 | Microsoft update: We’re seeing encouraging recovery progress in Europe, with service availability and email delivery performance improving across a growing portion of affected Microsoft 365 infrastructure. Japan remains comparatively more stable, while North America is also improving; however, some users may still experience intermittent issues as recovery actions continue. |
| 13 Nov, 11:04 | Microsoft update: We've made additional progress toward service recovery, with recovery actions completed across portions of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, and we're seeing improvements in key customer scenarios, including mailbox access and delayed email processing. However, some users may continue to experience intermittent issues. |
| 13 Nov, 10:01 | Microsoft update: Recovery actions are ongoing and have progressed in phases across affected Microsoft 365 infrastructure. Global telemetry and customer reports show incremental improvement in several workloads; however, service health remains variable and capacity has not yet fully returned to baseline. Network and traffic management actions remain active. |
| 13 Nov, 09:14 | Microsoft update: Users may be unable to connect to multiple Microsoft 365 services. |
| 13 Nov, 09:10 | Microsoft update: Recovery efforts are ongoing across impacted infrastructure. We are seeing early signs of stabilization, but service capacity has not yet returned to normal levels and health remains variable as traffic is carefully reintroduced.Our primary mitigation path continues to focus on service stability and controlled recovery. |
| 13 Nov, 07:29 | Microsoft update: We’re seeing positive results for server stability after applying an upstream authentication/routing configuration component patch to a portion of our infrastructure. We’ll continue to monitor its progress and are working to expand it to servers supporting active regions coming online. As of now, we are not aware of any malicious activity that is causing this incident. |
| 13 Nov, 00:30 | Azosis advisory published. Latest Microsoft position: partial recovery, not resolved. |
| 12 Nov, late | Microsoft returning a portion of affected servers to service, stable so far. Shifting traffic to alternate routes with limited recovery. |
| 12 Nov, late | Microsoft found a core process on affected servers becoming overwhelmed. Earlier actions had not given the expected relief, so all recovery pathways opened. |
| 12 Nov, ~21:00 | Alternative server health check method validated. Some servers returning to service. |
| 12 Nov, ~20:30 | No recent change found that matches the start of impact. Failed health checks traced to a component that processes server health. |
| 12 Nov, ~19:00 | All deployments paused. Traffic moved off affected infrastructure. Servers being restarted. |
| 12 Nov, ~18:48 | Connection traffic redistributed across worldwide infrastructure. |
| 12 Nov, 18:26 | Incident MO1550821 opened. Microsoft confirms impact may reach users in any region. |
| 12 Nov, ~17:30 | Exchange Online mailbox access problems reported in the Americas (EX1550543). |
Sources: Microsoft 365 Status on X, BleepingComputer, Global News, Digital Trends.