Microsoft Teams is back up and running after a lengthy outage on Friday left people unable to use the service.

The Redmond-based tech giant confirmed the issue on X at 8:45 a.m. PST, stating that they were investigating an issue impacting multiple Microsoft Teams features.

At 9:17 a.m. PST, Microsoft identified a networking issue affecting a portion of the Teams service and initiated a failover to remediate the impact. Real-time outages monitor Downdetector reported around 14,500 incidents related to Microsoft Teams by 10:41 a.m. PST.

Users faced various challenges, including difficulties logging in, missing messages, failed message loading, and delays in sending and receiving messages.

Microsoft provided updates throughout the day, confirming at 10:22 a.m. PST that they had completed the failover process in the EMEA region, with service telemetry showing improvement. Failovers for the North and South America regions were still ongoing at that time.

By Saturday, January 27, at 10:00 a.m. UTC, Microsoft reported that its Teams services had been restored after extended monitoring and mitigation efforts. The company acknowledged the disruption and apologized for the inconvenience caused to users.

The cause of the global partial outage remains unclear, and Microsoft’s engineering team worked to resolve the issues, particularly in the Americas where failover operations did not initially provide relief.

Microsoft posted a list of some of the issues users may have experienced:

  • 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

 

 



from UC Today https://ift.tt/ej3q2Py