Microsoft Teams should have completed Client APIs so that third party apps can be created to fill specific needs.

This API should allow call control of the Microsoft Teams application. Necessary call control features include:
• dial/call
• call answer
• hang-up
• hold/off hold
• call transfer (all types: blind, consult, safe)
• add participant
• mute/unmute
• park/unpark
• call as a delegate
Some general features include:
• search contacts
• get contact presence
• get contact list folders/contacts
• setup contact list folders/contacts
• get/set my presence
• get/set my note
• get/set my delegates
• get/set my Calling Groups
• Get/set my call forwarding
• get/set audio device
• get/set voicemail settings

Messaging
• get/send chat messages
• get/send voice/audio message

The above lists are not comprehensive but are to give an idea of the necessary features.

Also
The Teams Client API should be able to be used inside the Microsoft Teams client canvas or from a standalone application. Ideally, the application developer could decide if they want to access the above functionality by controlling the Microsoft Teams application, with the Teams app running alongside, or as a standalone application, without the Microsoft Teams application running.

We see this as part of achieving Skype for Business parity so ISV's can write applications like Attendant Consoles so organizations can move to Microsoft Teams.

Allow for explicit Connector configuration (not possible in MS Teams because of O365 Groups drawbacks in this area)

Currently if you don't set Connetors in O365 Groups via powershell command to disabled you would have it fully open in O365 Groups.

The MS Teams app suffers from this drawback because you cannot allow Connectors. On the MS Teams admin console it looks like one could control Connectors, but if you get the deeper dependency to O365 Groups and that the Setting there is "oversteering" MS Teams, you see all granularity is not helping you with Connectors.

On Enterprise Level this is a heavy drawback as it leads to no Connectors open for users in MS Teams.

Please make the "combination Teams / Groups" in regard to Connectors usable -- i.e. controllable for an Enterprise IT / Security that has to look after how data is flowing.

Late last week, OneNote on Teams stopped working whether you are using the desktop application or the web based. Creating a new OneNote tab on Teams, it still does not work as well. All we get for a message is:

"We can't access this notebook.

You might not have permissions to view it, but your IT Admin show be able to help you."

Previously, OneNote had been working. If OneNote is accessed directly with OneNote application, it will work fine.

This appears to be a bug on Teams as others are reporting the same issues as well. Could this be checked out and fixed?

Include a project timeline for channels, that includes milestones, tasks subtasks - the whole nine. Whoever is admin/assigned project manager should be able to assign tasks etc with reminders that sync to calendars (outlook etc) so that those people get automatic pop-ups and reminders about items coming due - and everyone can see the progress/assignees. When completed files/pieces of the project are complete, the upload button should include an option to choose a task from the timeline to check as complete, and the timeline updates - who completed, date, and the file. Milestones will update as "reached" or complete when all tasks and related subtasks are complete. Also - conversations should be possible to identify in the same way with hierarchies: Project, Milestone, Task, Subtask etc -archiving as appropriate when sections are complete.