Microsoft Teams Issue: Some users may experience multiple issues with their Microsoft Teams
Incident
Report for Moveworks
Resolved
We're pleased to inform you that the recent Microsoft Teams incident which potentially impacted the bot performance have been largely resolved.
For more detailed information and real-time updates, you may refer to the Microsoft Service Health using the below link.
https://portal.office.com/servicestatus
For more detailed information and real-time updates, you may refer to the Microsoft Service Health using the below link.
https://portal.office.com/servicestatus
Update
Latest update from Microsoft
We’re continuing to apply mitigations across the affected infrastructure and our telemetry is showing additional improvement in the user experience, though many customers are still affected by this issue. We’re also working to apply fixes to address individual affected Teams features in parallel while our broader remediation strategy is ongoing. We’re evaluating any and all additional workstreams that will allow us to reduce the impact to those customers that are still affected.
We’re continuing to apply mitigations across the affected infrastructure and our telemetry is showing additional improvement in the user experience, though many customers are still affected by this issue. We’re also working to apply fixes to address individual affected Teams features in parallel while our broader remediation strategy is ongoing. We’re evaluating any and all additional workstreams that will allow us to reduce the impact to those customers that are still affected.
Identified
Latest update from Microsoft
User impact: Users may experience multiple issues with their Microsoft Teams.
More info: Affected scenarios include, but aren't limited to:
- Users performing a cold boot may not able to log into teams and will see an "oops" page
- Users logging in or unlocking their devices after some time may see missing messages
- Users may fail to load messages in channels and chats
- Users are unable to view or download their media (images, videos, audio, call recordings, code snippets)
- Some messages may experience delays being sent
- Call Recordings might take longer to appear in user's OneDrive for Business and SharePoint Online
- Users may be unable to load previous Copilot history, or new history is not written
- Bots may be unable to download attachments
- Sending and receiving read receipt notifications may be delayed
- Anonymous users may be unable to join meetings
- Teams connectors for Power Automate/Power Apps may experiencing errors
Current status: Our failover operation did not provide the anticipated relief to end users
in North and South America regions, and we are now working to optimize traffic patterns as part of the mitigation effort. We’re applying configuration changes across the affected network infrastructure to reduce customer impact as quickly as possible.
For Root Cause and Next Steps, please refer to the Microsoft Advisory. Direct link below (requires M365 Admin Rights):
https://admin.microsoft.com/#/servicehealth/:/alerts/TM710344
User impact: Users may experience multiple issues with their Microsoft Teams.
More info: Affected scenarios include, but aren't limited to:
- Users performing a cold boot may not able to log into teams and will see an "oops" page
- Users logging in or unlocking their devices after some time may see missing messages
- Users may fail to load messages in channels and chats
- Users are unable to view or download their media (images, videos, audio, call recordings, code snippets)
- Some messages may experience delays being sent
- Call Recordings might take longer to appear in user's OneDrive for Business and SharePoint Online
- Users may be unable to load previous Copilot history, or new history is not written
- Bots may be unable to download attachments
- Sending and receiving read receipt notifications may be delayed
- Anonymous users may be unable to join meetings
- Teams connectors for Power Automate/Power Apps may experiencing errors
Current status: Our failover operation did not provide the anticipated relief to end users
in North and South America regions, and we are now working to optimize traffic patterns as part of the mitigation effort. We’re applying configuration changes across the affected network infrastructure to reduce customer impact as quickly as possible.
For Root Cause and Next Steps, please refer to the Microsoft Advisory. Direct link below (requires M365 Admin Rights):
https://admin.microsoft.com/#/servicehealth/:/alerts/TM710344
Investigating
User impact: Users may experience multiple issues with their Microsoft Teams.
More info: Affected scenarios include, but aren't limited to:
- Users performing a cold boot may not able to log into teams and will see a "oops" page.
- Users logging in or unlocking their devices after some time may see missing messages.
Scope of impact: Impact is specific to users in North America or the Europe, Middle East, and Africa regions.
For Root Cause and Next Steps, please refer to the Microsoft Advisory. Direct link below (requires M365 Admin Rights):
https://admin.microsoft.com/#/servicehealth/:/alerts/TM710344
More info: Affected scenarios include, but aren't limited to:
- Users performing a cold boot may not able to log into teams and will see a "oops" page.
- Users logging in or unlocking their devices after some time may see missing messages.
Scope of impact: Impact is specific to users in North America or the Europe, Middle East, and Africa regions.
For Root Cause and Next Steps, please refer to the Microsoft Advisory. Direct link below (requires M365 Admin Rights):
https://admin.microsoft.com/#/servicehealth/:/alerts/TM710344
This incident affected: Enterprise Messaging Integrations (Microsoft Teams).