A cloud software dashboard shows service status and alerts across devices in a modern data center.
The question being asked across the US this morning is whether Microsoft 365 is down again. As of the most recent reporting available, the answer is "some users are reporting problems, and Microsoft has not confirmed a new widespread outage." That is not a satisfying headline, but it is the accurate one. Nerves are still raw after last week's large disruption, so it is worth separating what users are reporting from what Microsoft has confirmed.

A cloud software dashboard shows service status and alerts across devices in a modern data center. What's being reported on November 17​

The Sunday Guardian ran an explainer on Microsoft 365 trouble in the US. It named Word, Excel, Outlook, Teams, sign-in and cloud services as places users might see problems. It did not include Downdetector counts, a Microsoft incident number or evidence that each of those apps was failing. To its credit, it says plainly that user reports alone don't prove an outage.

Other outlets give more specific detail:

  • IBTimes Australia reported that users in the United States reported fresh issues with Exchange, logging in and Excel, even after Microsoft said last week's major outage had been resolved. It added that the reports did not establish a confirmed new nationwide outage, and that Microsoft had not acknowledged a new incident at the time of writing.
  • DesignTAXI's community tracker said Microsoft 365 and Outlook were reportedly down for some users on November 17, 2026. It said that based on the outage graph on DownDetector UK, reports started climbing around 7:57AM GMT (2:57AM Eastern Time). So at least some of today's complaints started in the UK, not only the US.
  • StatusGator, which watches Microsoft's official status feed, said it last checked the status of Microsoft Copilot (Microsoft 365) on November 17, 2026 at 11:05 AM UTC and the service was operational. Its page also showed a steady flow of user reports through the morning, including one person saying Copilot in Outlook was failing with a "something went wrong" message.

That last point shows the pattern. The official status said "operational" while individual users said "broken." Both can be true at once. A tenant-specific fault, a sign-in problem on one device or leftover effects from last week can all produce real complaints that never show up as a Microsoft-wide incident.

Bottom line: some users had real problems with Outlook/Exchange, sign-in and Excel today. Nothing found so far shows Word, PowerPoint, Teams, OneDrive and SharePoint failing together, and Microsoft has not announced a new confirmed incident.

Why everyone is jumpy: last week's large outage​

Today's reports follow a confirmed and serious incident. Wikipedia's entry on it says a major global Microsoft outage occurred from November 12 to 14, 2026, and that problems were reported with numerous Microsoft 365 services, including Outlook, Teams, and Copilot.

The main facts:

  • Timeline: IBTimes Australia, citing Microsoft's incident reports, said problems with Exchange Online began at around 11:17 a.m. Eastern time on Nov. 12, according to Microsoft's incident reports, followed by a broader Microsoft 365 outage at 1:26 p.m.
  • Incident IDs: IT consultancy Epifive said the outage was tracked as EX1550543 (Exchange Online, from 16:17 UTC / 11:17 a.m. ET / 21:47 IST on 12 November 2026) and MO1550821 (multiple services). German IT firm IT-Klett reported that Microsoft has set incidents EX1550543 and MO1550821 to "Post-Incident Report published". Admins who want Microsoft's full account can open those IDs in their tenant's Service health history.
  • Scale: Reuters reported on November 12 that Downdetector had logged more than 97,000 incidents of people reporting issues with Outlook at 2:07 p.m. ET, and that the actual number of affected users may vary. Those numbers belong to November 12. They are not today's figures.
  • Cause: IBTimes reported that Microsoft said the outage was caused by a technical issue introduced during a network-capacity upgrade. Microsoft also said it was not a cyberattack.
  • Knock-on effects: Reuters noted the disruption also hit connectors used by OpenAI's and Anthropic's AI services.

So when people return to work and Outlook stalls on a Monday or Tuesday, they jump to the worst conclusion. IBTimes put the open question well: it is not yet clear whether Monday's reports reflect lingering effects of last week's outage, isolated problems or a new issue.

Downdetector shows reports, not a diagnosis​

Downdetector is useful, but it only shows that users are complaining. It can't confirm what is actually wrong. As IBTimes put it, it collects reports submitted by users and does not confirm the cause or scale of a problem.

A spike tells you that many people are frustrated at the same time. It doesn't tell you:

  • whether the cause is Microsoft, an ISP, an identity provider or a single tenant's setup
  • which Microsoft 365 workloads are actually affected
  • how many distinct customers are affected

