We are in the journey from Skype for Business on-premise Enterprise Voice to Teams voice. We started by operating in Islands mode (because we didn't know any better/we wanted to introduce the full features of Teams to get buy-in). However, now that we are testing moving users to Teams Only with Phone System, we are finding that because all other users are in Islands mode, calls from the Teams Only users to users still using Skype Enterprise Voice are ringing to the Teams client, not to the users' desk phones or Skype client.

This can be solved by changing the Coexistence Mode to "Skype for Business with Teams Collaboration and Meetings," HOWEVER, this also completely removes the Chat section of Teams. This is HIGHLY undesirable, since we have been championing Teams as hard as we can. As an example, in order to test this I changed the Coexistence Mode of one of our internal IT staff, and she lost access to a group chat in which she had been planning a baby shower with a few other staff.

So, I believe I am requesting a new Coexistence Mode: "Skype for Business with Teams Collaboration, Meetings, and Chat" or perhaps "Teams with Skype for Business Calls." Referring to the diagram on https://4sysops.com/archives/understanding-microsoft-teams-coexistence-and-upgrade-modes/ This would be an additional Mode with Calls on the Skype for Business side and Chat, Meeting Schedule, and Teams and Channels on the Teams side.

Make new conversation UI for desktop align with mobile versions.

Right now, there are a LOT of new conversations that get started as someone is attempting or meaning to reply to an existing conversation. The fact that the replay and start a new conversation are often next to each other, and visually very similar as text input it's easy to confuse them.

The problem with new threads is they become disconnected from those who are actually replying to an existing thread.

This isn't the case in mobile, specifically android, where the new conversation is a round button in the lower-right corner. The abstraction of creating a new conversation leads to less unintentional new threads.

I would like to see the UI for the desktop version match android so that the new conversation is more different from a direct reply.

To address interop issues during transition from Skype (both consumer and SfB) to Teams. Teams needs a "Skype" button that allows you jump into Skype quickly to avoid interop issue. Need to share a file with someone still using SfB - hit the Skype button to open a Skype chat with that peron, need to screen with someone - hit the Skype button, need a group chat - hit the Skype button. The button could be configured to only show if the person you were talking to was still using SfB. This would really help smooth the transition from. It's not "Islands" mode because I still want all IM & calls to come into Teams initally but I may need to use some advanced features too even if the other person is still on SfB.

A similar idea to this was already marked as completed. And perhaps it was back when that idea was created.

However, currently VSTS has a Kanban integration with Teams that TFS does not, and my team would desperately like to have this integration.

Although, my understanding is that the VSTS integration simply imports the VSTS Kanban into teams. What we would prefer is for the Teams Kanban (currently hosted by Microsoft Planner) to simply be able to create and sync with tasks in TFS.

The TFS Kanban feels extra and under featured now, and we would like one central place to manage the projects where only a portion of the project actually involves TFS bugs.

User A is using Teams
User B is using Skype for Business and has A in their SfB contact list.

B initiates a call to A as a Skype audio call.

User A hears an audio indicator via headset or speaker that an inbound call is ringing but no on-screen popup occurs to offer a way to answer or decline the call.

Both users are licensed with Enterprise Voice. If B calls A using the PSTN number assigned to A, no problem.

Issues occur when B uses the SfB default to simply make a non-PSTN audio call between the two users.

Fix -- properly display the toast notification that an inbound call is present.