Event banner
Event details
54 Comments
- Any end user input is always valuable for planning priorities, please always enter your feedback: aka.ms/feedback
- Will we see NDI Out and/or Hardware Out via SDI also on Teams Rooms (on Windows) OR will this stay with the Desktop client? We DO see many use cases for this in bigger rooms like in auditoriums with lots of external AV equipment.
- There was a post a long time ago about Teams is move away from Electron to Webview2, is this still happening? If so when? How much performance improvements will this bring?
- This is on Mac OS
- When do you thing Microsoft will have MS Teams policies in place for naming convention standardization to gain control from a administrative perspective instead of owners adding special characters in teams names please?
- I have a question regarding connected 4K displays. With a ticket to Microsoft we have only received the information, that Microsoft is working on it. Why there is no roadmap or timeline? We have 150 employees which are programming on 4K resolution and need to make Teams Video calls incl. Screen Sharing in good performance - this is currently not possible.
- GREAT Questions. Please feel free to ask more questions as it relates to this topic! Performance, Reliability and Quality
- What is the status of screen markup and annotation?
- Is there any news on improving on the "up to 28 and 60 days to update the local client cache"? It is troublesome having to wait this long and it provides and inconsistent user experience. https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/user-information-not-updated?msclkid=dce9c0abc57a11ecbf7fd5c1d653a0b4
- This behavior is by design. Teams has a caching scheme that is designed for capacity and performance optimization. The Teams service caches general user information for up to three days. The Teams client also caches general user information locally. Some data, such as display name and telephone number, can be cached up to 28 days in the client. Profile photos can be cached up to 60 days.
- Hi Stephen. I understand it is currently by design per the link I included in my post. By your restating the content of that doc, Microsoft is basically saying, it cannot feasibly/reasonably improve this functionality and it is not in its roadmap to attempt to do so. Does Microsoft not see how for a collaborative communications tool, this is a somewhat glaring shortcoming in functionality. We have to tell users to plan to update your profile photo up to 2 months ahead of when you want to display the change. This lack of dynamism is disappointing.
- From a performance perspective as a phone system, there are still functionality items like support for analog gateways that are missing. Is there any roadmap or updates on when this will be implemented?
- Are you able to share any news about Microsoft Teams and its Cache? We all have been in cases when the solution has been “clear cache”. Currently your customers have built many different homemade solutions for this work. As the cache is clear “performance” item, you perhaps can clarify: - for what items Teams is using the cache, does it really makes difference? - do you have plans to improve Teams client so that end users does not need to worry about clearing cache?
- Skype for Business allowed us to pull PSTN call statistics and user reviews directly out of the database. Teams does offer some PSTN statistics, but we're unable to pull the raw data to parse real-time MOS scores and PSTN activity. PowerBI won't be adopted by the business, which renders any solutions dependent on PowerBI unavailable to us. Ideally, we should be able to pull real-time data out of Teams the same as we were able to pull out of the on-prem SfB databases. Is there an option in the roadmap to give us *all* of our usage data?
- The response I heard was "use PowerBI". This isn't helpful to organizations like ours who are unable to use PowerBI. We need to be able to pull, at minimum a CSV of call usage from our tenant.
