Web & Browsers

Microsoft 365 Down? How to Check Outlook and Teams Status

A practical guide to checking a Microsoft 365 outage and telling Outlook or Teams service issues apart from browser, account, and network problems.

Outlined browser panel with mail and chat symbols connected to a cloud, warning indicator, and checked laptop in lavender, violet, and sage on an ivory background.

Outlook refuses to load, Teams keeps reconnecting, and the first instinct is to restart everything. Sometimes that helps. Sometimes the problem is at Microsoft's end, and no amount of clearing caches will bring your inbox back.

A widespread Microsoft 365 disruption began on November 12, 2026, affecting Outlook, Teams-related functions, and other connected services. Microsoft said the affected services had been restored by November 14. The incident is a useful reminder: check service health before you start changing settings. A reported outage from last week does not mean the service is down right now.

Here's a quick way to separate a Microsoft 365 outage from a problem with your browser, device, network, or work account.

First, check Microsoft's own service status

Open Microsoft's Service Health Status page. It provides public information about Microsoft consumer services and may surface important business-service incidents, particularly when administrators cannot reach their normal dashboard.

For a work or school Microsoft 365 account, ask your administrator to check the detailed Service health view in the Microsoft 365 admin center. Microsoft documents the navigation as Health > Service health. This view is more useful for organization-specific incidents and advisories than a generic public status page.

Look for the affected product, when the incident began, the symptoms Microsoft acknowledges, and the time of the last update. An incident may affect only some regions, organizations, or features. A green public page is reassuring, but it does not rule out a tenant-specific issue.

You can also check Microsoft 365 Status on X for incident updates. Third-party outage trackers can provide additional signals, but a spike in user reports is not proof of the underlying cause.

Know which Outlook account you're using

There are two products that are easy to confuse:

  • Outlook.com: personal mail accounts such as Outlook.com, Hotmail.com, and Live.com.

  • Outlook on the web: the browser interface for a Microsoft 365 work or school mailbox, typically opened through Microsoft365.com or outlook.office365.com.

Their status and troubleshooting paths are not always identical. If only your company mailbox is failing while a personal Outlook.com account works, that doesn't prove your computer is fine or that Microsoft 365 is broadly down. It simply narrows the problem.

A five-minute checklist before you change anything

  1. Try the browser version. If desktop Outlook fails, open your work mailbox in a supported browser. For Teams, try teams.microsoft.com. If the web versions work, focus on the installed client or its sign-in state. If both fail, check service health and network access before assuming why.

  2. Try a private browser window. A private or incognito window can help distinguish a normal browser session problem from a wider issue. It does not bypass company security rules, and some extensions or policies may still apply.

  3. Try another connection, if permitted. Switching temporarily from home Wi-Fi to a mobile hotspot can reveal a network-specific problem. On a managed work device, follow your organization's network and VPN policy rather than disabling required controls.

  4. Ask whether a colleague sees the same error. Compare the same Microsoft 365 service, at roughly the same time, with a colleague in your organization. One failing account and several failing accounts suggest different investigation paths.

  5. Record the exact symptom. Note the error message, timestamp, affected app, whether sign-in succeeds, and whether sending, receiving, or calendar access is affected. This is more useful to IT than simply saying, 'Microsoft is down.'

One simple network check on Windows

If you use Windows and want a quick connectivity clue, open PowerShell and run:

plaintext
Test-NetConnection outlook.office365.com -Port 443

This tests whether your device can establish a TCP connection to that hostname on port 443. A TcpTestSucceeded result of True suggests that particular network connection works; it does not prove Outlook is healthy, that you can sign in, or that email delivery works. A failure can come from DNS, a firewall, a proxy, or the network path, not necessarily a Microsoft outage.

For personal Outlook.com accounts or Teams problems, use the relevant web app and service-status information rather than treating this Outlook business hostname as a universal test.

When Outlook works but mail still doesn't arrive

A successful sign-in is not the same as healthy mail flow. You might be able to read old messages while new messages are delayed. Check whether the problem affects incoming mail, outgoing mail, or just desktop synchronization.

If you're a user, inspect your Outbox, Sent Items, and any visible error without repeatedly resending the same message. Multiple retries can lead to duplicates once delivery recovers. If you're an administrator, use the appropriate Exchange Online diagnostics and message-trace tools available to your organization rather than guessing from the desktop app alone.

After a major outage is declared resolved, allow for the possibility that mail queues and application synchronization may take additional time to settle. Follow the incident updates for your tenant rather than treating the first successful login as proof that every delayed action has completed.

What to avoid during a confirmed Microsoft 365 outage

  • Don't reset passwords across the team unless there's a separate sign-in or security reason.

  • Don't remove Outlook profiles, reinstall Office, or delete application data just because the service is failing for many users.

  • Don't disable antivirus, firewalls, or company VPN controls as an improvised workaround.

  • Don't change your organization's DNS or mail routing in response to a cloud-service incident without identifying a genuine configuration problem.

When the service provider is restoring a disrupted backend, local configuration changes may create extra work after the outage is over.

How the November 2026 incident was resolved

News reports from November 13 described a major disruption to Microsoft 365 services, including Outlook and Teams-connected features. On November 14, Microsoft said service had been restored following a technical problem associated with network capacity changes. Reporting also said Microsoft found no indication that a cyberattack caused that incident. These are details of that specific event, not a diagnosis of future outages.

If you're reading this during a later incident, don't rely on those dates. Use the current Microsoft status page and, for work accounts, the admin center's Service health dashboard.

Quick answers

Is Outlook down right now?

A static article can't reliably answer a live status question. Check the official Microsoft status page and your organization's Service health dashboard, then compare that information with the symptoms you're seeing.

Why does Teams chat work while its calendar fails?

Features in Microsoft 365 can depend on different underlying services. A problem affecting Exchange Online, for example, may disrupt calendar-related features while other Teams functions remain available. Check the incident's listed symptoms rather than assuming every part of Teams must fail together.

Should I clear my browser cache?

Not as your first move. Try a private window and confirm service health first. If the issue is isolated to your browser session, targeted troubleshooting may help. Clearing all browser data can sign you out of unrelated sites and remove stored preferences.

The practical takeaway

Start with the official service-health dashboard. Then compare the web app, desktop app, another connection, and a colleague's experience. Those few checks usually tell you whether it's time to troubleshoot your own setup or wait for a documented service issue to be resolved.

Further reading: Microsoft's guide to checking service health, Outlook on the web sign-in help, and Teams connection troubleshooting.