Teams status is showing as 'status unknown'

[JamesDay]

We are seeing a strange issue where users of Teams have their status shown as 'status unknown'. In our organisation this only seems to be affecting users who are using Teams on MacOS. Users have tried signing out/back in, restarting their Macs, and also reinstalling Teams.

[#2]

My organization has been seeing the same issue today as well. Hopefully they are aware and looking into it. @JamesDay 

[#3]

This is in my Service Health dashboard:

---

All users can't view or update user presence in Microsoft Teams

TM212081, Microsoft Teams, Last updated: May 5, 2020 3:33 PM

Start time: May 5, 2020 12:21 PM

Status: Service degradation

User impact: Users are unable to view or update user presence in Microsoft Teams.

Latest message

Title: All users can't view or update user presence in Microsoft Teams

User Impact: Users are unable to view or update user presence in Microsoft Teams.

More info: Users will see a "Status Unknown" message when attempting to view another users' status. Current status: We've performed additional analysis and determined that failing over traffic to alternate infrastructure will be a more efficient mitigation strategy. We'll continue to monitor service health while this process completes.

Scope of impact: This issue may potentially affect any of your users attempting to look up or update user presence.

Start time: Tuesday, May 5, 2020, 12:21 PM (7:21 PM UTC)

Preliminary root cause: A recent configuration change resulted in a spike of memory utilization on infrastructure that facilitates user presence requests and updates.

Next update by: Tuesday, May 5, 2020, 4:30 PM (11:30 PM UTC)

[#4 · Accepted solution]

@JamesDay we are experiencing similar symptoms where most users show as "status unknown".  We're running Teams across multiple Windows desktops and Android devices.

[#5]

@tko888 I started having this issue since three days ago

[#6]

@MohammedAlhajsalem  We are also seeing the same issue in team. 

[#7]

@JamesDay In my case, I just had to sign out and log in again.