Managing presence indicators such as Available, Busy, or Away in Teams Free
In Microsoft Teams, a contact’s presence showing as Status unknown while other users see it correctly is typically caused by one of these conditions:
- The contact is actually offline or has set Appear offline.
- There is a network communication issue with the unified presence service.
- The contact is using Skype for Business and the coexistence presence behavior makes this expected.
Because the issue is intermittent and resolves as soon as a chat is started, this points to presence updates not flowing correctly between the observer and publisher until direct communication occurs.
For Microsoft Teams (including free), the supported troubleshooting and escalation path is:
- As admin, verify the four prerequisites for the affected contact (publisher):
- The contact is signed in to Teams.
- The contact has not set Appear offline.
- Network connectivity to all required Teams endpoints is healthy from both observer and publisher devices.
- The contact is actually using Teams (not only Skype for Business) if in a coexistence scenario.
- If all of these are already confirmed and the issue persists, collect data and open a support ticket. The required information is:
- Sign-in address of the user who sees Status unknown (observer).
- Sign-in address of the contact whose presence shows as Status unknown (publisher).
- Desktop and debug logs from both observer and publisher. For log collection steps, see Use log files in troubleshooting Microsoft Teams.
- UTC time when the publisher changed presence and when the observer noticed it remained Status unknown, ensuring those times are visible in all logs.
Presence issues of this type (where all client-side steps have been exhausted and the behavior is inconsistent across users) require backend investigation by Microsoft Support; there is no additional client-side “permanent fix” beyond the documented steps and ensuring network access to Teams services.
References: