Skip to main content
OutageMicrosoft 365·1 March 2025

Microsoft Outlook outage March 2025: a problematic code change took email down

On 1 March 2025 Outlook, Exchange Online and Teams failed for users worldwide, with more than 35,000 Downdetector reports. Microsoft reverted a suspected code change and later blamed a problematic code change.

By APPNEURAL Editorial2 min read

Quick answer

On 1 March 2025 Outlook, Exchange Online and Teams users around the world hit failures for several hours, and Downdetector recorded more than 35,000 reports. Microsoft said it had identified a suspected code change and reverted it to restore service, and later blamed a problematic code change for the outage.

Key facts

Date
1 March 2025, from about 4:00 p.m. US Eastern
Services
Outlook, Exchange Online, Teams
Reports
More than 35,000 on Downdetector
Cause
A problematic code change, reverted by Microsoft

What happened

On the afternoon of Saturday 1 March 2025, US Eastern time, users began reporting that Outlook would not connect, and problems spread to Exchange Online and Teams. More than 35,000 reports reached Downdetector.

Microsoft said it had identified a potential cause and reverted the suspected code to alleviate the impact. It later attributed the outage to a problematic code change. Reported end times differ between outlets, but service recovered the same evening after the rollback.

The pattern

A code change made by the vendor, for every customer at once, stopped email for every customer at once. It is the same shape as the October 2025 Azure Front Door outage and the November 2026 outage, which Microsoft traced to a defect in a July update.

What to do now

  • Write down what happens when email is down: who decides, which channel staff switch to and how customers are told.
  • Keep a second way to reach your team and customers that does not depend on the same vendor, and test it before you need it.
  • List the business processes that stop when one vendor's service stops: invoices, password resets, approvals, bookings.

Our suggestion

Your own suite is not stopped by a shared platform's outage

APPNEURAL Suite is installed for your business as its own installation, in your own cloud account and on your own domain. It is not one tenant among millions on Microsoft 365's shared service.

  • A Microsoft 365 outage does not take your suite down with it.
  • Updates reach your suite when you decide, so a change made for millions of other customers does not land on you in the middle of a working day.
  • Mail, chat, calling and meetings in one suite on your own domain, so your team keeps a way to work and to reach customers.
  • A one-time payment instead of per-user monthly fees, with CRM, billing, payroll and 95+ business apps included.

No system can promise zero downtime. Your suite runs on a cloud provider, which can have problems of its own. The difference is that you are not sharing one installation with millions of other businesses. Running costs still exist: your cloud account, email sending and AI usage are billed by those providers at their own prices, straight to you. Ask us which updates and support your quote includes.

Frequently asked questions

What caused the Outlook outage on 1 March 2025?

Microsoft said a problematic code change caused it. It reverted the suspected code to restore service.

How many people reported the March 2025 Outlook outage?

More than 35,000 reports reached Downdetector during the outage.

Sources

APPNEURAL makes APPNEURAL Suite. This article reports public information from the sources above, then explains where our own product fits. Vendor names are trademarks of their owners. Check each vendor's current status and prices before deciding.