We acknowledge the demand for this capability and are exploring the best possible solutions to enable this.
A significant barrier to getting users to use Teams chat instead of Skype for Business is inability to pop out a chat window and keep your focus on other items in Teams.
Chat with someone and your focus on documents or other threads is lost - doesn't make UI sense at all.
It looks like some people in the thread below have figured it out — we actually have this. You can start a chat both ways; the system will automatically recognize if this person is on Skype for Business or on Teams.
Thanks and let me know if you have any questions.
I agree with the recent comments that this is NOT working in any way that makes sense.
I start a chat with someone who is has both Skype for Business and Teams running (both tenants in Islands mode). Other user sometimes receives chat in Teams, sometimes in SfB.
If they receive in Skype for Business and respond, I get the response back in Teams. So far, so good.
if the other user signs out of SfB to use Teams instead, a chat I send to them still tries to deliver to SfB - says they're offline and delivers the "chat" via email. Of course, the other user says they're online in Teams and is completely confused.
Bottom line, I can't tell what the ground rules are for which path Teams will use. And I can't tell users what they should do. We're to the point of just telling users to stay in Teams and not use SfB if possible. Hardly the right answer and frankly not possible when we interact with outside users who use both Teams and Skype for Business.
So --- what do I want?
I want a clear document that says what the interoperability behavior is right now -- not what it will be someday on the roadmap. And I'd like that document to be kept up to date as Teams evolves.
We monitor the roadmap document - that's great as far as it goes. But we and many of our customers are at various points in the SfB to Teams transition. Given that Teams is frequently updated across multiple platforms, the rules and interoperability patterns are in a constant state of flux. We're promoting Teams with our customers, but the constant confusion about how it will work is working against us all the time.
Using Calls with recipients who need to join a meeting by phone instead of a Teams app requires one of two things.
Conference calling add-on. Enables adding a conference call-in number to a Teams meeting.
Enterprise E5 license - that includes the conference calling add-on as well as a number of other feature adds.
Voicemail notifications appear in activity. Tapping one does not take you to the voicemail, instead it displays the call history.
I know I have voicemail since I see that in the desktop app.
The iPad app does not link to voicemails.
The Android phone app does work properly, it appears that the iPad app is the only one broken.
iPad version 1.077
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
100% agree. We've had this exact conversation with countless Teams users - reply in the conversation, not using the "new conversation" area.
Current UI hints at this difference but needs to be more forceful and obvious. Users see the box at the bottom of the window and just start typing there.
Thanks to everyone who volunteered for testing the Office 365 group calendar. The TAP team will be reaching out as we are closer to being ready.
Until there is an official way to do this, is there a workaround that can be used? Other than, of course, telling users to bounce back and forth between Teams and Groups.
We know you are patiently waiting for this feature. This feature is being implemented in stages. Fast tenant switching is currently in testing both internally and with early customers. We expect to release to the public in the Fall. I’ll post an update once it’s rolling out.
Full multi-tenant, multi-user support will be added after fast tenant switching.
Second this - we like Teams with Power BI but need to share Power BI dashboards as well as reports.
Current Power BI tab allows one report, meaning that several Power BI reports will consume many tabs. A single dashboard is far more effective.