Use it to see whether others are having the same problem, then check Microsoft's official channels before you wake the CIO.

How to check what Microsoft has actually confirmed​

For admins: the Service health page​

Microsoft's documentation says organizations can view the health of Microsoft services, including Office on the web, Microsoft Teams, Exchange Online, and Microsoft Dynamics 365 on the Service health page in the Microsoft 365 admin center. The steps:

  1. Go to the Microsoft 365 admin center (admin.microsoft.com) and sign in with an admin account. Microsoft notes that people who are assigned the Service Support admin and Helpdesk admin role can view service health.
  2. In the left-hand navigation, go to Health > Service health, or select the Service health card on the Home dashboard.
  3. Look at the Overview tab. Two sections matter most. Issues for your organization to act on lists problems found in your own environment. Active issues Microsoft is working on lists incidents and advisories Microsoft is working to resolve.
  4. Check Issue history for problems resolved in the last 7 or 30 days. That is where last week's incident records and post-incident reports live.
  5. If users are clearly affected and nothing is listed, use Report an issue. Microsoft says it will look at related data and reports from other organizations to see how widespread the issue is, and if it originated with our service.

To get alerts instead of refreshing the page, go to Customize > Email and turn on service health email notifications. You can send them to up to two addresses per admin.

How to read the labels​

Microsoft separates advisories from incidents:

  • Advisory: Microsoft is aware of a problem affecting some users, but the service is still available. These are often intermittent or limited in scope. Today's scattered reports would fit this kind of entry, if Microsoft posts one at all.
  • Incident: a critical issue and the service or a major function of the service is unavailable, for example when users can't send or receive email or can't sign in.

Status values to watch for include Investigating, Service degradation, Service interruption, Restoring service, Extended recovery and Service restored. There is also False positive, which Microsoft uses when it confirms the service was healthy or the cause was outside its service.

If you can't reach the admin center​

Microsoft says that if you are unable to sign in to the admin center, you can use the service status page to check for known issues preventing you from logging into your tenant. It also points to its @MSFT365status account on X. Keep in mind that a green public status page is not proof your own tenant is fine. IBTimes noted that problems affecting a single organization may show up there before or instead of on Microsoft's public status page.

Practical troubleshooting for end users​

If Outlook won't sync or Excel won't open a shared workbook, try these low-risk checks before blaming Redmond:

  1. Check your connection. Confirm other sites load and restart your router if needed.
  2. Restart the app, or reload the browser tab for web apps.
  3. Sign out and back in. This helps if you keep getting repeated authentication prompts.
  4. Install pending Office updates for the affected app.
  5. Try another browser, a private window or another device. If Outlook on the web works but desktop Outlook doesn't, the problem is probably local.
  6. Ask a colleague. If one person is affected, look at that account or device. If the whole team is affected, tell IT.
  7. Check official status using the channels above.

These steps can't fix a fault on Microsoft's side. They only help you rule out your own setup. If Microsoft has a real incident open, waiting it out may be the only option.

Admins: also remember the SLA credits​

There's a money question from last week too. IBTimes reported that affected business customers can request service credits for the interruption. Cloud consultancy DeployFlow says SLA credits must be claimed by 31 December 2026. Confirm the terms that apply to your agreement. Don't let the claim window close while you're watching Downdetector today.

The takeaway​

Some users, mostly with Outlook/Exchange, sign-in and Excel, reported problems on November 17, a few days after a confirmed global outage. Microsoft has not confirmed a new widespread incident, and the evidence doesn't show every Microsoft 365 app failing at once. Admins should treat the tenant's Service health page as the authoritative source, set up email alerts, and file a Report an issue request if users are affected and Microsoft has posted nothing.

 

References

  1. Microsoft 365 Outage Today: Is Microsoft 365 Down in the US? Users Report Word, Excel, Outlook, Teams, Login and Cloud Service Issues | Check Latest Downdetector Status - The Sunday Guardian The Sunday Guardian 2026-11-17T15:20:41+00:00
  2. Microsoft 365 Down Again? Users Report Fresh Outlook, Excel and Login Problems as Workweek Begins After Outage ibtimes.com.au
  3. Is Microsoft 365 / Outlook down? (November 17, 2026) - Microsoft 365 / Azure / Outlook / Teams down? - DesignTAXI Community: Creative Connections, Conversations and Collaborations community.designtaxi.com