Microsoft Outage Enters Second Day, Disrupting Banks and Governments

A Microsoft outage has stretched into a second day, and the damage has spread well beyond inboxes. The disruption, which began on Thursday, has knocked out Outlook email, Microsoft Teams and the Copilot assistant for users worldwide, and the roster of affected organisations runs from a Swiss luxury house to a Wall Street bank to the Japanese government. For finance teams, the Microsoft outage is a live demonstration of how much of the working day now depends on a single supplier.
What has the Microsoft outage disrupted?
The failure has hit the tools businesses use to operate, not a peripheral service. Since Thursday, users have been unable to send or receive email through Outlook, with Microsoft Teams, Copilot and other Microsoft 365 services also affected. Many organisations said they could not carry out routine work or reach colleagues and clients. Public institutions were caught up alongside companies: doctors and the Houses of Parliament in the UK, police in Australia and the Japanese government all reported problems, and some regional NHS branches in the UK asked patients to telephone rather than email.
Which financial and corporate names have been hit?
The corporate roll-call is where the story turns material for investors. Richemont, the Swiss group behind Cartier and Chloé, briefly delayed its half-year results on Friday. Goldman Sachs experienced email disruption before finding a workaround, according to a person familiar with the matter, and the Gulf carrier Emirates warned that booking confirmation emails could be delayed. OpenAI and Anthropic both reported errors affecting their Microsoft 365 connectors. In Japan, local media reported that some banks and securities firms fell back on fax machines to confirm transactions, while the logistics group Sagawa Express suspended same-day reservations for its station and airport luggage services.
What caused it, and is this a cyberattack?
Microsoft has not disclosed a root cause, but it has ruled out foul play. Charles Lamanna, the company's executive vice-president for Copilot, Agents and Platform, said on X that there was no sign the incident stemmed from "malicious or cyber activity." By Friday the company reported further progress, with recovery partially completed in the Asia Pacific region and improvements to mailbox access and email delays, though it cautioned that some users might still see intermittent issues. One secondary risk is worth flagging for finance teams: Sophos, the cyber-security firm, warned that criminals often exploit high-profile outages with phishing messages posing as the affected company or a bank, so staff should treat unexpected Microsoft or banking communications with extra caution.
Why does one company's problem hit the whole economy?
This is the systemic question. The outage is the latest case of a single failure at a dominant infrastructure provider cascading across global business, following high-profile disruptions at Cloudflare and Amazon's cloud services last year. UK defence minister Luke Pollard said the government was assessing the damage and pressed for more resilient technology systems and faster recovery. The episode also rhymes with a structural shift in the compute market: as hyperscalers consolidate cloud and AI infrastructure, both the financial and the operational risks of leaning on a handful of them keep climbing.
Why This Matters to FinanceX Readers
For financial institutions, this outage reframes operational resilience as a first-order risk rather than an IT housekeeping item. When email, collaboration tools and back-office workflows all route through one vendor, that vendor's bad day becomes a continuity problem for results reporting, client communication and trade confirmation, as Richemont's delayed numbers and the resort to fax machines in Japan both show. Regulators in banking and markets increasingly expect firms to map and mitigate concentration in critical third parties, and a two-day global outage is exactly the scenario those rules anticipate.
The practical takeaways are unglamorous but urgent: documented fallback channels, tested business-continuity plans, and heightened vigilance against the phishing that tends to follow a crisis.

