(Updated) Purview Communication Compliance: Temporary delays in processing due to planned infrastructure migration [MC1214183]

Message ID: MC1214183 (Updated)

Updated March 4, 2026: We have updated the timing of this change below. Thank you for your patience.

[Introduction]

Microsoft Purview Communication Compliance is undergoing a scheduled infrastructure upgrade. Although this migration is planned outside of normal business hours, some production clusters may experience higher loads, potentially causing brief delays in downstream processing. Brief delays in processing may occur during this migration, but no data will be lost.

[When this will happen:]

This migration will begin January 5, 2026, and end April 15, 2026 (Previously February 28, 2026).

[How this affects your organization:]

Who is affected:
Admins managing Microsoft Purview Communication Compliance policies and review workflows.

What will happen:

• Updates to policy insights and aggregated counts (New pending today, Total pending, Total resolved) may occur at a slower pace than usual.
• Intermittent errors may occur when reviewing flagged messages.
• Brief delays may be observed between receiving an alert notification and accessing messages for review.
• Certain report views may display outdated data until backlog processing is complete.
• Some export functions, such as exporting reports and files, might be temporarily unavailable.
• No data loss will occur—only temporary slowdowns in processing times.

This maintenance is scheduled outside of normal business hours to minimize impact. However, global organizations may experience some overlap with active hours.

[What you can do to prepare:]

• No action is required from administrators; the upgrade will be implemented automatically.
• We recommend informing your administrative and compliance teams about these possible short-term delays.
• If needed, update internal documentation to reflect potential temporary limitations.
• Learn about Communication Compliance.

[Compliance considerations:]

No compliance considerations identified; review as appropriate for your organization.

Source: Microsoft

<<< [MC1214183] Archive
Tooltip: View earlier revisions of this post

Latest Posts