Users may have been unable to access or protect content using ARM in Microsoft 365 services.
- Status
- Wiederhergestellt
- Funktion
- Multiple Applications
- Region
- Nicht angegeben (alle Regionen)
- Beginn
- 12.10.2026, 09:00 Uhr
- Behoben
- 12.10.2026, 12:21 Uhr
- Dauer
- 3 Std. 21 Min.
Mehr Informationen
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.
Betroffen
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.
Ursache
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.
Abschluss
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.
Verlauf
Alle Updates von Microsoft zu dieser Meldung, das neuste zuoberst.
- 12.10.2026, 14:13 Uhr
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.
- 12.10.2026, 12:42 Uhr
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.
- 12.10.2026, 11:16 Uhr
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.
Störungen in LEXOJ abonnieren