Live status of all services Incident · resolved

Users may have been unable to access or protect content using Azure Rights Management (ARM) in Microsoft 365 services

Microsoft 365 apps OP1500833

Users may have been unable to access or protect content using ARM in Microsoft 365 services.

Status
Service restored
Feature
Multiple Applications
Region
Not specified (all regions)
Started
Oct 12, 2026, 09:00 CEST
Resolved
Oct 12, 2026, 12:21 CEST
Duration
3 h 21 min

More info

Impact may have prevented users from encrypting, decrypting, or opening protected files and email messages across Microsoft 365 services that rely on ARM. This included protection capabilities in Microsoft Purview, encrypted documents, protected file uploads and downloads in SharePoint Online, related Power BI and dependent service functionality, and publishing agents or adding skills to existing agents in Microsoft 365 Copilot Chat.

Scope of impact

Some users attempting to encrypt, decrypt, open, upload, or download protected content across Microsoft 365 services that rely on ARM, including Microsoft Purview and Power BI, or publish agents or add skills to existing agents in Microsoft 365 Copilot Chat, may have been impacted.

Root cause

A section of the ARM service infrastructure that facilitates the processing of cached service data was underperforming, resulting in impact.

Next steps:
- We’re reviewing performance data and trends on the affected infrastructure to help prevent similar impact from happening again.

Final status

We’ve determined that a section of the ARM service infrastructure that facilitates the processing of cached service data was underperforming, resulting in impact. We’ve confirmed, following a period of monitoring service telemetry, that the mitigating actions successfully resolved the issue.

Timeline

Every update Microsoft posted for this issue, newest first.

  1. Oct 12, 2026, 14:13 CEST

    We’ve determined that a section of the ARM service infrastructure that facilitates the processing of cached service data was underperforming, resulting in impact. We’ve confirmed, following a period of monitoring service telemetry, that the mitigating actions successfully resolved the issue.

  2. Oct 12, 2026, 12:42 CEST

    We’ve redirected traffic away from affected infrastructure to allow the unhealthy service components to recover. Following this action, we’ve observed service recovery across all affected regions. We’re monitoring service health to confirm that recovery remains stable while we continue investigating the root cause.

  3. Oct 12, 2026, 11:16 CEST

    We’ve identified that some service components responsible for processing ARM requests are in an unhealthy state. We’re attempting to restart the affected components to mitigate impact. We’re seeing early signs of service recovery and are investigating the root cause while evaluating whether additional mitigation actions are required.

When Microsoft 365 goes down

The live overview shows the current state of every Microsoft 365 service, refreshed every minute from Microsoft Graph.

Live status of all services Subscribe to incidents in LEXOJ

To see whether your own tenant is affected, check Service health in the Microsoft 365 admin center. Only a backup outside Microsoft protects against data loss, and only a tested break-glass account against locked-out admins. We set up both in fixed-scope sprints.

Source: Microsoft Graph, Service Communications API. This is the view of a Swiss Microsoft 365 tenant: services not licensed there are missing, and individual issues may affect your tenant differently. Microsoft names the region only in the issue text. The Switzerland view shows issues for Switzerland, for Europe in general and those without a region, but not issues that only name other countries such as Germany or the UK. This page is not provided by Microsoft.