What the Tokyo Foundation said
The Foundation's English notice says a global Microsoft 365 outage that began Thursday afternoon was still running on Friday. It says that, from early on November 13 (JST), Microsoft 365 had been suffering a major global outage. As a result, the Foundation is "currently unable to reliably receive or review" messages sent by email or through its online contact form. It apologizes and asks for patience.
The English page doesn't say which Microsoft component is involved at the Foundation. It gives no start time beyond "early" on November 13, JST. It doesn't describe how the Foundation's mail or form is set up.
The Japanese notice gives more practical advice
The Foundation's Japanese-language notice adds guidance that the English copy leaves out:
- Urgent matters: call the Foundation by telephone. The Japanese notice points to its phone-number directory.
- Messages sent after the outage began: these may not have reached the Foundation.
- Next step: contact the Foundation again once service is restored.
The notice doesn't say whether messages are delayed, bounced or lost. Don't assume any one outcome. In practice, a sent email or a submitted form is not proof that anyone at the Foundation has seen it.
The wider outage
The Foundation's problem fits the broader picture. Reports from Thursday and Friday describe the following.
- Where it centers: UC Today reported that Microsoft opened Exchange incident EX1550543 at 16:17 GMT on Thursday, November 12, after users had trouble reaching Outlook mailboxes on the web, desktop and mobile.
- Mail flow: Microsoft also warned that inbound mail may be delayed, and that on-premises mail flow may be affected if it goes to or from Exchange Online. That matches the Foundation's worry about messages arriving.
- Connection methods: Microsoft's service text, quoted by ABC News (Australia), said users may be unable to access their mailbox using Outlook on the web, Outlook desktop (MAPI), Exchange ActiveSync (EAS), or REST-based connections, and email delivery may be delayed.
- Related services: ABC News listed other effects. Users may be unable to view recently used files in Microsoft 365 apps, and Defender for Office 365 Safe Links may be unable to verify URLs. It added that Microsoft Graph API requests that access Exchange Online data, such as mail, calendar and contacts, may time out.
- Services named by Microsoft: ABC7 listed Exchange Online, Teams, SharePoint Online, Copilot 365, Defender XDR, Planner, Intune and Defender for Office 365 among the affected services.
- Initial explanation: Microsoft's early statement was that a portion of infrastructure is experiencing elevated load across multiple regions. It also said it had begun redistributing traffic. Later coverage points to restart and recovery work, but the final root cause isn't established in the material I reviewed.
- Malicious activity: ABC News reported that Microsoft said the outage was not believed to be due to "malicious activity".
- Status as of Friday morning: UC Today said that, as of 07:25 GMT on November 13, the outage was still going, more than 15 hours after Exchange Online first failed, with no estimated time for recovery. Later ABC7 headlines mention "partial recovery across regions", so the situation was still changing. I can't confirm full restoration.
- Scale: Newsweek and others cited Downdetector, where almost 130,000 users reported problems accessing Outlook in the United States just after 1 p.m. That's a count of user reports, not a count of affected organizations or people.
The Foundation's own disruption is one organization's account of its effects. The wider coverage gives context but doesn't prove what caused the Foundation's specific problem.
Why IT teams should care
Most outage coverage is about staff who can't open Outlook. The Foundation's notice shows the other side: outsiders can't reach you. Public-facing inquiry channels are often built on the same cloud email, and the website can stay up while the inbox is unreliable.
Some practical points follow, based on general industry practice rather than anything the Foundation has said:
- Publish a non-email fallback. The Foundation's telephone route is a simple example.
- Post a status notice on a site that doesn't depend on your mail service. The Foundation did this with a news page in two languages.
- Keep notices consistent across languages. The English page lacked the phone and resend guidance, so an English-only reader would miss it.
- Tell senders to resend after recovery. Nobody should assume a message sent during an outage was delivered.
- Check your contact form's design. If it forwards into Exchange Online, a mail outage can silently swallow submissions. The Foundation hasn't said how its form works, so this is a general caution.
- Admins can follow the incident in the Microsoft 365 admin center. The incident IDs reported publicly include EX1550543 and MO1550821.
What senders should do
- If you wrote to the Tokyo Foundation after the outage began, assume it may not have arrived.
- For urgent matters, use the telephone numbers the Foundation publishes.
- For anything else, wait until service is restored, then resend.
Bottom line
The Foundation's notice is short, but it shows a real consequence of the outage. Its inbox and form can't be relied on, and its Japanese notice tells people to phone and to resend later. The outage's full scope, final cause and restoration time are still being reported, so treat any single figure with caution.