Microsoft Confirms Outlook.com Outage: Sign-In Failures, "Too Many Requests" Errors Hit Users Globally

Microsoft confirmed on April 27, 2026 that Outlook.com is suffering a global outage that is preventing users from signing into their mailboxes. The disruption began earlier in the day and within three hours had generated thousands of complaints on Downdetector, with concentrated reports from the United Kingdom, Europe, North America, and parts of Asia — including India.

The official Microsoft 365 Status account acknowledged the incident, stating that engineers are investigating intermittent sign-in failures affecting Outlook.com customers. As of publication, the root cause has not been disclosed and no ETA has been given for resolution.

What Users Are Seeing#

The reported symptoms cluster around three patterns:

• Sign-in failures — entering the correct password returns "too many requests" or generic authentication errors
• Unexpected sign-outs — already-logged-in sessions are being terminated, forcing reauthentication that then fails
• iPhone Outlook app crashes — the mobile app is crashing on launch or loading but showing zero new messages despite expected inbox activity

Users on Reddit and the Microsoft Q&A forum report that the issue affects both personal Outlook.com mailboxes and Microsoft 365 work accounts that use Outlook.com infrastructure on the backend.

Indian Impact#

For Indian users, the outage hit during evening business hours (April 27 IST). Reports from Bengaluru, Mumbai, and Delhi confirm that Outlook web access (outlook.live.com) and the new Outlook for Windows app are returning sign-in errors. Microsoft 365 Business Basic and Standard customers in India also reported intermittent issues with Exchange Online sync, suggesting the outage extends beyond just consumer Outlook.com.

For startups and SMBs that have moved off Gmail to Microsoft 365 in the past 18 months — a notable trend driven by Copilot bundling — this is a meaningful productivity hit. Mid-sized Indian firms running customer support through shared Outlook inboxes are reportedly falling back to WhatsApp and phone for urgent communication.

What Microsoft Has Said#

From the Microsoft 365 Status feed: "We're investigating an issue where users may be unable to sign into Outlook.com. Customers may experience intermittent failures including 'too many requests' errors. We're working to identify the root cause and will provide an update as soon as one is available."

Translation: they don't yet know what broke. Historically, similar outages have been traced to authentication token service overload, a misconfigured DNS change, or a rolled-out backend update that didn't handle a specific edge case at scale. The "too many requests" error specifically suggests rate-limiting on the auth tier, which is consistent with either token service overload or a defensive throttle Microsoft activated to protect a downstream system.

Workarounds That Actually Help#

While Microsoft works on a fix, here's what Indian users can actually do right now:

1. Wait 15-20 minutes between sign-in attempts — repeatedly retrying in quick succession will deepen the "too many requests" lockout. Back off, then try once.
2. Try a different client — if web fails, try the desktop Outlook app or vice versa. The auth path differs slightly between clients, and one may succeed where another fails.
3. Use a different network — switch from broadband to mobile hotspot (or vice versa). Some auth failures correlate to specific network egress points.
4. Clear browser cache + cookies for live.com and microsoft.com — if you got partial token corruption during a sign-out, clearing fixes it.
5. For mobile: uninstall and reinstall the Outlook app — only do this if you have access to recovery credentials, since reinstalling forces fresh sign-in.
6. For business-critical email: use Outlook on the Web in private/incognito mode — bypasses any cached corrupted state.
7. Check status.office.com for the official Microsoft incident timeline.

What NOT to Do#

• Don't change your password — the issue is server-side, not credential-side. Changing your password during an outage can leave you locked out longer.
• Don't enable/disable 2FA right now — same reason. Auth state changes during an outage often get stuck.
• Don't delete and re-add the account in Outlook desktop — re-adding requires successful sign-in, which is exactly what's failing.
• Don't panic-call Microsoft support — for outages of this scale, support has the same information you do. Watch the status page instead.

The Bigger Pattern#

This is the third major Microsoft 365 outage in the past six months. February saw an Exchange Online routing failure that took mail delivery offline for ~4 hours. March had a Teams authentication outage. Now Outlook.com sign-in. The common thread: Microsoft's auth and identity tier is increasingly the single point of failure across the entire 365 stack.

For Indian IT decision-makers, this is the third data point in an emerging conversation about "is single-vendor productivity safe?" Google Workspace had its own multi-hour Drive outage last quarter. The honest answer is that no cloud productivity vendor is bulletproof — but the frequency of Microsoft 365 incidents in 2026 is higher than 2025, and that trend matters when you're renewing a 5-year enterprise contract.

How Long Will This Last?#

Based on the pattern of similar Outlook outages over the past two years: most are resolved in 4-8 hours from official acknowledgement. Auth-tier failures specifically tend to take longer because the fix often requires a controlled redeploy rather than a quick rollback. Set realistic expectations — full restoration today is possible but not guaranteed.

What to Watch Next#

Once Microsoft publishes the post-incident report (usually 5-10 business days after resolution), the interesting question is: which dependency caused this? Recent Microsoft 365 incident reports have pointed to Azure Active Directory Conditional Access policy changes and ENS (Edge Name Server) DNS issues. The pattern Microsoft chooses to disclose will tell you whether to expect repeat incidents.

We'll update this article when Microsoft confirms resolution. For now: take a coffee break, don't change your password, and try again in 20 minutes.