Users may currently be unable to connect to their Exchange Online mailboxes across multiple connection methods. Our upstream partner, Microsoft, has confirmed this is an active infrastructure issue and is actively investigating.
User impact Users may be unable to connect to multiple Microsoft 365 services.
More info Potentially impacted services include:
Exchange Online
Microsoft Teams
SharePoint Online
Microsoft Copilot 365
Microsoft Defender XDR
Microsoft Planner
Microsoft To Do
Current status While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.
Previous Status While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.
New Media Studios Support
Users may currently be unable to connect to their Exchange Online mailboxes across multiple connection methods. Our upstream partner, Microsoft, has confirmed this is an active infrastructure issue and is actively investigating.
User impact Users may be unable to connect to multiple Microsoft 365 services.
More info Potentially impacted services include:
Current status While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.
Previous Status While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.