03-16-2017 09:34 AM
03-16-2017 09:34 AM
I am having trouble figuring out how to use Teams as my only client and shut down Skype. I know that if I do not have Skype running I will get the notifications in Teams. But I only want 1 client.
So my first big question is how do I send a message to a Skype user from Teams?
03-16-2017 09:53 AMSolution
Hi Mike. You'll still need Skype (for Business) for online meetings and calls with people outside your organization. You can hold a meeting within your org using Microsoft Teams, but attendees will need to be members of the team. Teams meetings have a limit of 80 attendees. You can share your screen in a Teams meeting. But if your org is in the practice of recording meetings, this feature isn't available in Teams yet.
As for Skype for Business Interop
- "Plan, Deliver and Operate Microsoft Teams" from the Planning Workshop PowerPoint at https://www.successwithteams.com/#Download.
03-16-2017 10:30 AM
03-16-2017 11:00 AM
09-07-2017 01:54 AM - edited 09-07-2017 03:02 AM
This is going to confuse lots of folks! Is this really just an advert for Microsoft Teams and a nudge for those users to check out Teams, or something else? Either way, it seems poorly worded and out of place.
09-07-2017 02:12 AM
We've also seen this? Does anyone know if it's reversable?
As I understand Teams isn't a replacement for Skype so this feels wrong.
09-07-2017 02:51 AM
Same for us (French users)
A bit confusing as we have some users fully online and for whom we can't let them without Skype IM...
Answer awaited with a huge restlessness...
09-07-2017 03:02 AM
Nico, I found your article helpful with more background info - Office 365 Mail pushing Microsoft Teams. Sounds like this is (was?) just a temporary glitch but we can read more into if want to ;-)
09-07-2017 03:06 AM
09-07-2017 03:09 AM - edited 09-08-2017 08:04 AM
Microsoft can't really do this until they have external guest access and federation working for Teams. My users of Skype Online (through OWA) cannot contact externals... It is impacting my Service Desk.
UPDATE: Microsoft recognized this was a little mistake. It is fixed.
09-07-2017 03:31 AM
I agree with the frustration. This cannot be done this way, i haven't really understood that this was going to happen and i don't see any information about this change.
It's creating a lot of confusion since we have disabled teams up until we can figure out how that space can interact (if) with our way of working which now consists of mainly yammer for social collaboration. Yes, I understand the advantages of teams but we are trying to avoid too much confusion too early.
Microsoft, this is extremely unfortunate and badly implemented/informed.
09-07-2017 08:11 AM - edited 09-07-2017 08:13 AM
This story got picked up by Mary Jo Foley - Microsoft may be repositioning some (or all) of Skype for Business as Teams pointing to this very thread, that answers some of the questions many of us had.
"A number of Office 365 users received a big surprise today when trying to log onto Skype for Business."
09-07-2017 11:43 AM - edited 09-07-2017 11:44 AM
Now confirmed -
"We're upgrading Skype for Business to Microsoft Teams. This will take us some time to complete. For now, this is an opt-in experience, as we continue to work on enhancing the Microsoft Teams experience."
09-07-2017 11:52 AM
I've got that message in the Admin center too but no other sign of it, and hope this is one of their crazy ideas that doesn't come to pass!?!
09-07-2017 01:10 PM
For testing purposes, we have multiple O365 tenants. This message appeared in all of them today. Within an hour, all of the messages were gone. Oooops.
09-07-2017 11:26 PM - edited 09-08-2017 08:06 AM
Today, we have another surprise. You can add external guest users - but it doesn't work after you add them.
The external guest gets an email saying they've been added, but when they try to get in, it fails...
09-07-2017 11:43 PM - edited 09-08-2017 08:09 AM
I am getting some private messages basically implying people don't believe me when I say external access is half-turned-on :)
UPDATE: Microsoft Product Group contacted me on this. It was a small mistake. It only impacts users that were in Azure AD already, not "new" external guest users. It still fails, but it seems this will be fixed soon.
09-08-2017 12:52 AM
@Josh SullinsTeams is built on groups, groups allow guest access, that's what you are seeing and has been there since the start. It's useful to know that when uploading a file using Teams that this might be seen by a guest accessing SharePoint.
Guest access to Teams conversation is coming, it's been talked about on the roadmap for a long time, and I'm sure we'll get all the details about it at Ignite.
09-08-2017 08:16 AM
You are right @Steven Collier, but this morning we got a message in all our Teams based on O365 Groups that already had externals in them, that the externals were added in the Team. So, I think something happened today, maybe it was possible before, and it is a little bug, but the message was an issue.
Again, MS PG contacted me (appreciated) and I know it will be addressed.
09-08-2017 08:17 AM
09-09-2017 01:58 AM
09-29-2017 10:33 AM
09-29-2017 11:11 AM
Well worth checking the FAQ, along with the other resources, if you haven't seen it yet. It mentions, amongst other things, Inbound and outbound calls to PSTN numbers, as well as basic calling features (hold, call transfer, speed dial, voicemail) are to be added plus support for USB & IP phone hardware. Also, audio conferencing is being added to Microsoft Teams. There is a roadmap update due in October for Teams, that might add some further clarity.
10-06-2017 12:32 PM
12-06-2017 01:33 AM
I am following and advising customer UC and/or Microsoft since the OCS days.
For me Skype is going from a majority of 1-1 communications with easy escalations to a group. Now there is teams which is focussed on (larger) groups.
I know there is a roadmap to take all Skype online functionalities towards teams, which will take plus one year and not even the more advance communications will be included.
I am afraid of the following: items not working anymore between Teams and Skype for Business (federation, videoconferencing, desktopsharing, file transfer etc). A lot of investment need to be made into adoption of a new client.
Less support of Skype for Business 2019. If i look at the roadmap announcement at Ignite, only items i see is removal of silverlight and some connection to O365 dashboards. I am just not getting why trying to port a 13 years product towards something completely new (1year). Too difficult to manage Skype Online??
I know there is room for team communications. Funny part is that persistant chat never took off on Lync 2010/2013 and Skype. It was supposed to be used in the financial area, but my last customer was an international bank and they did not use it.
If I look at my majority of clients with 5000+ users they should stay on Skype for Business On-premise or actually in most of the cases still in the proces of migrating away from the old PBX-es, Analogue connections, PZI integrations, Video integrations, Contact Center integration, Voice recording etc. All those items are already difficult for Skype On-Premise, impossible for people going to the Cloud. Why even consider Hybrids. So Microsoft is focusing on their Cloud-First initiative because it's in their benefit, I see little benefit for the customers (note: just the Skype for Business workload, the rest is has a better business case).
In the meantime Microsoft should deliver on their cloud roadmap and also fully invest in the On-Premise product. Otherwise there will be an opportunity again for Cisco, Avaya, Mitel etc. to take over again in the UC space. Cisco has already passed Microsoft in the Gartner MQ for UC.