Cybersecurity update: Outlook outage triggers reporting obligation
Please confirm you are human to start the audio.
Authors
The Austrian NISG 2026 has been in force since 1 October 2026. With the global outage of Microsoft 365 and Exchange Online since the evening of 12 November 2026, many group IT service providers are now facing a very concrete question for the first time: Are we obligated to report?
In addition to the NISG 2026, Commission Implementing Regulation (EU) 2024/2690 applies directly. It specifies certain digital service providers when a security incident is significant and therefore subject to mandatory reporting. An incident is significant, in particular, if the managed service is completely unavailable for more than 30 minutes. Limited availability lasting more than one hour is equally significant if it affects more than 5% of users in the EU or more than 1 million users. Whether an attack has occurred is irrelevant: even a purely technical outage may be a significant security incident.
In many groups, a dedicated IT company runs operations centrally. It holds the contract with the cloud provider, provides Exchange and Outlook to the other group companies, and handles any service disruptions. As such, it qualifies as a managed service provider. If its service has been down for more than 30 minutes, the reporting obligation falls primarily on the IT company itself and not on the group companies that merely use the service. The same applies to anyone operating Exchange services for others.
An early warning would therefore have to be filed within 24 hours. Typically, this would have been by November 14, 2026, at the latest. Failure to register does not exempt a company from the obligation to report.
Downtime for each service should be documented, its significance briefly assessed, and, in case of doubt, an early warning submitted. An unnecessary early warning presents less risk than a missed report.