Collaboration is a core element of how we work which requires the creation of extended teams on a project or long term engagement. Whilst the majority of our teams are internal staff, there is still a critical element of any project that requires the inclusion of our clients and/or external vendors. It is imperative that Microsoft Teams allows for the easy (but secure) inclusion of external parties for the length of any project or engagement.

This is why historically products like Groups etc. have not been adopted as widely as we would hope. If the tool only allows for 60-70% of a team to participate, it breaks. If a tool does not allow 100% of those who need to be involved to participate equally, if breaks and our users and clients have far too many alternative solutions that they can easily adopt (Slack etc.) to quickly and efficiently do their jobs.

Finally, making external parties sign up for a Microsoft account (such as Hotmail) to authenticate against any collaboration service does not work, and better approach is required and needed.

Looking for the ability to create a channel that only channel members can see. Private channels are available in slack. There is an admin for private channels who is the creator, and they are the ones who add/remove users.

Five types of public/privacy that is being asked for by users:

- Public-Open (visible anywhere including outside the org and anyone can join)
- Public-Invitation (visible anywhere including outside the org, must be invited)
- Company-Open (only visible inside the org and anyone in the org can join; outside the org must be invited)
- Company-Invitation (only visible inside the org, must be invited)
- Secret (invisible to everyone except existing members, must be invited)

Right now you can add a new tab for Planner in Teams. However, you are not afforded all the capabilities of Planner in this tab. Its really "Planner Lite." Here are some items you cannot do with Planner in Teams:

1) If you create a Planner in Teams, it will not be shown in Planner itself!
2) you can go to the group (in web outlook) wich is automatically created for the team and click there on planner and it will take you to the planner for the new group, which then cannot be displayed at teams, but the team was the purpose for the group in the first place?!
3) You cannot import a previous Planner into teams; you must recreate manually
4) Planner tasks do not sync from Planner to Teams
5) You can't get reminders for your Planner tasks in Teams
6) You can't choose different views of Planners when in Teams
7) You can't see progress of Planner items when in Teams
8) No view of Planner Hub

Please integrate Planner in Teams better and integrate Teams in Planner better!!

Honestly, this is a tall order due to the fact that Teams was not launched this way in the first place, but my real world experience, and feedback from the field, is that having Skype-for-Business-like functions in Teams (chat/Presence/etc) be separate from Skype for Business itself is not only confusing for many users, but inhibits adoption. Users want to consolidate the number of apps they use, not increase it. I personally find this to be true.

Teams is an incredible tool with so much potential, but living and breathing in Skype for Business, like so many of us do, Teams isn't a completely organic feel due to the disparity of chat identities. If I could go into Teams, manage my projects/files/OneNote, engage in Chats, see and join my meetings, engage in Audio/Video calls (I can do all this now), AND THEN also place and receive all my PSTN calls, Teams would be my new permanent application for doing all this, and email would start to fade into the background.

This is the direction I truly hope to see things go. Teams' potential is incredible, but realizing its full potential, in my humble opinion, relies on complete Skype for Business integration.

LOG INTO MULTIPLE ACCOUNTS
Original user posted:
I would like to heave this multi-team/tenant option within “MS Teams”, like in Slack. Currently I’m in four different organization. They’re using all office365, three of them now changed from Slack to Teams. I’ve to permanently login/logout to switch to the related MS Team. This is really time consuming.

Another user says:
We need the ability to sign in with multiple accounts. Many of us have several O365 accounts for various reasons (consulting, etc), and we’d need to be able to access teams directly.
This is not a federation or B2B scenario, but a case where new O365 credentials have been created in another tenant for us. The app today only allows a single signed-in account at a time and that’s a blocker.

SHARED CHANNELS ACROSS TEAMS
From a merged idea:
Please add support for shared channels which could be used in multiple teams. Suppose there is one company-wide team with multiple channels. It would be great if all teams within the company could include these channels or at least one of them in their own team. In that way you don’t have to recreate the channel for every team again.

#1 User Request on SharePoint:
Enable integration of Microsoft Teams to an existing SharePoint site rather than to always create a new site collection

There have been a few ideas raised on integrating lists, OneNote, document libraries, etc. from an existing SharePoint site with Microsoft Teams, but in summary, it will be best if we could create a team upon on existing site, so that the "Files" and "Notes" tabs would directly reference the existing document library and OneNote in SharePoint. It does not make sense to have two separate sites: one for all the usual SharePoint stuff, and another just for Microsoft Teams.

#2: Link to Existing SharePoint Sites

Trying to link my Team up to an existing SharePoint site - only seem to be able to link to individual folders rather than the whole document library, meaning that if i want all folders on the Team i need to create multiple tabs to get this. Would be good to link to a whole document library rather than one folder.

#3: Other Asks

Post Team chat to SP microfeed
Connect team sites onenote if available (replace default notes)
Add links to existing document libraries (replace default files)
Add links to existing lists
Add support for SharePoint taxonomy and managed metadata, SharePoint views etc :D