Is Microsoft Down? How to Check and What to Do

Outlook is not sending email. Teams calls keep dropping. SharePoint files will not open. When Microsoft services go down, the impact hits millions of businesses simultaneously. Microsoft 365 alone has over 400 million paid seats, and Azure powers a significant percentage of enterprise cloud infrastructure. A Microsoft outage does not just inconvenience individual users. It can halt entire organizations.

This guide covers how to check if Microsoft is down, what typically causes outages across their major services, and what you can do while waiting for recovery.

How to Check if Microsoft Is Down

Microsoft operates dozens of interconnected services. An outage in one does not necessarily mean all of them are down. Here is how to pinpoint what is affected.

Check the Official Microsoft Status Pages

Microsoft maintains separate status pages for different product families.

The Microsoft 365 status page shows current incidents and advisories for each service. Each entry includes a description, affected regions, and a timeline of updates. Azure's status page breaks down by service (Virtual Machines, App Service, SQL Database, etc.) and by region.

For Microsoft 365, administrators can also check the Service Health page in the admin center at admin.microsoft.com. This provides more granular detail, including the number of affected users in your tenant, than the public status page.

Use Is That Down

Is That Down monitors Microsoft's status pages and sends you an alert the moment an incident is declared. This saves you from manually refreshing status.office.com during a suspected outage. For a broader look at checking any service, see our guide on how to check if a service is down.

Check Third-Party Outage Trackers

Downdetector is one of the most popular places people report Microsoft outages. It tracks separate pages for Microsoft 365, Teams, Outlook, Azure, and Xbox. A sudden spike in user reports, especially during business hours in major time zones, is a reliable signal that something is wrong. Downdetector often reflects problems before Microsoft's official status page is updated.

Check Social Media

Search Twitter/X for "microsoft down," "teams down," or "outlook down." Microsoft outages trend fast because of the sheer number of affected users. The @MSABORDC and @Microsoft365Status accounts post updates during incidents, though the official status pages tend to be more detailed.

Test the Specific Service

If Teams is not working, try Outlook on the web (outlook.office.com). If Outlook is down, try SharePoint. Microsoft services share infrastructure but can fail independently. Knowing exactly which service is down helps you find the right workaround.

For Teams specifically, try the web version at teams.microsoft.com if the desktop app is not working. Desktop app issues are sometimes caused by local caching problems rather than a service outage.

Microsoft Services and Their Dependencies

Understanding which services depend on which infrastructure helps you predict the scope of an outage.

Microsoft Teams depends on Azure AD for authentication, Exchange Online for calendar integration, SharePoint for file storage, and its own real-time communication infrastructure for messaging and calls. A Teams outage can be caused by a failure in any of these dependencies.

Outlook / Exchange Online handles email, calendar, and contacts. It has its own infrastructure but depends on Azure AD for authentication and Azure networking for connectivity.

SharePoint and OneDrive share the same underlying storage and application platform. If SharePoint is down, OneDrive is usually affected too. Both depend on Azure AD and Azure infrastructure.

Azure is the foundation for all of Microsoft's cloud services. Azure outages can cascade to Microsoft 365, Dynamics 365, and third-party applications hosted on Azure. Azure itself is divided into dozens of services across multiple regions, so an Azure outage does not necessarily mean all of Azure is down.

Common Causes of Microsoft Outages

Azure Active Directory (Entra ID) Issues

Azure AD (now called Microsoft Entra ID) handles authentication for virtually all Microsoft cloud services. When Azure AD has problems, users cannot sign in to anything: Teams, Outlook, SharePoint, Azure Portal, and every third-party app that uses Microsoft for single sign-on. Azure AD outages are among the most impactful because they affect every service that depends on authentication.

Networking and DNS Problems

Microsoft operates a global network connecting its data centers. Routing issues, DNS misconfigurations, or problems at internet exchange points can isolate specific regions from Microsoft services. These outages are often regional, with users in one part of the world affected while others are fine.

Capacity and Scaling Issues

Microsoft 365 usage follows predictable patterns: surges during business hours in major time zones, Monday mornings, and after holidays. Unpredictable surges also occur during global events that drive everyone to Teams simultaneously. If infrastructure cannot scale fast enough, services degrade for a subset of users.

Software Deployments

Microsoft deploys updates to its services continuously. A deployment that introduces a regression can affect production users. Microsoft uses staged rollouts (deploying to a small percentage of users first), but issues sometimes slip through to broader deployment. Teams is particularly prone to deployment-related issues because of its rapid release cadence.

Data Center Incidents

Physical infrastructure failures, including power outages, cooling failures, or network hardware problems, can take down services in specific Azure regions. Microsoft designs for redundancy, but single-region services or services with misconfigured failover can still be affected.

What to Do When Microsoft Is Down

Switch to Alternative Communication

If Teams is down, move calls to Zoom, Google Meet, or a phone conference line. If Outlook is down, use personal email or a messaging platform like Slack or Signal to coordinate with your team.

Prepare these alternatives before you need them. Having a documented backup communication plan means your team can switch over in minutes instead of scrambling. For tips on handling vendor outages, see the vendor monitoring guide.

Access Cached and Offline Content

Outlook desktop clients cache email locally. You can read and compose messages offline. They will send when connectivity is restored. OneDrive files that are set to "Always keep on this device" are available offline. Teams mobile apps cache recent chat messages.

Use Web Alternatives

Sometimes the desktop app is affected but the web version works (or the reverse). Try accessing Outlook at outlook.office.com, Teams at teams.microsoft.com, or SharePoint directly through your browser.

Communicate With Your Users

If you run a business that depends on Microsoft services, tell your customers and staff what is happening. Post on your own status page, send a message through a non-Microsoft channel, and link to Microsoft's status page. Proactive communication reduces support tickets and frustration.

How to Get Notified About Future Microsoft Outages

Subscribe to Microsoft status pages. Both status.office.com and status.azure.com offer RSS feeds. Microsoft 365 admins can configure email notifications through the admin center's Service Health section.

Use automated monitoring. Is That Down monitors Microsoft's status pages and sends alerts through email, Slack, or webhooks the moment an incident is reported. This is faster than waiting for Microsoft to send notifications through the admin center, which can lag behind the public status page. For a full alerting setup, see our guide on setting up outage alerts.

Set up a backup communication channel. Create a group on a non-Microsoft platform (Slack, Telegram, Signal) and ensure your team knows to check it if Teams goes down. Pin the instructions in your Teams channels so they are visible right before people lose access.

Recent Notable Microsoft Outages

January 2023 Azure AD/Networking Outage

In January 2023, a WAN routing change impacted connectivity between clients and several Microsoft services including Azure, Microsoft 365, and Power Platform. The incident lasted several hours and affected users worldwide. Microsoft attributed the issue to a change that impacted traffic across their wide area network, and the recovery required rolling back the change and revalidating traffic paths.

July 2022 Microsoft 365 Degradation

In mid-2022, Microsoft 365 services experienced widespread degradation affecting Teams, Exchange Online, and SharePoint Online. Users reported intermittent access failures and slow performance. The incident was linked to infrastructure changes that interacted badly with production traffic patterns. The extended recovery period frustrated enterprise customers who depend on these services for daily operations.

References

• Microsoft 365 Service Health - Official status for Microsoft 365 services.
• Azure Status - Official status for Azure services.
• Microsoft 365 Admin Center - Detailed service health for tenant administrators.

Beyond vendor monitoring, consider uptime monitoring for your own services and DNS monitoring to catch infrastructure issues that can look like vendor outages.