Teams Issues

TM710344User 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 Current status: We’ve identified that a portion of the Microsoft Teams service is experiencing a networking issue.  Microsoft is performing a failover to an alternate infrastructure to remediate impact and estimate this should take approximately an hour to complete. Scope of impact: This issue can potentially impact any Microsoft Teams user in the scenarios outlined in the More info section.-=-=-=-=-=-=-Jan 26, 2024, 1:16 PM ESTCurrent status: Microsoft has completed the failover in the Europe, Middle East, and Africa (EMEA) region and telemetry is showing improvement.We’re continuing with the failover processes in the Americas, and are monitoring whilst these processes complete.-=-=-=-We will provide updates as we get them. Best regards, The Sherweb Technical Support Team

Update Jan 26, 2024, 3:02 PM EST Current status: Microsoft's failover operation did not provide the anticipated relief to end users in North and South America regions, and they are now working to optimize traffic patterns as part of the mitigation effort. They are applying configuration changes across the affected network infrastructure to reduce customer impact as quickly as possible.

Update from Jan 26, 2024, 5:02 PM EST :Current status: Microsoft's network and backend service optimization efforts are ongoing and they’re monitoring internal telemetry to confirm that the efforts are effectively reducing the impact to customers. They are continuing to scale up their services and identify new workstreams intended to remediate this problem more rapidly. Although many customers remain impacted by this issue, we’re seeing a reduction in errors and an increase in availability. Sherweb will continue to provide Microsoft's updates until this is resolved. *Should this be affecting any customers with our Managed Teams Voice service, please reach out to our support so we can provide an alternate softphone (with the same phone / extension number) until this is resolved on Microsoft's end. 

Update from Jan 26, 2024, 5:58 PM EST Current status: Microsoft is continuing to apply mitigations across the affected infrastructure and telemetry is showing additional improvement in the user experience, though many customers are still affected by this issue. They are also working to apply fixes to address individual affected Teams features in parallel to the broader remediation strategy. They are evaluating any and all additional workstreams that will allow them to reduce the impact to the customers that are still affected.

Update from Jan. 26, 2024, 7:45 PM ESTDetailed Status Update:We’re seeing significant improvements with many of the Teams features affected by this incident as Microsoft continues to apply mitigations and optimize traffic. They are evaluating the remaining impact scenarios and are developing fixes and workstreams to address all lingering impact associated with this event.Mitigated/improving: - [Updated] Users logging in or unlocking their devices after some time may have missing messages. We believe that this symptom has been addressed.
- [Updated] Users may have been unable to load messages in channels and chats. We believe that this symptom has been addressed.
- [Updated] Users were unable to view or download their media (images, videos, audio, call recordings, code snippets). We believe that this symptom has been addressed.
- [Updated] Some users were experiencing delays sending and receiving chat messages. We believe this symptom has been largely addressed, though some users may still experience brief delays.
- [Updated] Anonymous users may be unable to join meetings. We’re seeing improvement in this area but some users may still be affected by this scenario.
- [Updated] Teams connectors for Power Automate/Power Apps were experiencing errors. We believe that this symptom has been addressed.
- [Updated] Call Recordings might take longer to appear in user's OneDrive for Business and SharePoint Online. This symptom has been addressed.Still affected/undergoing further evaluation: - 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
- Users may experience issues resuming or rejoining meetings.
- Users within organizations leveraging an Information Barrier may experience issues joining meetings
- Users performing a cold boot may not be able to log into teams and will see an "oops" pageSherweb's next status update on this topic will be tomorrow morning, January 27th.  You can view Microsoft's updates directly on the Service Health page in the Microsoft 365 admin centerBest regards, The Sherweb Technical Support Team