Microsoft 365 Outage Update: Services Restored on November 14

Verified and updated: November 15, 2026, 12:15 a.m. AEDT (UTC+11); 1:15 p.m. UTC, November 14.

Microsoft says it has restored service to the remaining customers and regions affected by this week’s widespread Microsoft 365 outage. Its public service status page currently lists all products as operational, so the latest confirmed update is that the major disruption is over. Some users may still encounter delayed mail or tenant-specific issues as systems catch up; check your organisation’s service health feed for a more precise view.

The outage affected services including Outlook, Teams and Copilot. Microsoft attributed it to a technical issue connected to an earlier network capacity upgrade that surfaced after a later network change. The company said it had no indication the disruption was caused by malicious activity. The Associated Press reported Microsoft’s restoration statement and explanation.

Destaques

• Microsoft says service has been restored to remaining affected customers and regions.
• The public Microsoft 365 status page currently reports all products operational.
• Outlook, Teams and Copilot were among services disrupted during the global incident.
• Users with lingering problems should check their tenant’s Service health page before troubleshooting locally.

Is Microsoft 365 back online?

Yes. Microsoft’s latest public statement says it completed work on the underlying issue and restored service to the remaining impacted customers and regions. The public status page now shows all products operational. That is a broad service-level signal, not a guarantee that every account, device or organisation has recovered identically.

For business and education accounts, the most relevant check is the Microsoft 365 admin center. An administrator or a staff member with the appropriate service-support role can open Health > Service health to see incidents and advisories affecting their tenant. Microsoft says the dashboard also shows issue history and updates; if you cannot access the admin center, its public service status page can help check for known problems. Microsoft’s service health guidance explains these options.

What happened during the Microsoft outage?

Users around the world reported problems with Microsoft 365 applications and connected cloud services. Outlook access and mail flow were disrupted, while Teams, Copilot and other services also experienced interruptions or degraded features. The impact varied: an app could open while a dependent feature, sign-in path or mail delivery remained unreliable.

Microsoft linked the incident to a technical problem during an earlier network capacity upgrade that became apparent after a more recent network change. It said recovery proceeded gradually as engineers restored affected customers and regions. The Associated Press reported that the disruption was not attributed to a cyberattack or AI agents. Microsoft said it would provide a fuller post-incident report after its review; until that appears, further technical detail should be treated as unconfirmed.

What should you do if Outlook or Teams still has problems?

First, check whether the issue is listed in your organisation’s Service health dashboard. If it is, follow the incident updates and avoid repeatedly changing account or device settings while Microsoft is still reporting a service issue. If the dashboard is clear, try the affected service in its web version and compare with another network or device. This can help narrow down whether the problem is tied to one app, device or connection.

For Outlook, check whether new messages arrive and whether older messages are still queued or delayed. Avoid sending repeated copies of the same time-sensitive message; confirm delivery through an approved alternate channel if necessary. In Teams, verify whether the problem concerns chat, calling, calendar or file access rather than assuming the whole service is unavailable. If one feature remains broken, record the time, error message and affected service, then report it to your IT administrator or support team.

For Australian organisations, the immediate practical step is to confirm critical workflows have resumed: email delivery, meetings, shared files and any business process dependent on Microsoft 365. Microsoft’s operational indicator is encouraging, but organisations should use their own tenant status and normal monitoring to verify recovery. If Microsoft later publishes an incident report or a new status advisory, that could clarify residual effects and prevention steps; for now, no further recovery timeline has been announced.

Frequently asked questions

Is Outlook working again?

Microsoft says the affected services have been restored, and its public status page currently lists products as operational. Check your organisation’s tenant health for any remaining local issue.

Was the outage caused by a cyberattack?

Microsoft said it had no indication the incident was related to malicious activity. It described a technical issue associated with a network capacity upgrade and a later network change.

Where can I check Microsoft 365 status?

Use the public Microsoft 365 status page or, for work and school accounts, the Service health section in the Microsoft 365 admin center.