Forum Discussion

ericoliv's avatar
ericoliv
Copper Contributor
Apr 02, 2020

Unknow Status

4 Replies

  • Leachim_'s avatar
    Leachim_
    Copper Contributor

    ericoliv 

     

    Ok the tenant is now working properly :

    -the statuses are finally working
    -the federation is also working (it was also a problem - not possible to chat with external users)

     

    Spent a few hours with Microsoft yesterday to test a lot of things but nothing came out of it, And this morning it finally works!

    Also, about 24H ago, we removed,from our domain, the SIP DNS records (CNAME and SRV) that we added when we first used O365, which weren't needed if S4B was not used (and we never used it).

    So either :
    - Microsoft did something (which seems unlikely, nothing in my support tickets shows an action on their part)
    - the DNS records were somehow interacting with the presence and the federation capabilities.

     

    For the SIP DNS records, i stumbled upon this thread with a similar solution, so I think the DNS problem is the most likely :

    https://techcommunity.microsoft.com/t5/microsoft-teams/status-showing-as-unknown/m-p/211483

     

    • Leachim_'s avatar
      Leachim_
      Copper Contributor

      Apparently Microsoft fixed something.

       

      See communication TM208898

      Title: All users see presence unknown status in Microsoft Teams User

      Impact: Users may have seen a presence unknown status for all users in Microsoft Teams.

      Final status: We've determined that a configuration issue was causing user presence to show as unknown in Microsoft Teams. We've manually corrected the configuration to mitigate impact.

      Scope of impact: Your organization was affected by this event, and this issue may have affected any user's presence.

      Start time: Tuesday, March 24, 2020, at 2:45 PM UTC End time: Tuesday, April 7, 2020, at 11:06 PM UTC

      Root cause: A configuration issue was causing user presence to show as unknown in Microsoft Teams.

      Next steps: - We're investigating what caused the configuration issue so that we can help prevent similar problems in the future.

  • Leachim_'s avatar
    Leachim_
    Copper Contributor

    ericoliv 

    We have the exact same problem on our tenant.

    The error in the log is a user not found / 401 error when querying the presence service

     

    2020-04-02T20:08:46.178Z War HTTP request DM getPresence POST failed: POST "https://presence.teams.microsoft.com/v1/presence/getpresence/", status: 401, response: {"message":"User not found"}, errorCode: undefined, requestId: undefined, correlationId: 9d7bdd9c-1e06-42fb-967f-91effa282bfd, afdCorrelationId: undefined

     

     

    No response so far from Microsoft as to what the problem could be.  All users and all clients impacted. 

    We tried about everything we could on our side.

  • Brad Groux's avatar
    Brad Groux
    Iron Contributor

    ericoliv 

    Status reliability may be hampered by your architecture, especially if Team is operating in "Islands" mode, which is found in the Teams Upgrade page of the admin portal (See Coexistence mode https://admin.teams.microsoft.com/company-wide-settings/teams-upgrade).

    In short, there could be a plethora of reasons that your status messages are different or unreliable, and all of those reasons will likely reside outside of Teams. Azure AD, Skype for Business, Exchange Online and the Teams modes are just a handful of the variables in  play.