Sorry for the delay on an update on this one! I’m hunting down the status for you and will update once I have it.
Also, if you are interested in participating in testing or surveys for this, just tweet me at @skprufo.
This item is still on the backlog. I’ve received no further updates yet about this topic. I will continue to bring your feedback to the feature team.
Agreed. This is a functional requirement for many Bot use cases. For example, my org has an internal Bot for Slack that copies conversations on bugs into our issue tracker as comments. This is currently not feasible to replicate in Teams (despite the threaded chat being better suited to issue-specific conversations!) due to the requirement of mentioning the Bot on every reply.
I've also noticed that this requirement limits the usefulness of some third party bots like the Meekan scheduler.
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.
Yes please! Seeing O365 Group Calendars in ActiveSync/3rd party EWS clients would also go a long way, but I understand that's probably a different department :) Maybe system calendar integrations on the iOS/Android apps could close the gap?
This feature request is still working its way through the backlog queue.
I agree. If you are creating teams for specific departments or work groups in the company, it should be expected that membership and access to those teams follow the current membership of the security group.
The way I would expect this to work is to have the security group itself be listed as a member of a team. Right now when you add a group or DL it just auto fills the current membership list as individual members.
This is still being worked upon. I hope to have more details in the next couple months.
Please know the team is actively working on this feature.
The feature team is still considering this item. No confirmation yet.
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.