Global disruption of Microsoft services hits Indian firms

Share on WhatsAppMore current affairs

EconomyScience & TechnologyGS 3

2

A global disruption of Microsoft services began on Thursday and continued into Friday. It affected email access and workplace applications in businesses, public...

A global disruption of Microsoft services began on Thursday and continued into Friday. It affected email access and workplace applications in businesses, public services and other organisations worldwide. Indian firms, from start-ups to multinationals, lost internal communication and customer support. The episode shows the risk of concentrating critical digital services in a few providers, and it bears on cyber resilience, digital sovereignty and critical information infrastructure.

Key Facts

·      Cause and scope:

o   Microsoft named Exchange Online (cloud email, calendar, contacts, tasks) as the primary service affected.

o   Some Microsoft Graph requests to Exchange Online data timed out, which hit dependent features in Teams, Copilot and SharePoint. Core Teams messaging and meetings largely continued.

o   Microsoft said it knew of no malicious activity behind the outage and promised a root-cause report after restoration.

o   Recovery was progressing: better in North America and Europe, encouraging in Asia-Pacific. Intermittent delays could continue, and a 48-hour timeout window protects delayed messages.

·      Impact in India:

o   A major telecom firm’s staff could not send service-disruption alerts to customers, and call-centre traffic rose.

o   A deep-tech start-up and a Big Four firm reported disrupted emails, Teams meetings and internal operations.

o   IndiGo and Akasa Air reported email support delays. Air India said flight operations were unaffected.

2

·      Impact abroad: government email disruptions in Singapore and Japan. In Britain, NHS staff handling emergency calls could not access patient details as usual, and prescriptions were delayed.

·      CERT-In advisory: a high-severity advisory on Friday on multiple Microsoft product vulnerabilities, including an Outlook flaw reported as actively exploited. CERT-In is separate from the outage, and no link is established.

·      Expert views: reduce dependence on external providers and build a diverse ecosystem, citing Germany’s regional choice of email providers (many using free and open-source software). Others urged backup channels, multiple providers and tested continuity plans.

Static Dimensions

·      Cloud and concentration risk: a few hyperscalers (Microsoft, Amazon, Google) host a large share of global workloads. A single fault can cascade across sectors. This is called systemic or concentration risk.

·      CERT-In: national nodal agency under MeitY for cyber incidents, set up under Section 70B of the IT Act, 2000. It issues advisories and the 2022 directions require reporting of incidents within six hours.

·      Critical Information Infrastructure (CII): Section 70 of the IT Act. The National Critical Information Infrastructure Protection Centre (NCIIPC) protects sectors like power, banking, telecom, transport and government.

·      DPDP Act, 2023: data fiduciaries must adopt security safeguards. Data localisation and cloud policy debates (MeitY’s MeghRaj cloud policy, empanelment of cloud providers) are linked.

·      Digital sovereignty and open source: India’s National Open Source policy and government use of indigenous email (NIC email) aim to reduce dependence. The India AI and digital public infrastructure approach favours interoperable systems.

·      Business continuity and disaster recovery (BCP/DR): redundancy, failover, multi-cloud, offline backups and regular drills.

·      Related incidents: the July 2024 CrowdStrike-Windows outage disrupted airports and banks globally and is a standard comparison.

Analysis

·      Single point of failure: the outage affected hospitals, airlines, telecom and governments because many depend on one vendor’s cloud. Email looks routine but supports alerts, customer service and emergency coordination.

·      Not a cyberattack, but similar effect: even without malice, availability failure harms the confidentiality-integrity-availability (CIA) triad. For essential services, resilience matters as much as security against hackers.

·      Business impact: delayed alerts, customer-support backlogs and lost productivity. Firms with alternative channels (IndiGo’s virtual assistant, Akasa Air’s call centre and social media) coped better. Air India’s rerouting of email shows planning helps.

·      Public-sector exposure: government and health services using commercial clouds face continuity risk and possible loss of control over data and uptime. The NHS example shows the human cost.

·      Sovereignty versus efficiency: diversification and open-source options raise resilience and bargaining power, but cost more, need skills and can create integration gaps. Total independence is unrealistic. A multi-vendor approach is more practical.

·      Regulatory gap: India has incident-reporting rules, but there is no dedicated framework treating major cloud and SaaS providers as systemic. Outage reporting, service-level obligations and transparency on root causes are limited.

·      Caution: the cause is not yet known. Conclusions should wait for Microsoft’s root-cause report.

Challenges

·      Vendor lock-in and concentration of critical services.

·      Limited visibility into vendor-side failures.

·      Low preparedness and untested continuity plans, especially in MSMEs.

·      Skill and cost barriers for open-source or in-house alternatives.

·      Overlap of outages with active vulnerability exploitation.

Way Forward

·      Mandate BCP/DR plans and periodic drills for CII and essential-service operators.

·      Encourage multi-vendor and hybrid architectures, with offline and alternate communication channels.

·      Define systemic cloud providers and require incident disclosure, SLAs and post-incident reports.

·      Promote indigenous and open-source options (NIC email, public cloud under MeghRaj) for government use.

·      Strengthen CERT-In and NCIIPC coordination; patch quickly on advisories.

·      Build skills and support MSMEs with affordable resilience tools.

Conclusion

Digital services are now essential infrastructure, so their failure is a governance issue and not just a technical one. India should combine vendor diversity, strong continuity planning and a clear regulatory framework to protect public services and businesses from provider-level failures.

Chat with us