loader image

When the Digital World Goes Offline: The Microsoft Outage and its Implications on Law of Service And Limitation

When the Digital World Goes Offline: The Microsoft Outage and its Implications on Law of Service And Limitation

When technology fails, does the law take notice?

By Abhishek Garg*, Yash Gaiha** and Naman Mehta***

Microsoft Outage and Law of Limitation

1. Introduction

The law has increasingly embraced technology. From the filing of cases before courts to the receipt of statutory notices, orders, summons and other communications, electronic communication has become integral to the administration of justice.

Today, an email is much more than a mere means of communication. Its date and time can determine whether a notice has been issued within limitation, whether an appeal has been filed within time, whether a party has been afforded an opportunity of hearing and, in certain circumstances, whether a proceeding is maintainable at all.

It is ironic that, while the legal framework in India has progressively adopted electronic modes of communication, it must now contend with the possibility that the very mode of service on which it relies may itself fail without warning.

The Microsoft outage of 12.11.2026 to 14.11.2026, an unprecedented event, illustrates this problem well. What initially appeared to be a technical inconvenience soon developed into a significant disruption of communications, raising an unusual question:

What happens when the law requires a communication to be sent within a prescribed period, but the infrastructure requisite for doing so becomes suddenly unavailable?

2. The Microsoft Outage: Brief Facts and Consequences

According to the Report dated 15.11.2026 published by Microsoft Corporation[1], on 12.11.2026, users across the globe began to experience widespread difficulty in accessing Microsoft 365 services, including Exchange Online, and were unable to access their mailboxes through Outlook, or to use Copilot, Teams, SharePoint, OneDrive, and other applications.

Microsoft has attributed the outage to a combination of three circumstances: a latent defect, dating back to July 2026, in the internal servers used by the Microsoft 365 networking gateway; a significant increase in the load on the primary gateway, after Teams traffic was moved to it approximately fifteen hours before the outage; and the unavailability of approximately 14% of the gateway’s server capacity owing to an unrelated issue on the preceding day. Individually, these circumstances might not have resulted in a major disruption. Their combined effect, however, triggered a cascading failure and, at its lowest point, more than 80% of the affected server fleet had become unresponsive.

Recovery was particularly complicated because servers brought back online were overwhelmed by the accumulated traffic and stopped responding again. Microsoft was therefore required to restore services gradually.[2]

Practical consequences: Emails that were never sent or emails that never arrived

Different users experienced the outage in different ways:

● Some emails that were attempted to be sent were not transmitted and remained in the drafts/outbox folder.

● Some senders received bounce-back or delivery-failure notifications.

● Some emails were sent (at least in sender’s mailbox) but were never received by the recipients.

● Certain emails were held in delivery queues and were eventually delivered once services began to recover.

● Some users experienced mailbox functions becoming available and unavailable at different times.

Even as Outlook began to recover, delays in delivery continued, and it could not safely be assumed that every email would immediately reach its intended recipient.[3]

The practical difficulty was thus not merely that users could not access their inboxes. There was considerable uncertainty as to the actual status of communications: whether they had been transmitted, whether they had reached the recipient’s server, whether they were merely delayed, or whether they had failed altogether.

Microsoft stated that it extended the email timeout window as a preventive measure, so that delayed messages would not be permanently lost merely because the delivery window had expired while it cleared the accumulated backlog.[4] The report dated 15.11.2026 records that the outage lasted approximately 23 hours and 50 minutes (from 04:20 P.M. UTC on 12.11.2026 to 04:10 P.M. UTC on 13.11.2026, i.e., from 09:50 P.M. IST on 12.11.2026 to 09:40 P.M. IST on 13.11.2026), although residual disruptions continued until Microsoft confirmed restoration of its services on 14.11.2026.

While email communications take place across several platforms, Microsoft is undoubtedly a major player, particularly among organizations. As per some sources[5], Microsoft 365 is used by over 3.7 million companies worldwide.

Consider a taxpayer using Gmail who is to be served with a notice by a statutory authority using Microsoft Outlook. Although the taxpayer does not use Outlook, the receipt of that communication may nevertheless be affected by an outage on the sender’s side.

In other words, the impact of an email failure is not necessarily confined to the direct users of the affected provider. It may extend to recipients on entirely different platforms, depending on the infrastructure through which the communication is initiated and transmitted.

