Live
Azosis Customer Advisory

Microsoft 365 Service Updates

Live status for Azosis customers. This page checks for new updates every 1 minutes.

Service updates MC1556088 and MC1558030

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.

Last updated: . This incident is closed.

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?

Contact us on WhatsApp

Your Azosis Support Team

Please message your dedicated Azosis support engineer on WhatsApp. They will check your tenant, keep you updated, and guide you on escalation if needed.

Email may be delayed during this outage, so WhatsApp is the fastest way to reach us.

Microsoft 365 usage by country dashboard

Figures compiled 18 Nov 2026, 08:11 UTC (22 h 37 min ago) from public trackers and news reports. Each figure shows its source and time. These are public figures and are verified by Azosis.

More than 430 millionPeople who use Microsoft 365 apps worldwideMicrosoft website, cited by CBS News, Nov 2026
About 110 millionMicrosoft 365 users in the United States in an unverified estimateEstimate only, not Microsoft data, Nov 2026
About 32 millionMicrosoft 365 users in India in an unverified estimateEstimate only, not Microsoft data, Nov 2026

Share of user reports by country, last 24 hours

Microsoft service status snapshot at 09:05 UTC, 18 Nov. Reports were made to that site, not to Azosis.

Top countries by Microsoft Office 365 companies

#CountryLatest public figureReported 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

How to read this: counts are reports submitted by members of the public to tracking sites. They show where people notice problems, not how many people are affected. Figures from different trackers and times are not directly comparable, so countries with published counts are ranked first by size, followed by countries with documented impact. These country figures are unverified estimates, not published by Microsoft, and may differ from actual usage.s using Microsoft Office 365 from job postings. They show relative presence, not total customers. Spain, Switzerland, Italy, Brazil, Belgium and Ireland rank between some of the countries shown but are not listed.

Live trackers

Live dashboard

Microsoft's official status over the last 24 hours, in 20 minute segments. Each tick marks a public Microsoft update. View only.

Microsoft status over the last 24 hoursEach segment is 20 minutes, coloured by Microsoft's official status. Each tick above the strip is a public Microsoft update.Microsoft updates18 Nov 07:00 UTC: Working normally18 Nov 07:20 UTC: Working normally18 Nov 07:40 UTC: Working normally18 Nov 08:00 UTC: Working normally18 Nov 08:20 UTC: Working normally18 Nov 08:40 UTC: Working normally18 Nov 09:00 UTC: Working normally18 Nov 09:20 UTC: Working normally18 Nov 09:40 UTC: Working normally18 Nov 10:00 UTC: Working normally18 Nov 10:20 UTC: Working normally18 Nov 10:40 UTC: Working normally18 Nov 11:00 UTC: Working normally18 Nov 11:20 UTC: Working normally18 Nov 11:40 UTC: Working normally18 Nov 12:00 UTC: Working normally18 Nov 12:20 UTC: Working normally18 Nov 12:40 UTC: Working normally18 Nov 13:00 UTC: Working normally18 Nov 13:20 UTC: Working normally18 Nov 13:40 UTC: Working normally18 Nov 14:00 UTC: Working normally18 Nov 14:20 UTC: Working normally18 Nov 14:40 UTC: Working normally18 Nov 15:00 UTC: Working normally18 Nov 15:20 UTC: Working normally18 Nov 15:40 UTC: Working normally18 Nov 16:00 UTC: Working normally18 Nov 16:20 UTC: Working normally18 Nov 16:40 UTC: Working normally18 Nov 17:00 UTC: Working normally18 Nov 17:20 UTC: Working normally18 Nov 17:40 UTC: Working normally18 Nov 18:00 UTC: Working normally18 Nov 18:20 UTC: Working normally18 Nov 18:40 UTC: Working normally18 Nov 19:00 UTC: Working normally18 Nov 19:20 UTC: Working normally18 Nov 19:40 UTC: Working normally18 Nov 20:00 UTC: Working normally18 Nov 20:20 UTC: Working normally18 Nov 20:40 UTC: Working normally18 Nov 21:00 UTC: Working normally18 Nov 21:20 UTC: Working normally18 Nov 21:40 UTC: Working normally18 Nov 22:00 UTC: Working normally18 Nov 22:20 UTC: Working normally18 Nov 22:40 UTC: Working normally18 Nov 23:00 UTC: Working normally18 Nov 23:20 UTC: Working normally18 Nov 23:40 UTC: Working normally19 Nov 00:00 UTC: Working normally19 Nov 00:20 UTC: Working normally19 Nov 00:40 UTC: Working normally19 Nov 01:00 UTC: Working normally19 Nov 01:20 UTC: Working normally19 Nov 01:40 UTC: Working normally19 Nov 02:00 UTC: Working normally19 Nov 02:20 UTC: Working normally19 Nov 02:40 UTC: Working normally19 Nov 03:00 UTC: Working normally19 Nov 03:20 UTC: Working normally19 Nov 03:40 UTC: Working normally19 Nov 04:00 UTC: Working normally19 Nov 04:20 UTC: Working normally19 Nov 04:40 UTC: Working normally19 Nov 05:00 UTC: Working normally19 Nov 05:20 UTC: Working normally19 Nov 05:40 UTC: Working normally19 Nov 06:00 UTC: Working normally19 Nov 06:20 UTC: Working normally19 Nov 06:40 UTC: Working normally12:0018:0000:0006:00now (UTC)
Working normallyPartial recovery or monitoringMajor outageMicrosoft update
Current statusAll services operationalper Microsoft
Microsoft updates11public posts so far

