Updated May 15, 2026: We have updated the timeline. Thank you for your patience.
[Introduction]
Microsoft Purview Communication Compliance is undergoing an infrastructure upgrade from January 5 to June 15, 2026, causing temporary processing delays, intermittent errors, and possible outdated report data. 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.
No action is required, but admins should inform teams about these short-term impacts.
[When this will happen:]
This migration will begin January 5, 2026, and end June 15, 2026 (previously May 15).
[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.
- Users may experience reduced responsiveness and intermittent instability in the experience.
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
- AWS Direct Connect announces 100G expansion in Lima, Peru
- AWS Marketplace now supports self-service seller signature management for India-based sellers
- AWS Elastic Disaster Recovery is now available in six additional AWS Regions
- Amazon EKS now supports EFA and placement groups on Amazon EKS Auto Mode and Karpenter