3. Dependence on Electronic Communication under the Indian Legal Framework

Several enactments expressly provide for electronic modes of communication for the service of documents. These include:

3.1 Bharatiya Nagarik Suraksha Sanhita, 2023

Sections 63 and 64 of the Bharatiya Nagarik Suraksha Sanhita, 2023 (“BNSS”) permit a Court’s summons to be issued in electronic form bearing the image of its seal or a digital signature, and the proviso to Section 64(2) allows such a summons to be served by electronic communication in such form and manner as may be prescribed by the State Government. Section 70(3) deems a summons so served to be duly served, and Section 530 permits the issuance, service and execution of summons in electronic mode.

Delhi, for instance, has notified the BNSS (Service of Summons and Warrants) Rules, 2025, which permit Court summons and warrants to be served by electronic means such as email and WhatsApp.

3.2 Central Goods & Services Tax Act, 2017

Section 169(1) of the Central Goods and Services Tax Act, 2017 (“CGST Act”) recognizes email as one of the modes of service of any decision, order, summons, notice or other communication, by sending it to the email address provided at the time of registration or as amended from time to time.

3.3 Income Tax Act, 2025

Section 501 of the Income Tax Act, 2025 permits the service of notices, summons, requisitions, orders and other communications by electronic record in the manner provided under Chapter IV of the Information Technology Act, 2000 (“IT Act”).

Rule 232 of the Income Tax Rules, 2026 further prescribes the email addresses to which such communications may be delivered or transmitted, including the email address furnished in the return of income and the address available on the e-filing portal.

3.4 Negotiable Instruments Act, 1881 and Payment and Settlement Systems Act, 2007

The Negotiable Instruments Act, 1881 (“NI Act”) prescribes strict timelines for the issuance of notice, which makes the date of service very crucial. Proceedings under the NI Act are linked to the BNSS, which allows service by electronic communication. Thus, under the NI Act read with the provisions of the BNSS, notices can be served through email.

Under the proviso to Section 138, the payee or the holder in due course of the cheque, as the case may be, is required to make a demand for payment by giving a notice in writing to the drawer within thirty days of the receipt of information from the bank regarding the return of the cheque as unpaid. The drawer is then required to make payment of the said amount within fifteen days of the receipt of the said notice.

There are many other important statutes, such as the Prevention of Money Laundering Act, 2002, Payment and Settlement Systems Act, 2007 and so on which provide for email communication as a valid mode of service, and where limitation depends upon the date of issuance, service or communication.

4. Service of Electronic Communications: Dispatch and Receipt

A notice issued by a statutory authority, a summons transmitted during an investigation or an order communicated to a litigant may carry significant legal consequences. The validity of subsequent proceedings, the computation of limitation and the availability of statutory remedies may all depend upon the point of time at which such communication is deemed to have been served. This gives rise to an important question:

Where the delivery of an email is delayed or disrupted owing to a failure/unavailability of the underlying email infrastructure (that too without the infrastructure operator itself being aware of it), can such communication be said to have ‘issued’ and/or the addressee nevertheless be treated as having been duly ‘served’?

An email is not necessarily delivered at the precise moment when the sender clicks the ‘Send’ button. There may be an interval between the initiation of transmission, the communication reaching the relevant computer resource, and its eventual availability to the addressee.

The answer must therefore be examined in the light of the IT Act, which provides the framework governing the dispatch and receipt of electronic records, read alongside the relevant principles under the Indian Contract Act, 1872 (“Contract Act”).

4.1 Information Technology Act, 2000

Section 13 of the IT Act governs the time and place of dispatch and receipt of electronic records, save as otherwise agreed between the originator and the addressee. Under Section 13(1), dispatch occurs when the electronic record enters a computer resource outside the control of the originator. Under Section 13(2), receipt occurs when the record enters the computer resource designated by the addressee or, where none is designated, the addressee’s computer resource; and where it is sent to a resource other than the designated one, when it is retrieved by the addressee.

The fact that an addressee has not personally opened or read an email does not necessarily mean that the electronic record has not been received. Equally, the mere fact that the originator attempted to send an email does not necessarily establish that it was dispatched.

4.2 Indian Contract Act, 1872

Section 4 of the Contract Act embodies the postal rule: communication of an acceptance is complete as against the proposer when it is put in a course of transmission to him so as to be out of the power of the acceptor. However, it applies specifically to proposals, acceptances and revocations, and cannot be treated as an automatic rule governing every statutory notice or legal communication.

