Blog Post

Microsoft Teams Blog
2 MIN READ

Update! Presence now respects a user's coexistence mode

Rahul Kayala's avatar
Rahul Kayala
Former Employee
Oct 30, 2018

Based on customer feedback, we are updating how presence works when organizations are using both Microsoft Teams and Skype for Business.  With this update, routing and presence are fully aligned. To ensure that routing follows presence, presence publishing is now based on a user’s coexistence mode


If a user is in TeamsOnly mode, then any other user, whether in Teams or Skype for Business, will see presence based on the user’s activity in Teams.


If a user is in any of these modes: SfbOnly, SfbWithTeamsCollab, SfbWithTeamsCollabAndMeetings – then any other user, whether in Teams or Skype for Business, will see presence based on the user’s activity in Skype for Business.


If a user is in Islands or Legacy mode, presence is independent and the values need not match.

 

  • From Teams, any other user within the same tenant will see presence based on that Island user’s activity in Teams. Chat and calls from Teams users in same tenant to that Islands user will land in Teams.
  • From Teams, any other user in a federated tenant will see presence based on the user’s activity in Skype for Business. Chats and calls from Teams users in a federated tenant to that Islands user will land in Skype for Business. 
  • From Skype for Business, any other user will see presence based on the user’s activity in Skype for Business.


Please note that If a recipient you previously had a conversation thread with is subsequently upgraded to Teams, that thread will no longer reflect accurate presence and will no longer be routable. You should start a new thread.

You can find more information about co-existence modes here

 

 

Updated Jan 26, 2021
Version 5.0

64 Comments

  • Great news. Is there any estimate on the release date of this user voice request: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16925461-allow-different-notifications-options-on-teams-and?

     

    I also share my opinion on how to enhance the notification behavior that I believe is vital in Teams.

     

    This is what I think should be the behavior or it should be allowed the user to configure (one to one or group chats or channel conversations).

    - One to one chat or group chat: When someone starts a conversation, a callout message should be displayed (to allow the person to know someone wants to chat) 
    Then, if we reply and someone in the conversion replies back, we should be able to not see a callout message for every message they send. A simple notification count with the number of unread messages in the Teams icon in the taskbar and the Teams icon blinking for a few seconds after the message is sent should be enough. This is what is the behavior in both Skype Consumer and Skype for Business and is the one that makes more sense to me

    - One to one chat or group chat: In resume, when someone starts a new conversation, the other involved persons should receive a callout message but not for the remainder of the conversation, where only taskbar blinking and showing notification counts should be displayed

    - Channel conversations: if a channel conversion is started, there shoudn't be any callout messages unless a person is mentioned directly, only the Teams icon blinking for a few seconds and the indication of the number of unread messages

    The main goal here is to be less interrupted by Teams notifications and in particular by callout notifications that are distracting and can make people to lose focus.

     

    Does this makes sense and is the team actively working on any of this?

     

    Thanks

    Miguel

     

  • Deleted - Yes, this change has been rolled out to all tenants earlier today. Please note that it may take up to a day for the update to take affect for some users!

    ChrisWebbTech - Glad you're liking it! Thanks

  • I thought I notice my status get stuck on Away the other day. Assuming it was part of this push. Changing status in Teams seems to be much more responsive now. That's nice!