Microsoft 365 Outage Disrupts Outlook and Teams as Recovery Efforts Continue
A Microsoft 365 outage that began on 12 November has disrupted email and other connected services, with Microsoft continuing recovery work on Friday morning.
Microsoft’s public status page still listed service degradation in an update timestamped 08:57 SAST on 13 November. The company reported marginal success in recovery efforts and said it was expanding capacity using virtual machines. Full restoration had not been confirmed in that update. Microsoft service status
Which services are affected?
Microsoft identifies Exchange Online as central to the disruption. Users may experience mailbox connection problems or delayed email delivery.
The company’s detailed notice also describes problems affecting functions across Copilot, Planner, To Do, education tools and other connected services.
However, the impact varies by feature. Microsoft says most core Teams functions, including calls, meetings and standard channel messaging, remain functional. Calendar functions that depend on Exchange Online may fail. Files stored directly in SharePoint Online remain accessible. Microsoft’s detailed incident notice
This distinction matters for readers deciding whether to postpone a meeting, change a communication channel or ask colleagues to check a particular task.
How did the outage develop?
BleepingComputer reports that the broader Microsoft 365 incident began at 20:26 SAST on Thursday, following earlier Exchange Online connectivity problems.
Microsoft initially reported elevated infrastructure load, then explained that unexpectedly unavailable servers were placing additional pressure on the remaining systems.
Recovery measures included pausing deployments, redirecting connection traffic and restarting affected servers. An earlier update described limited recovery as some capacity returned.
The reporting also distinguishes a separate Teams disruption earlier on Thursday, which Microsoft said had been resolved. That earlier incident should not be confused with the wider Microsoft 365 problem. BleepingComputer’s outage report
Microsoft’s latest public notice said it was not aware of malicious activity causing the incident. That statement reflects the investigation’s current position rather than a completed technical assessment.
What does this mean for South African users?
The disruption is relevant to South African organisations that depend on cloud email, shared calendars and connected workplace applications.
However, the sources reviewed do not establish how many South African customers are affected. A worldwide incident does not mean every organisation, account or application experiences the same problem.
For example, being able to join a meeting does not necessarily mean calendar invitations are working normally. Equally, a colleague’s successful login does not establish that your organisation’s affected functions have recovered.
Check the specific service and task involved before assuming that normal operations have resumed.
Helpful steps while services recover
The following are practical continuity suggestions, rather than a technical fix for Microsoft’s infrastructure:
- Preserve copies of unfinished work and important messages where your organisation permits.
- Use an approved alternative channel for urgent communication.
- Confirm receipt of time-sensitive messages directly when delivery is uncertain.
- Record affected tasks and error messages for your IT support team.
- Follow your organisation’s instructions before changing account settings or reinstalling applications.
If a meeting invitation cannot be updated, explain the arrangements through a working channel. For deadlines involving customers, students or suppliers, agree on an alternative submission method and document the revised arrangement.
Keep confidential information within approved systems. Moving work to a personal account may create problems with access, recordkeeping or organisational rules.
For team managers, a brief shared update can reduce duplicated troubleshooting and help colleagues prioritise urgent work during the disruption.
When services become available again, review pending messages and calendar changes before resuming routine work. A short check can help identify tasks that need to be repeated or confirmed.
How to check Microsoft 365 service health
Microsoft recommends checking service health before spending time troubleshooting a known cloud incident.
Administrators can open the Microsoft 365 admin centre, then select Health > Service health. The dashboard provides affected services, incident updates and information relevant to the organisation.
Microsoft also directs users to its public status page when administrators cannot access the admin centre. Relevant incident references include EX1550543 for Exchange Online and MO1550821 for the broader disruption. Microsoft’s service health guidance
Check the update timestamp as well as the status label. Microsoft distinguishes degraded performance from confirmed restoration, so partial recovery should not be presented as an all-clear.
What happens next?
Microsoft says it will provide further root-cause information in a post-incident report after mitigation.
Readers should consult the official service status page for subsequent developments. This report reflects the timestamped update above and does not establish that every affected service has recovered.