Read together, these provisions raise the following question in cases of technical failure:

At what precise point did the electronic record leave the control of the originator and enter the designated computer resource of the addressee during the outage from 12.11.2026 to 14.11.2026, when different users were faced with different kinds of problems as enumerated above?

4.3 Judicial Interpretation of Dispatch: Suman Jeet Agarwal[6]

The decision of the Hon’ble High Court of Delhi in Suman Jeet Agarwal v. Income Tax Officer assumes particular significance in the present context. The case concerned notices under Section 148 of the Income Tax Act, 1961, which were generated on 31.03.2021, the last date for issuance of such notices under the limitation regime then applicable. The Department contended that, since the notices had been generated and digitally signed on the Income Tax Business Application Portal on 31.03.2021, they were to be treated as having been issued within limitation. However, the actual electronic dispatch of the notices, in certain categories of cases, took place on or after 01.04.2021.

The Hon’ble High Court examined Section 13 of the IT Act and held that the mere generation or digital signing of a notice did not suffice, and that there had to be an actual act of dispatch. In the case of electronic communication, dispatch occurs when the email leaves the servers of the Department and enters a computer resource outside the control of the Department, that is, the addressee’s designated email infrastructure.

The judgment lays down the principle that the date of creation or generation of an electronic communication is not necessarily the date of its issuance, and that the actual date of dispatch must be established.

The above principle was also applied by the Hon’ble High Court in the case of Usha Gupta v. Income Tax Officer, Ward 11(1) & Anr.[7], where, although the notice was dated 30.06.2021, the email showed that it had been sent at 12:12 A.M. on 16.07.2021. The Department was unable to produce any material to establish that the notice had been issued earlier. Accordingly, the Hon’ble High Court set aside the notice as barred by limitation.

4.4 Application to the Microsoft Outage

If an email is generated on the last day of limitation but remains within the sender’s system or is not actually dispatched until the following day on account of a technical failure, the sender may not be able to rely upon the earlier date merely appearing on the document.

On the other hand, where the sender establishes that the email had already left its system and entered a computer resource outside its control before the expiry of limitation, a subsequent delay in the addressee’s ability to access the mailbox raises a different question.

The precise statutory requirement – whether it requires issuance, dispatch, service or receipt – will therefore be decisive.

5. Limitation: Whether the Outage Affords Any Protection

The next question is whether the outage can afford any protection to a person whose period of limitation expired on 12.11.2026 or 13.11.2026.

5.1 Closure of Court or Office: Section 10 of the General Clauses Act, 1897 and Section 4 of the Limitation Act, 1963

Section 10 of the General Clauses Act, 1897 provides that, where any act or proceeding is to be done or taken in any Court or office within a prescribed period and the Court or office is closed on the last day, it shall be considered as done in due time if done on the next day on which the Court or office is open. Section 4 of the Limitation Act, 1963 makes a similar provision for suits, appeals and applications. Both provisions are concerned with the closure of the Court or office, and a technology outage is not expressly equated with such closure.

A Court that is physically open while its electronic infrastructure is unavailable presents a different factual situation from a Court that is formally closed.

It is certainly arguable that, where electronic filing is the only permitted or practically available method and the relevant system becomes unavailable, the litigant ought not to be prejudiced merely because the technological infrastructure has failed.

5.2 Condonation of Delay and Force Majeure: Section 5 of the Limitation Act and Sections 107(4) and 168A of the CGST Act.

Section 5 of the Limitation Act permits an appeal or an application to be admitted after the prescribed period if the appellant or the applicant satisfies the Court that he had sufficient cause for the delay. Its application is not universal: it does not generally extend limitation for suits, and special statutes may prescribe their own restrictive rules.

For instance, under Section 107(4) of the CGST Act, the Appellate Authority may, if satisfied that the appellant was prevented by sufficient cause from presenting the appeal within the prescribed period of three months, allow it to be presented within a further period of one month.

Another provision worth considering in this context is Section 168A of the CGST Act, which empowers the Government, on the recommendations of the Council, by notification, to extend the time limit specified in, or prescribed or notified under, the Act in respect of actions which cannot be completed or complied with due to force majeure. The Explanation thereto defines ‘force majeure’ to mean a case of war, epidemic, flood, drought, fire, cyclone, earthquake or any other calamity caused by nature or otherwise affecting the implementation of any of the provisions of the Act.

