South African businesses and public institutions experienced disruptions to their operations following a global Microsoft outage that affected email and workplace applications, exposing the risks of relying heavily on a single technology provider.
The outage, which began on Thursday, 12 November 2026 affected Microsoft’s cloud-based services, including Outlook, Exchange Online, Teams and Copilot. The disruption left organisations struggling to communicate with customers, employees and suppliers, with some having to redirect enquiries to alternative channels.
The South African Revenue Service (SARS) warned taxpayers and traders that the outage could affect access to its Microsoft applications.
“Please be advised that Microsoft is experiencing a global service outage, which may affect access to Outlook, Teams and other Microsoft 365 applications,” SARS said in a notice on November 13.
The City of Cape Town also confirmed that its Microsoft 365 environment was affected, warning users that they could experience difficulties accessing emails, sending and receiving messages and retrieving documents through OneDrive.
Businesses turn to alternatives
Several private sector companies also reported disruptions, including Absa, Eskom, FlySafair and medical scheme Bestmed.
Absa warned that some employees were experiencing intermittent difficulties accessing Microsoft applications, including email and Copilot.
“Microsoft is actively working on a resolution, and our tech teams are monitoring the situation closely,” the bank said.
State-owned power utility Eskom confirmed that its email services were affected by the worldwide disruption to Microsoft’s Exchange service.
The utility advised customers to use alternative communication channels, including its telephone line, WhatsApp, Alfred chatbot and USSD service to access assistance.
Domestic airline FlySafair also reported disruptions to its email services, saying it was temporarily unable to receive or send emails.
The airline directed customers to its call centre and WhatsApp service while Microsoft worked to restore its systems.
Bestmed also notified customers that its email communications had been affected. JSE-listed fintech company Lesaka Technologies and financial services group Momentum Group were among other businesses reported to have experienced disruptions.
The extent of the financial losses and operational delays experienced by the affected organisations has not been publicly quantified.
Dependence on one technology provider
Technology analyst Arthur Goldstuck said the incident exposed how dependent businesses had become on Microsoft’s interconnected infrastructure.
Goldstuck questioned why the company’s backup systems had not been able to prevent the disruption from spreading across its services and regions.
“One would expect there to be backups that allow the servers to kick in immediately when it fails in one place and then comes up again in another place,” he said.
He argued that the failure of underlying server infrastructure could affect multiple services that depend on the same systems.
Smaller enterprises that rely on cloud-based platforms for daily operations, the incident raises questions about business continuity planning.
Alternative communication channels, independent and data backups could help organisations maintain essential operations when their primary technology providers experience disruptions.
Microsoft attributed the incident to a technical problem associated with an earlier network capacity upgrade that surfaced following a subsequent network change.
Microsoft also said it was not aware of any malicious activity causing the incident.
As part of its recovery efforts, the company adjusted network traffic, restarted affected infrastructure and applied configuration changes to improve server stability.
The technology giant apologised to customers and partners for the disruption.
“We are deeply sorry for the disruption this incident has caused our customers and partners,” Microsoft said.
On Saturday, November 14, the company said it had addressed the underlying issue and restored services to the remaining affected customers and regions. However, it continued monitoring delayed email messages and service performance.
Microsoft said it would publish a post-incident report outlining the incident and its response.


























