Advisory details

Announced18 Nov 2026, 05:00 UTC (9:00 AM Dubai, 10:30 AM India)
Microsoft referenceMC1556088 MC1558030
ScopeMicrosoft Teams on iPhone and iPad, and OneDrive on Windows and Mac. Worldwide, business and enterprise tenants.
Cause (per Microsoft)

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:23Microsoft 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:54Microsoft advisory MC1556088 published: Teams will require iOS 18 or iPadOS 18 or later from mid December 2026. (Microsoft Message Center)
14 Nov, 06:31All the Microsoft Products are operational (Latest Update from Microsoft)
14 Nov, 06:31All the Microsoft Products are operational (Latest update from Microsoft)
14 Nov, 05:43Microsoft 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:00Microsoft 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:02Microsoft 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:57Microsoft 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:56Microsoft 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:00Microsoft 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:04Microsoft 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:01Microsoft 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:14Microsoft update: Users may be unable to connect to multiple Microsoft 365 services.
13 Nov, 09:10Microsoft 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:29Microsoft 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:30Azosis advisory published. Latest Microsoft position: partial recovery, not resolved.
12 Nov, lateMicrosoft returning a portion of affected servers to service, stable so far. Shifting traffic to alternate routes with limited recovery.
12 Nov, lateMicrosoft 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:00Alternative server health check method validated. Some servers returning to service.
12 Nov, ~20:30No recent change found that matches the start of impact. Failed health checks traced to a component that processes server health.
12 Nov, ~19:00All deployments paused. Traffic moved off affected infrastructure. Servers being restarted.
12 Nov, ~18:48Connection traffic redistributed across worldwide infrastructure.
12 Nov, 18:26Incident MO1550821 opened. Microsoft confirms impact may reach users in any region.
12 Nov, ~17:30Exchange Online mailbox access problems reported in the Americas (EX1550543).

Sources: Microsoft 365 Status on X, BleepingComputer, Global News, Digital Trends.

Disclaimer

Advisory only. This page is purely advisory. Azosis Technologies provides it for information and analytics only, to help each organisation determine and decide on fixes together with the authorised decision makers of that organisation and the guidance of its subject matter experts. It is not professional, legal, technical or security advice for any particular situation.

Not an official Microsoft communication. Microsoft information on this page is summarised from Microsoft's public status sources and may be incomplete or delayed. For your own tenant, the Service health page in the Microsoft 365 admin center is the authoritative source. Azosis Technologies does not operate the affected Microsoft services and does not control their restoration.

Third party figures. Global and country figures come from third party public outage trackers and news reports named on the page, at the times shown. They reflect reports made by members of the public to those sites, not to Azosis Technologies, are not verified by Azosis Technologies, and show reported impact only, not confirmed faults or the number of people affected.

No warranty and no reliance. The information is provided as is and as available, without any warranty of accuracy, completeness or timeliness. It does not replace official notices or professional advice, and it does not change any contract. Your service agreement with Azosis Technologies continues to govern the services you receive. To the fullest extent permitted by applicable law, Azosis Technologies is not liable for loss or damage arising from decisions taken on the basis of this page alone.

View only. This page has no forms, sets no cookies and collects no information from visitors. Names and marks of Microsoft and of other companies belong to their owners and are used only to identify them. No affiliation or endorsement is implied.

The full terms of use and privacy notice apply to this page.