The reported disruption is affecting multiple Microsoft 365 cloud services globally, including:

The specific incident details for MO1550821 and EX1550543 are not available here, so a confirmed root cause, active mitigation steps, or an exact restoration timeline for those incident IDs cannot be provided.

Supported guidance for this scenario:

1. Check tenant-specific impact in Microsoft 365 admin center
   Go to Health > Service health. This page shows:
   • active issues Microsoft is working on
   • issues in the environment that require action
   • current service status
2. Use the incident status to interpret progress
   Service Health uses statuses such as:
   • Investigating: Microsoft is gathering scope and impact details.
   • Service degradation: the service is available but impaired.
   • Service interruption: users cannot access the service consistently.
   • Restoring service: corrective action is in progress.
   • Extended recovery: restoration is underway but full recovery will take more time.
   • Service restored: the issue has been resolved.
   • Post-incident report published: root cause and follow-up actions have been published.
3. Expect update cadence through Service Health Dashboard
   Microsoft notifies Microsoft 365 administrators through the tenant-specific Service Health Dashboard in the Microsoft 365 admin portal. During service incidents, updates are normally provided on an hourly cadence unless a different cadence is announced in the dashboard posting.
4. Understand what Microsoft provides after major incidents
   For broad, customer-impacting unplanned incidents declared through Service health:
   • a preliminary post-incident review (PIR) is delivered within 48 hours of incident resolution
   • a final PIR follows within five business days
   The PIR includes:
   • customer impact
   • incident start and end time
   • timeline of impact and resolution measures
   • root cause analysis
   • actions being taken for continuous improvement
5. Prevention and recurrence handling
   Microsoft states that after incidents it performs post-incident reviews, identifies root causes and required fixes, and applies those learnings across services as part of continuous service improvement. Microsoft also describes built-in resiliency measures such as fault isolation in code development, service deployment, load balancing, and database replication to limit cross-service impact.
6. If broader monitoring is needed
   Service communications can also be consumed through:
   • the Microsoft 365 Service Communications API in Graph for real-time service health and Message Center communications
   • SCOM with the Microsoft 365 Management Pack

• How to check Microsoft 365 service health
• Learn about Microsoft 365 monitoring
• Enterprise business continuity management customer and cloud partner responsibilities
• Service health and continuity
• Built-in service resiliency in Microsoft 365