A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
We are still Experiencing the same issue.
c
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Microsoft Support Team,
We would like to raise a concern regarding the ongoing Microsoft 365 service degradation under Incident ID: MO1550821, along with the related Exchange Online incident EX1550543.
The reported disruption is affecting multiple Microsoft 365 cloud services globally, including:
Microsoft Teams
SharePoint Online
Microsoft 365 Copilot
Microsoft Planner
As per the reported updates, the disruption is attributed to elevated infrastructure load across multiple regions, resulting in connectivity and service accessibility issues.
This disruption is impacting business operations and user productivity. We request your team to prioritize the investigation and provide the following information:
What is the confirmed root cause of this widespread service disruption?
What mitigation measures are currently being implemented?
What is the estimated timeline for complete service restoration?
What steps are being taken to prevent recurrence of similar incidents?
Can Microsoft provide regular progress updates until all affected services are fully restored?
We request an urgent update and appropriate resolution, as the disruption is affecting multiple business-critical services.
We appreciate your immediate attention and support.
Best Regards,
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
We are still Experiencing the same issue.
c
You can use this link to monitor repair progress.
https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect
The reports are quite detailed.
Microsoft also provides a 99.9% money back SLA which you can also explore if the disruption to your firm is serious.
Hi @Mr Sonbir
Please note that this platform is a user to user community forum rather than an official Microsoft Support ticketing channel. There are no Microsoft Support engineers or incident response personnel monitoring this board to provide direct escalations or customized updates.
Regarding the disruption you mentioned, Microsoft's current notification for Incident ID MO1550821 classifies the issue as a Service Degradation affecting Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot, and Microsoft Defender XDR.
Microsoft has identified that the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. Microsoft is currently restarting and repairing impacted portions of the infrastructure to restore capacity. Additionally, they are investigating an unexpected increase in a specific type of service traffic and evaluating options to redirect traffic to alternative infrastructure to expedite recovery.
Because live incident tracking is not available on this forum, the best course of action is to have your Global Admins monitor the situation directly inside the Microsoft 365 Admin Center under Health > Service health.
If you're an end user without admin permissions, kindly reach out to your Microsoft 365 administrator and ask them to monitor this incident and keep you informed of any relevant updates.
As a fellow forum user, I’m unable to directly influence or expedite the resolution, nor can I provide a confirmed timeline for when everything will return to normal. However, please rest assured that the relevant teams are working to get this resolved as quickly as possible.
I really appreciate your patience and understanding here. Hopefully, the issue will be fully resolved soon so that everything is back up and running smoothly for all of us.
We are still Experiencing the same issue.
c
AI answer
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: