Exchange Online disruption reached desks
Microsoft's status account was investigating Exchange Online access problems on 12 November 2026 as a 12-hour global Microsoft 365 outage disrupted financial operations. Downdetector reports in the US rose above 130,000 at the peak, before the effects reached Asia-Pacific business hours. Teams, Outlook and Copilot were also affected.
Japanese broker SBI FX Trade told clients that Outlook might not deliver important login and execution messages, and advised them to check their trading tools instead. Golden Way (GW) Securities, which operates FXTF, said login codes still worked but email enquiries were unavailable. Gaitame Finest said it could not review or answer contact-form messages because its customer enquiry process uses Microsoft 365.
Fallbacks exposed operational dependencies
Brokerages in Singapore and India warned of substantial customer-support delays, according to Bloomberg. At CMC Markets in Singapore, staff used phone calls and WhatsApp to get around automated online processes. The disruption left firms relying on communication routes outside the affected services, as Finance Magnates reported.
In Japan, settlement confirmations also required manual handling. Bloomberg reported that desks at firms including BNP Paribas Asset Management processed settlements by hand.
Portfolio managers at hedge fund Blue Edge Advisors said the incident cut them off from research and trading platforms that used email authentication. Kalshi made light of the disruption on X, suggesting Japanese markets had been pushed back to fax machines.
| Measure | Reported figure |
|---|---|
| Outage duration | 12 hours |
| Downdetector reports at the US peak | Over 130,000 |
The integration question
For operations teams, the incident puts the dependencies between identity, communications and trading workflows in focus. Can clients still receive access or execution notices if email is unavailable?
Can support teams accept and track enquiries through an independent route? If confirmations need manual processing, how are those actions recorded and reconciled once services return?
The report does not specify how many messages or settlements were delayed, or how long each firm's fallback lasted. Operators should check their own runbooks for email-authentication failure, confirm who can authorise manual settlement handling, and establish how queued messages and work completed offline will be reviewed.
Platforms · Software · Providers · Markets