If your office inbox bounced you out this morning, you are not the only one refreshing the page. On 13 November 2026 Microsoft 365 was still degraded in India, a full day after the outage began on 12 November. Outlook, Teams and Copilot were all on the affected list. Moneycontrol reported the update at 13:51 IST, after Microsoft posted a status note at 12:59 pm IST saying a new patch was the first thing that actually looked stable.
This is not a “try logging out and back in” kind of morning. Microsoft has already restarted servers, moved traffic and rolled back recent configuration changes. Those steps did not hold. The company is now watching a patch on part of its infrastructure, and it still has not given a time when mail and chat will be normal again.
What Microsoft said at 12:59 pm IST
The status update sits under incident MO1550821. Microsoft said it was seeing “positive results for server stability after applying an upstream authentication/routing configuration component patch” on a portion of its infrastructure. Engineers were tracking how that fix behaved, and they planned to extend it to servers supporting active regions as those machines came back online.
Read that slowly. The patch was not on every server. It was on a portion. “Positive results” is not the same as “fixed.” The Microsoft 365 business and enterprise entry still carried a service degradation label when Moneycontrol checked. The next company update was due by 2 pm IST.
Microsoft also said it had found no sign of malicious activity. That matters in an Indian office WhatsApp group, because the first theory that spreads is usually “someone hacked it.” The company has promised a Post-Incident Report on the root cause and the repair once services are restored. Until that report lands, the public explanation is a capacity and health-check failure, not an attack.
Which apps are actually stuck
Moneycontrol’s reading of the status page listed Exchange Online, Microsoft Teams, Microsoft 365 Copilot, SharePoint Online, Microsoft Defender XDR and the wider Microsoft 365 suite. Microsoft said anyone trying to reach these services may be affected.
Business Today, updated 13 November 2026 at 10:20 am IST from its Noida desk, put the centre of the outage on Exchange Online, the cloud mail service behind Outlook. Users may be unable to open mailboxes in Outlook on the web, Outlook desktop using MAPI, Exchange ActiveSync or REST-based connections. If your phone mail app is blank and the desktop client is blank too, that is the same pipe, not two separate bugs.
Teams, Copilot and SharePoint were also hit, but Business Today noted the impact can differ by app and feature. Not every button inside Teams is necessarily dead. Copilot features that depend on mail and files are the ones colleagues were complaining about. SharePoint is the quiet one: the document you needed for a 3 pm review may simply not open, even if chat still sends a message.
How big the complaints got
Downdetector logged nearly 130,000 problem reports for Outlook at the peak, and more than 47,000 for Microsoft 365, according to Moneycontrol. Those are complaint counts, not a census of every affected mailbox. A company with 400 people on one tenant can suffer in silence while one frustrated user files a Downdetector report. Even so, a six-figure Outlook spike is why this jumped to the top of Indian tech desks on a Friday.
Microsoft has been posting on the public status page because administrators may be unable to open the admin center. That is a nasty loop. The person who is supposed to tell staff what is wrong cannot always see the admin console that usually carries the incident. If your IT lead is forwarding a public status link instead of an internal advisory, that is why.
What actually broke
Microsoft’s account, as reported by Moneycontrol, is mechanical. A set of servers failed automated health checks and were pulled out of service. The traffic those machines had been carrying moved onto the servers that were still up. Those remaining machines then struggled with the extra load and started returning connectivity errors.
Later, the company found that a process responsible for setting up secure connections was getting overwhelmed, so servers could not handle requests. That is why a simple retry often failed. The login was not “wrong.” The handshake that is supposed to make the connection secure was itself jammed.
Engineers restarted servers, redistributed traffic worldwide and rolled back recent configuration changes. Microsoft reported early gains from the restarts on Thursday, 12 November. Then it said those measures were not delivering a sustained recovery. The authentication and routing patch is the next step, not a victory lap.
Why the first fix did not stick
Business Today’s 10:20 am IST report is blunter about the failed recovery. Some servers that had been brought back online became unresponsive again once they started receiving traffic. Microsoft was analysing diagnostic data with its networking and platform teams to see what triggered that relapse.
The company then did two more things. It temporarily restricted certain types of traffic reaching the affected infrastructure in specific locations. And it started rebuilding a subset of affected servers using an earlier software configuration, to test whether that older build would stop the machines from falling over.
Earlier attempts had already included restarts, moving traffic off the sick infrastructure, and testing an alternative way to check server health. Business Today said those steps did not give the expected relief. Microsoft was looking for other ways to add capacity and to manage traffic imbalances. The company acknowledged that its efforts to improve serviceability were “not taking as expected.”
There is still no confirmed time for a full restore. Until the recovery stabilises, Business Today said users may keep seeing problems across Microsoft 365 apps.
What this looks like from an Indian desk
Friday is a bad day for a mail outage. Offers, invoice follow-ups, college placement mails and client decks all pile up before the weekend. If you are on a company Microsoft 365 tenant, your personal Gmail is not a substitute for the thread your manager is waiting on. If you are on Outlook.com as an individual, you are in the same incident: Moneycontrol said both business and individual users were disrupted.
A few practical reads from the two reports, without inventing a workaround Microsoft did not publish:
- Do not keep hammering the sign-in button. The failure is on Microsoft’s servers, and extra attempts were part of the load problem the company was trying to drain.
- If desktop Outlook, Outlook on the web and phone ActiveSync all fail together, that matches the Exchange Online description. It is not your Wi-Fi by itself.
- Teams chat may still work in some tenants while mailbox-backed features do not. Business Today said not every function is necessarily unavailable.
- Your admin may not have the admin center. Check the public Service Health Status page for incident MO1550821 rather than waiting for an internal mail that cannot be delivered.
- There is no cyberattack finding in the 13 November updates. Treat phishing mails that pretend to be “Microsoft support” with the usual suspicion. The outage itself is not evidence that someone stole your mailbox.
Two clocks, one outage
The two Indian reports are a few hours apart, and they should be read in order. Business Today’s story, updated 10:20 am IST, describes recovery that was still failing: servers coming back, then dying when traffic returned, traffic being restricted, and a subset of machines being rebuilt on an older configuration. Moneycontrol’s story, timestamped 13:51 IST, adds the 12:59 pm IST status note: a patch on an upstream authentication and routing component was showing positive stability on part of the infrastructure, with a plan to widen it, and a further update promised by 2 pm IST.
That is progress on paper. It is not an all-clear. The degradation label was still up. The patch had not been applied everywhere. And Microsoft had already celebrated early restart gains on Thursday before those gains faded. Anyone who tells you “it is fixed because they applied a patch” is ahead of the status page.
What is still unknown
Neither desk published a root-cause postmortem. Microsoft said that report comes after restoration. Neither story gave an India-only user count separate from the global Downdetector peaks. Neither named a city, an ISP or a single Indian company as the source of the failure. The incident is global, and India is feeling it because Outlook and Teams are the default work stack in a lot of offices here.
Also unstated: whether consumer Outlook.com and enterprise Exchange recovered at the same pace, which regions got the patch first, and whether Copilot outages were only the mail-connected features or the whole product. Stick to the service list Microsoft actually published.
What to watch next
The useful checkpoint was 2 pm IST on 13 November, the deadline Microsoft set for its next status update after the 12:59 pm note. If that update says the patch is moving to more regions and the degradation label drops, the Friday afternoon inbox rush might still happen. If servers fall over again once traffic returns, you are back in the loop Business Today described at 10:20 am.
Until the Post-Incident Report, the story is simple enough to tell a colleague: health checks pulled servers out, the rest got overloaded, secure-connection setup jammed, restarts did not last, and a routing and authentication patch was the first thing Microsoft was willing to call positive — on part of the fleet, with no clock for full recovery.
Comments (0)
Be the first to comment!