Microsoft 365 outage disrupts trading communications worldwide

The disruption affected functions dependent on Exchange Online across Outlook, Teams and other Microsoft 365 products, while functions that did not rely on Exchange Online could remain available, according to Reuters.

Microsoft reported that most Teams calls and chats continued to work, although users had problems scheduling meetings and sending invitations, according to Cointelegraph. This meant the incident did not affect every Microsoft 365 function in the same way.

Microsoft said the incident originated in an issue introduced during an earlier network-capacity upgrade, which surfaced after a more recent network change, according to its Microsoft 365 Status update.

The company described the outage as a technical incident and said it was not related to malicious cyber activity or AI agents in the same status update. Further technical findings and preventive measures remain subjects for Microsoft's promised post-incident report.

Microsoft restored services gradually and validated stability at each stage instead of reconnecting all affected demand at once, according to the company's status explanation.

On November 14, Microsoft said it had restored service to the remaining affected customers and regions after an outage lasting more than 24 hours, Reuters reported.

The outage delayed work at trading firms, while some financial-market participants used telephone or fax communications to confirm transactions, according to Reuters.

For a centralized-exchange user weighing self-custody and on-chain perpetuals, the incident provides a reason to examine communication continuity separately from trade execution. The supplied reports establish disruption to communications and transaction-confirmation workflows, but they do not establish that a cryptocurrency exchange, custodian or DeFi operator suffered an order-processing or settlement failure because of this outage.

The disruption caused errors in ChatGPT's Microsoft 365 connector and failures involving email, calendar and search requests through Claude's Microsoft 365 connector, according to Cointelegraph.

Microsoft said the underlying incident was not caused by AI agents, according to its Microsoft 365 Status update. The connector failures were reported effects of the Microsoft 365 disruption rather than its stated cause.

The use of telephone and fax confirmations during the disruption shows that some market participants had to fall back to communication channels outside Microsoft 365, according to Reuters.

A trader reviewing a centralized exchange, self-custody wallet or on-chain perpetuals venue can check:

• Whether order execution, account access and transaction records remain available when email or calendars fail.
• Which independent channel handles urgent support, compliance questions and transaction confirmations.
• Whether API keys, wallet recovery material and two-factor authentication depend on one email provider.
• Whether the venue publishes a status page that is independent of its main communication suite.
• Which procedures apply when connected automation or AI tools lose access to email, calendar or search services.