Enterprise downtime costs $9,000+ per minute on average
ITIC research: 91% of enterprises say hourly downtime costs exceed $300,000. The average across all industries is $540,000/hour. Early detection reduces outage duration by 70%.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Microsoft goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Microsoft + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
Is Microsoft Down Right Now?
Guide to checking Microsoft 365, Outlook, Teams, OneDrive, and Azure status — with official sources, common error codes, and what to do when Microsoft services stop working.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
How to Check Microsoft Status Right Now
- 1. M365 Service Health — most detailed, requires admin login
- 2. Azure Status Page — public, real-time cloud status
- 3. DownDetector — crowdsourced user reports, fast signal
- 4. Search X/Twitter: "Microsoft down" — real-time social signal
🔧 Recommended Tools
Some Microsoft issues are ISP or region-specific. A VPN lets you test from different locations and bypass local blocks.
6,400+ servers in 111 countries · 30-day money-back guarantee
Monitor Microsoft and 100+ APIs with instant email alerts. 14-day free trial.
Microsoft Service Components
Microsoft operates dozens of independent services. An Outlook outage won't always mean Teams is down — each has its own status:
Word, Excel, PowerPoint, and web apps
Email and calendar service
Collaboration, chat, and video conferencing
Cloud file storage and sync
Intranet, document management
Cloud infrastructure, VMs, databases, AI services
Gaming network, Game Pass, store
Identity and access management
Stop finding out about Microsoft outages from your users
Set up independent monitoring so you know the moment Microsoft services degrade — before your team or customers start filing tickets.
Try Better Stack Free →Common Microsoft Error Codes & Fixes
0x80090016Microsoft account token refresh failedFix: Sign out from all devices and sign back in; clear the Windows Credential Manager
AADSTS50076Azure AD multi-factor authentication requiredFix: Complete MFA challenge; if locked out, contact your M365 admin for bypass
503 Service UnavailableMicrosoft server temporarily unavailableFix: Wait 5-10 minutes and retry; check M365 Service Health for active incidents
CAA20002 (Outlook)Authentication failed — invalid credentialsFix: Re-enter your Microsoft account credentials; check if your password has expired
Teams Error 80070422Windows service required for Teams is disabledFix: Enable the "Windows Update" service in Services (services.msc) and restart
OneDrive Error 0x80004005Unspecified sync errorFix: Unlink and re-link your OneDrive account; check file name restrictions
Troubleshooting Microsoft Outages
Isolate: service vs. local issue
If Outlook desktop is broken, try Outlook Web (outlook.office.com). If that works, the issue is your local app. If web is also broken, it's a Microsoft service incident.
Check the Service Health portal
M365 admins can see granular incident details at admin.microsoft.com — including estimated resolution time, affected users, and engineering updates.
Set up Service Health alerts
In the M365 admin portal, configure email alerts for specific services. You'll receive notifications the moment Microsoft declares an incident — rather than discovering it via frustrated users.
Use independent monitoring as a backup signal
Microsoft's status page occasionally lags behind real incidents. A synthetic monitor making real Outlook API calls every minute using Better Stack can detect degradation before the official page updates.
🏢 Microsoft Outage Business Continuity
Microsoft 365 downtime directly impacts productivity for over 400 million commercial users worldwide. Having a fallback plan is essential for businesses dependent on M365.
Recommended Continuity Steps
- • Keep local copies of critical documents (OneDrive sync)
- • Have a backup communication channel (Slack, Zoom) for when Teams is down
- • Enable Outlook cached exchange mode so email works offline
- • For Azure-dependent apps: configure multi-region failover and circuit breakers
- • Subscribe to Microsoft service health alerts via your admin portal
Related Guides
🌐 Can't Access Microsoft?
If Microsoft is working for others but not for you, it might be an ISP or regional issue. A VPN can help bypass network-level blocks and routing problems.
Troubleshoot with a VPN
Connect from a different region to test if the issue is local to your network. Also protects your connection on public Wi-Fi.
Try NordVPN — 30-Day Money-Back GuaranteeSecure Your Microsoft Account
Service outages are a common time for phishing attacks. Use a password manager to keep unique, strong passwords for every account.
Try NordPass — Free Password Manager🛠 Tools We Use & Recommend
Tested across our own infrastructure monitoring 200+ APIs daily
Uptime Monitoring & Incident Management
Used by 100,000+ websites
Monitors your APIs every 30 seconds. Instant alerts via Slack, email, SMS, and phone calls when something goes down.
“We use Better Stack to monitor every API on this site. It caught 23 outages last month before users reported them.”
Secrets Management & Developer Security
Trusted by 150,000+ businesses
Manage API keys, database passwords, and service tokens with CLI integration and automatic rotation.
“After covering dozens of outages caused by leaked credentials, we recommend every team use a secrets manager.”
SEO & Site Performance Monitoring
Used by 10M+ marketers
Track your site health, uptime, search rankings, and competitor movements from one dashboard.
“We use SEMrush to track how our API status pages rank and catch site health issues early.”
Frequently Asked Questions
Is Microsoft down right now?
To check if Microsoft is currently down: 1) Visit the Microsoft 365 Service Health dashboard at admin.microsoft.com/Adminportal/Home#/servicehealth (requires M365 admin account), 2) Check the public Azure Status page at azure.microsoft.com/en-us/status, 3) Check DownDetector for real-time user reports, 4) Search "Microsoft down" on Twitter/X for live updates. Microsoft outages often affect specific services (Outlook, Teams, SharePoint) independently rather than all services at once.
Why is Microsoft Outlook not working today?
Outlook issues can stem from multiple causes: 1) Microsoft Exchange server outage — check the M365 Service Health page, 2) Local profile corruption — try Outlook Web (outlook.office.com) to isolate the issue, 3) DNS or network issues — try from a different network, 4) Add-in conflicts — start Outlook in safe mode (outlook.exe /safe), 5) Authentication issues — sign out and back in. If Outlook Web works but the desktop app doesn't, the issue is local. If neither works, it's a service outage.
Why is Microsoft Teams not working?
Microsoft Teams outages are tracked separately from other M365 services. Check admin.microsoft.com for "Microsoft Teams" status. Common fixes for Teams issues: 1) Clear the Teams cache (delete %appdata%\Microsoft\Teams), 2) Sign out and back in, 3) Check if the issue is app-specific by trying teams.microsoft.com in a browser, 4) Verify your Microsoft 365 license is active. Teams has experienced several high-profile outages during peak usage periods.
Is Azure down? How do I check Azure status?
Check Azure status at azure.microsoft.com/en-us/status for a global view. For more detailed regional and service-level status, use the Azure Service Health blade inside the Azure Portal (search "Service Health"). Azure incidents are often region-specific — an East US outage won't affect West Europe. For critical production systems, set up Azure Service Health alerts to receive proactive notifications about outages affecting your specific services and regions.
How long do Microsoft outages usually last?
Most Microsoft 365 service degradations resolve within 1-4 hours. Major incidents (affecting multiple services or regions) can last 4-8 hours. Azure regional outages have historically lasted 1-6 hours. Microsoft posts post-incident reviews (PIRs) within 5 business days for significant events. You can access historical incident reports via the Microsoft Service Health portal or the Microsoft Trust Center.