The provision could become relevant if an extraordinary technology failure is regarded as sufficiently serious to warrant governmental intervention. However, it does not operate as an automatic extension in favour of an individual merely because a service provider has suffered an outage; a notification by the competent Government would be necessary.

5.3 Service by Post: Section 27 of the General Clauses Act, 1897

Section 27 of the General Clauses Act, 1897, which raises a presumption of service when a document is sent by registered post, is concerned specifically with service by post. It cannot be treated as a general presumption that every email is received merely because the sender claims to have dispatched it.

6. What happens where limitation expires on 12.11.2026 or 13.11.2026?

Consider an assessee who is required to submit a reply to a notice through email by 13.11.2026. The assessee prepares the reply well in advance but, owing to the Microsoft outage, the email remains in the Drafts folder or is not sent successfully.

Alternatively, the assessee sends the communication before the deadline, but the recipient’s mailbox, hosted by Microsoft, does not accept or process the communication until services recover.

Would the assessee be treated as having defaulted?

The answer cannot be the same in every situation.

(i) The first question is whether the communication was actually dispatched within the period of limitation. Section 13 of the IT Act and the principle laid down in Suman Jeet Agarwal (Supra) would be relevant.

(ii) The second question is whether the applicable legislation requires only dispatch or actual service or receipt. The two are not necessarily interchangeable.

(iii) The third question is whether the person affected could reasonably have used another legally permissible mode of communication, such as the relevant portal, an alternative email service, registered post or physical filing.

(iv) The fourth question is whether the person can establish that the failure was directly attributable to the outage and that reasonable diligence was exercised.

A mere assertion that Microsoft suffered an outage may not, by itself, establish that a particular email was not transmitted or received.

Equally, a person ought not automatically to be treated as having defaulted merely because a communication failed to reach its destination owing to a failure of the service provider’s infrastructure, particularly where the person can demonstrate a timely attempt and the absence of any effective alternative.

The courts will have to examine these circumstances in light of the language of the applicable statute.

Conclusion: Can the law accommodate a failure of the very technology it recognizes?

The law has progressively recognised email and electronic records as legitimate modes of communication. Yet it has not necessarily developed a comprehensive framework to deal with a widespread failure of the infrastructure on which electronic service depends.

It is almost amusing that a dispute on limitation, which would traditionally have turned on when a letter was posted or delivered, may now require an examination of server logs, delivery acknowledgements and the date and time at which the message entered a computer resource outside the control of the sender.

But the consequences are anything but amusing for a person who may lose a statutory remedy because an email could not be transmitted.

The outage also demonstrates why a distinction must be maintained between the legal act of dispatching a communication and its actual receipt. An email sitting in Drafts, an email successfully dispatched but awaiting delivery, and an email already received by the addressee’s server but inaccessible through an application are three legally distinct situations.

For those whose limitation periods expired on 12 or 13 November 2026, the incident may well furnish grounds for an argument based on Section 13 of the IT Act, the principles laid down in Suman Jeet Agarwal, the applicable provisions of the Limitation Act and the doctrine of sufficient cause, wherever available.

Whether such arguments will ultimately succeed is another matter. The existence of an outage does not automatically extend every statutory deadline, and the particular requirements of each enactment will have to be examined.

It will be interesting to see how such issues are raised before the Courts, how the authorities respond, and whether the judiciary treats the failure of a dominant electronic service provider as sufficient cause for protecting parties who were genuinely prevented from complying with statutory requirements within time?

The law may have embraced the digital age, but the digital age has now reminded the law that even technology is not infallible.


*Abhishek Garg – Advocate-on-Record, Supreme Court of India, Managing Partner – AGS Legal

**Yash Gaiha – Principal – AGS Legal

**Naman Mehta – Associate – AGS Legal

[1] Preliminary Post Incident Report for Microsoft 365 dated 15.11.2026, published by Microsoft Corporation

[2]Microsoft identifies months-old bug as a root cause of global outage | Microsoft | The Guardian

[3]Why is Microsoft’s outage lasting so long and will emails be lost?

[4]Microsoft 365 Status (@MSFT365Status) / X

[5]Microsoft 365 Usage and Security Statistics for 2026

[6] 2022 SCC OnLine Del 3141

[7]WP(C) No. 12278 of 2022