Live status of all services Incident · resolved

Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview

Microsoft Purview MP1471821

Admins may have received failures creating or updating Communications Compliance policies in Microsoft Purview.

Status
Service restored
Feature
General
Region
Not specified (all regions)
Started
Sep 14, 2026, 18:41 CEST
Resolved
Oct 12, 2026, 18:28 CEST
Duration
27 days 23 h

More info

Impact was limited to Communications Compliance policies with more than four classifiers.

Scope of impact

Some admins may have received failures when they created or updated Communications Compliance policies in Microsoft Purview with more than four classifiers.

Root cause

A service update which intended to add operations with larger data sizes introduced a code error, causing size limitation issues.

Next steps: We're reviewing and improving our service update validation procedure to prevent similar issues from occurring again in the future.

This is the final update for this event.

Final status

The fix deployed to the whole of the affected infrastructure, and we've confirmed with our internal monitoring telemetry that impact is remediated.

Timeline

Every update Microsoft posted for this issue, newest first.

  1. Oct 12, 2026, 18:42 CEST

    The fix deployed to the whole of the affected infrastructure, and we've confirmed with our internal monitoring telemetry that impact is remediated.

  2. Oct 6, 2026, 19:47 CEST

    We've completed the deployment to over 90 percent of the affected infrastructure. While most admins should see relief, we expect the release to complete by the next scheduled update.

  3. Sep 29, 2026, 18:35 CEST

    We've continuing to monitor the deployment of our fix which remains scheduled to complete by Monday, October 5, 2026.

  4. Sep 22, 2026, 18:44 CEST

    We've completed internal validations for our solution and have begun its deployment. Our fix deployment timeline projects the deployment will remediate the impact by Monday, October 5, 2026. Until this time, we advise users to keep Communications Compliance policies limited to under four classifiers in order to avoid impact.

  5. Sep 14, 2026, 18:47 CEST

    We've received reports from a subset of affected admins who have reported receiving size limitation failures when creating or updating Communications Compliance policies in Microsoft Purview. We've isolated that a recent update introduced operations with larger data size included a code issue, causing size limitation issues. We've created a code fix to address the issue, which we anticipate being fully deployed by Monday, October 5, 2026. During this time, we advise users to keep Communications Compliance policies limited to under four classifiers in order to avoid impact.

  6. Sep 14, 2026, 18:42 CEST

    We're investigating a potential issue with Microsoft Purview and checking for impact to your organization. We'll provide an update within 30 minutes.

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.