Bengaluru tech firms hit hard by Microsoft outage

Bengaluru: Late on Thursday night, as US offices woke up to dead inboxes, Bengaluru’s late shifts felt it too. Outlook, Microsoft 365, Teams and Copilot went down, with Outlook outage reports peaking at nearly 130,000 on Downdetector..'Not going as expected': Microsoft global outage continues to hit email, other apps.Sambratha Shetty, COO, Synergia Foundation, said that for a city whose economy runs on serving global clients, this is no minor inconvenience. Bengaluru’s IT firms, startups and global capability centres co-ordinate across time zones through email, Teams calls and shared files. When those stop, client deliveries slip, support queues pile up, and teams sit idle. For outsourcing contracts bound by strict service-level agreements, even a few hours of downtime can mean penalties and strained client trust.Microsoft blamed elevated load on parts of its infrastructure and said there was no indication of malicious or cyber activity. "That is the worrying part: no attack was needed at all. And another major Azure disruption struck only in October. Even OpenAI and Anthropic reported problems with their Microsoft connectors, showing how many services share the same pipes," Shetty said.Bengaluru’s tech leaders should treat cloud failure as certain, not hypothetical. That means backup communication channels, multi-vendor setups and regularly tested continuity plans. The city that builds resilient systems for the world must build them for itself, Shetty added.On Friday morning, techies in Bengaluru logged in ready to clear overnight mails, but Outlook refused to open. No inbox, no calendar, no Teams. Refresh. Restart. Still nothing. Meetings vanished, approvals stalled, clients waited, managers panicked.IT services firms including Infosys and Cognizant sent internal messages to their employees saying that they would keep them posted once Microsoft Outlook is fixed.Cognizant told employees, "Ongoing global outage: Microsoft 365 Services (Outlook, Teams, SharePoint, Copilot, SSO based Authentication) Status: Active- phased recovery in progress."Infosys sent SMSes to employees saying, "It's been observed that Multiple MS services are down including Exchange online, Copilot, Purview, SharePoint. While Teams is working, Microsoft is working on the restoration of the affected services."A user posted on X saying that "Today you knocked Outlook and Teams offices for hours, and millions of Americans couldn't email their boss, join their meetings or run their businesses. You charge us every single month. You push us onto your cloud. We deserve better than a vague status update."Ben Mudie, Field CTO, APAC Tenable said, “When essential tools become unavailable, employees naturally look for ways to keep working. The security risk is that temporary workarounds, such as personal email accounts or unapproved file-sharing services, can move sensitive business information beyond an organisation’s visibility and control. Disruption can also create opportunities for impersonation. An urgent request arriving through an unfamiliar channel, or a message offering to restore access, deserves extra scrutiny."An outage alone does not establish that a cyberattack has occurred. But it does underline why business continuity and cybersecurity need to work together. Employees need clear, approved alternatives so they can remain productive without exposing company data or bypassing security checks, he added.Govind Rammurthy, CEO & Managing Director, eScan, said, today's Microsoft 365 outage, affecting users across 74 countries for over eight hours (and ongoing), is a stark reminder of the fragility that comes with deep dependence on a single cloud provider. It is akin to a stack of cards forming a pyramid - move one card and the whole structure comes down! "When Outlook, Teams, Copilot and Exchange Online go down simultaneously, organisations don’t just lose email. They lose their entire operational backbone, communication, collaboration, compliance, and AI productivity, in one stroke," he said. The cause here was not cyberattack. It was an internal process failure. This matters because it shows us that the risk isn’t always a threat actor. It’s the architecture itself, he further said.When one provider underpins nearly every critical workflow, any failure, whether from misconfiguration, overload or a network change, cascades instantly and globally. The lesson isn’t to abandon cloud. It’s to design for resilience, to create a minimal/operational backup, atleast for priority communications. Organisations must maintain fallback communication channels, ensure critical workflows have offline or multi-provider alternatives, and test recovery procedures before an outage forces the issue. Single-vendor dependency, however convenient, is a concentration risk that today’s eight-hour outage has demonstrated very visibly, he added.