The Next Phase For the New Version of Stream
We're glad to announce we'll be entering the next phase of our journey to the new version of Microsoft Stream in Q3 2021. In this phase, we're on track to start bringing new experiences for sharing, discovery, and video playback on top of the Microsoft 365 file experience.
Teams annotations interact with background
Hi so I've been talking to some of my team about the collaborative annotation features in teams and there's one thing that's stumped us. When you turn on annotation mode this popup appears: The only problem is that there is no button anywhere to "interact with background"? Based on this blog post the feature was supposed to have been rolled out by mid-August, so what are we missing? Version is 1.6.00.22378 for what it's worth. Cheers!
External Users as Co-Organizers
Is there any word on allowing External Participants/Users to be Co-Organizers on a teams session? We’re a B2B company that runs a high volume of corporate trainings for clients, and the inability for external users to have full co-organizer access in a clients sessions is the number one hurdle we have for adoption of teams, and a reason why we consistently advise against moving trainings to the platform. Many structured trainings and meetings are used to having third parties produce, support, or facilitate, and these functions require an “organizer” level permission to invite, troubleshoot, manage breakouts and sharing, pull reporting, etc. The current solution of requiring tenant logins isn’t practical, as most large organizations which comply with IT security protocols require significant internal screening and administration when issuing an internal credential. Host Keys, external hosts, and passed permissions exist on every other video conferencing and meeting platform (Zoom, WebEx, Adobe Connect, UMeet, Kaltura, etc). Teams seems unique in lacking this basic feature. Is there any insight on when we can expect this basic functionality? Is it on the roadmap? If not, is there a way we can get it there?
Automatic purge of the cache when a profile picture is changed
Hi folks, Currently, profile pictures in Teams are cached on the client for up to 60 days. This means that it could take up to 60 days for colleagues to see your new picture with a nice Christmas sweater. To illustrate my point, let's consider a scenario where Satya Nadella changes his profile picture on December 1st with a great Christmas jumper. Would it be acceptable for his collaborators only to see the updated picture after their cache expires 60 days later, on February 1st? Shouldn't we purge the cache after each profile picture update to ensure the latest version is visible across all clients and solutions within 24 hours? The user's story could look like this: As a Microsoft Teams user I want my newly uploaded picture to be visible within 24 hours across all clients and solutions. So, my collaborators will always be served with the latest content. Please vote for the feedback here. Thank you. Dimitri LinkedIn | Medium | X | Microsoft | Web
