Some admins may see inaccurate status information in the service health section in the Microsoft 365 admin center

Title: Some admins may see inaccurate status information in the service health section in the Microsoft 365 admin center User impact: Admins may have seen inaccurate status information in the service health section in the Microsoft 365 admin center. Final status: We've reverted the offending deployment and confirmed through monitoring service health telemetry that the impact has been remediated. Scope of impact: Admins in the West US, UK South, and France Central regions attempting to view the accurate status of incident and advisory communications in the Microsoft 365 admin center may have been impacted. Start time: Tuesday, July 21, 2026, at 7:45 PM UTC End time: Saturday, July 25, 2026, at 6:57 PM UTC Root cause: A code defect introduced by a recent deployment to the Microsoft 365 admin center caused the systems to resolve status conflicts by an incorrect method, which resulted in status messages presenting as active instead of resolved for some communications. Next steps: - We're reviewing our update procedures to understand why impact to service health information wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes. This is the final update for the event.

Title: Some admins may see inaccurate status information in the service health section in the Microsoft 365 admin center User impact: Admins may see inaccurate status information in the service health section in the Microsoft 365 admin center. More info: Specifically, admins may see resolved incidents and advisories incorrectly displayed as active. Current status: We're continuing to monitor the reversion of the responsible deployment to remediate the impact and expect this process to complete for all remaining impacted admins by our next scheduled update. Scope of impact: Admins in the West US, UK South, and France Central regions attempting to view the accurate status of incident and advisory communications in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues. Start time: Tuesday, July 21, 2026, at 7:45 PM UTC Root cause: A code defect introduced by a recent deployment to the Microsoft 365 admin center caused the systems to resolve status conflicts by severity rather than status change was made resulted in the status showing as active instead of resolved for some communications. Next update by: Saturday, July 25, 2026, at 8:00 PM UTC

Title: Some admins may see inaccurate status information in the service health section in the Microsoft 365 admin center User impact: Admins may see inaccurate status information in the service health section in the Microsoft 365 admin center. More info: Specifically, admins may see resolved incidents and advisories incorrectly displayed as active. Current status: We've identified that a code defect was introduced by a recent deployment to the service health feature of the Microsoft 365 admin center which caused the systems to resolve status conflicts by severity rather than how recent a status change was made, resulting in the impact. We're reverting the offending deployment to remediate the impact, which completed for a majority of admins. Scope of impact: Admins in the West US, UK South, and France Central regions attempting to view the accurate status of incident and advisory communications in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues. Start time: Tuesday, July 21, 2026, at 7:45 PM UTC Root cause: A code defect introduced by a recent deployment to the Microsoft 365 admin center caused the systems to resolve status conflicts by severity rather than status change was made resulted in the status showing as active instead of resolved for some communications. Next update by: Friday, July 24, 2026, at 10:30 PM UTC