Use same presence as Skype for Business
HI again, and thanks for your patience in between updates for this request. I know it’s been a while since I wrote.
Last month we shared how Skype for Business will converge into Microsoft Teams. This week, we’ve shared some more information on exactly what features will come over. This one is one that we’ve been actively working on.
For more information on the roadmap, see the blog post here: https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Roadmap-for-Skype-for-Business-capabilities-coming-to-Microsoft/ba-p/119636
I’m trying to get an exact ETA on this feature’s ship date from the team — I haven’t secured it yet. But it is expected soon, so I’ll hopefully be posting good news soon.
Thanks again for your patience, and most of all your support.
if there is one thing that is stopping us from fully transerring from Skype for Business to Teams it is this feature. Our organisation is structured around working from home and we have a heavy reliance on the accuracy of the presence indicator. The Skype for Business presence indicator works pretty well, along with being able to set our current loction (ie home or office). Teams for us would be so much better with these 2 features.
Are we really supposed to wait for a halfway decent presence functionality until sometime next year? We don't need the other 1M lines of code from SfB, but just 10 that cover "when user is active (mouse/keyboard) anywhere" then don't set status to "Away"!
Rob Wilcox commented
Any update on this?
Josh Engelhart commented
This is a huge issue for us as well. Alot of times I'm "available" just not actively inside of teams. It should be set up the same as skype so that there is a pc idle time before displaying away etc.
Jeff Gould commented
Rolling Skype for Business into Teams is a BIG mistake! Everyone in my organization uses Skype for Business but only about 35% use Teams and it will stay that way for the foreseeable future. Teams is not an efficient form of communication it leads to fragmented conversations and leaves users "hunting" for info. Having to read through all the flotsam to get to the meat of something is not efficient(sorry got off topic there). Teams currently messes with presence info for S4B and I won't roll it out further until its fixed.
Justyn Davidson commented
Thank you for the update! I don't see anything about making any of the bug fixes with Presence as they relate to Teams (without S4B integration), which is where we will continue to be for the foreseeable future. No acknowledgement that these are even bugs indicates that they won't be addressed any time soon, rendering Teams basically unusable for a distributed organization. I really do appreciate the update; as a MS alum it's nice to know the roadmap is in place and has some timelines. Unfortunately it doesn't help with the viability of Teams as a collaboration solution for my company. We will need to start heading in a different direction (hopefully not Spark) but good to know that now rather than later.
Ideally the status as well as the presence state should work the same as Skype for Business.
We update skype status with what we are working on as we start new tickets and this functionality does not even seem to be in Teams.
Truthfully i hope you don't use the same presence as you used in SFB - 'presence' has been a big issue for us as a team moving from slack..
My team works remotely primarily and when you're not using Teams it automatically sets their status to Away - which means if I want to as my team a question i've actually got no way of telling if i'm going to get a timely response or not and has actually stopped me rom posting the message i.e. I'll wait until they're online again. Which is exactly what i don't want.
In slack presence is on/off primarily which acts as a flag to say "hey - I'm working now. I'm here if you need me" which mean i'm happy to post and I know i'll get a response today. Recently they introduced 'status' which can give some additional context.
Personally i believe it's a mistake for a tool which is supposed to bring people together through digital collaboration to use 'automated' presence detection which relies on you being with in the app (which most people aren't).
Darren Sully commented
No teams for us until this is sorted out..
With announcement at Ignite about Skype for Business being rolled into Teams I'm assuming this will just be a matter of time. Hopefully some of the quirky shortcomings of S4B can be smoothed out in future as it becomes part of Teams.
Jeff Sieben commented
Slack is great, BUT one thing it lacks greatly is the concept of presence. I loved Skype/Lync for keeping sync with Outlook Availability through Office 365. That's an essential feature of Teams needed to compete with Slack.
I was telling our Operations VP (140 employees here) about Teams, and Teams appears to have presence embedded (ie. Green for available, yellow for unavilable, red for busy), and it said she was available, but in fact here Outlook 365 calendar had meeting (and they're connected).
Presence didn't show well to the VP.
Big things make product essential.
Small things make product amazing.
...keep pushing to get the big and small things right.
John Black commented
You have to take what was said at Ignite and process it through a sales/marketing filter. Having been on the other end of preparing for those kinds of events/announcements at a previous company, I can attest to the careful and sometimes overly-optimistic wordplay that goes on. "Interoperable" might mean "they can be installed at the same time and you can use them together" rather than "the two programs actually interact with each other.
I'm confused. At Ignite Lori Wright said that the two clients currently are interoperable, with common presence, messaging and calling capabilities. That would suggest that the two clients already using a common presence, but that is not what we're seeing on our end. Can we expect this to be fixed soon?
Apr 28, 2017
Start off your weekend with good news: we’re working on this!
still laughing about this response - don't get too cocky...
David B. commented
This is extremely frustrating as I end up using S4B to see if someone is busy before I can go to Teams and chat with them. I've seen no improvement at all since starting to use Teams 6 months ago.
Any update on this?
Matt Shafer commented
@Alex, that's fine. It's the same "behavior", IMO, that we're looking for.
Consider this scenario: You have teams on another screen and are plugging away at something on your main screen and someone needs to get your attention for a quick question. The way this currently works is the other person will see you as away. The only way you appear online is if you're actively interacting with the Teams client. So now let's consider the very real possibility that you're a remote worker and your boss see's you as "idle" all the time. This can affect how they scrutinize your work among other things. You would think with the great presence that S4B has, Teams would get the same treatment since it's clearly going to replace S4B given your article
not sure this will happen since Skype for business is dead ;) https://www.petri.com/goodbye-skype-business-hello-teams
Justyn Davidson commented
S4B has the best Status/Presence format in its class. Integrating that same functionality needs to be an immediate priority. Without Presenting and On A Call there is a huge gap in collaboration usability. And of course the basic reliability of Presence on the desktop version needs to be addressed in concert.
Matt Shafer commented
I'm with Gary on this. I understand priorities shift, but there must have been some work on this in the last 4 months? The pitch has been that Teams is where MS is putting its development resources. Since this is a top 10 suggestion, I would expect better movement on this. The real gripe is that users appear as away even when they're at their PC working actively.