Teams has a bunch of difference local caches and temp files that just continually grow forever in %appdata%\Microsoft\teams. It would be great to have a button that would wipe out all the local cache and temp files in this folder. Doing it manually has a very noticeable performance gain throughout teams.

As it stands, I'm going to write a powershell script to run on all the workstations I manage periodically to close teams and clean this up as a refresh of teams.

Microsoft Teams is currently the most RAM consuming application on my Windows 7 Professional Laptop. I would expect there is room for improvement.

It is is just too slow :/

At our company, 100% of its employees telecommute. This makes our preferred method of live communication to be chat. Sometimes we need to copy snippets of a conversation into a work order, and it is SO difficult to copy text from Teams. Sometimes a person's name won't even appear above their text, once pasted, and the information has to be recreated. Please test this for yourself - copy and paste a few lines of a conversation, and please fix this!!!! Thanks!

How is that the free version Skype screen sharing have no issues, at the same time the paid version (Teams) always have issues, even though the teams screen share is a wrapper on existing skype?

Right now it simply loads too slowly, and it has that massive in-your-face splash screen while doing it.

My goodness, every time you start Teams it's as though it's the first time. Most or all history is gone until it pulls it down from the cloud again. If you want us to use it, make it start in less than 60 seconds.

Allow expanding just the last few comments in a thread, rather than always expanding the whole thing. A thread w/ ~200 replies takes 4-5 seconds to expand completely saturating 1 CPU core and then requires scrolling down through it all to get to the recent replies. This is particularly inconvenient if you are frequently switching channels or between Team view and Chat view as all threads are repopulated collapsed whenever you return to a channel.

We should be able to expand only the unread messages or 20 or so at a time.

For some reason the latest update has Teams using between 8% and 25% CPU idling, doing nothing. There is an issue with this update.

As the title says, our workstations which normally go to sleep after a set time now stay on forever because Microsoft Teams keeps the systems awake. Close teams, problem solved. Kind of irritating.

The native Mac client is very slow compared to either Slack or Hipchat when switching between channels or replying to a conversation.

Please improve the performance of the application.

Teams Webapp on Google Chrome is super slow.

Teams constantly consumes a small amount of cpu time which blocks my laptop from ever sleeping or hibernating because it is never idle. This is not ideal for many reasons. Obviously the software designed around a polling model which is not generally considered to be a great design pattern. To rephrase this as an idea: Change teams so it works on an event based model rather than constantly polling for updates.

Currently when I open a PDF in MS Teams "PDF File Viewer" I cannot click on the hyperlinks. Instead I have to download the document or open it in SharePoint just to click a link. Such a waste of time!

It can take 30s to switch between orgs/accounts in MSTeams - length of time makes the multi-org setup cumbersome to use...

Looking at UserVoice there are a few requests dealing with network utilization. Microsoft provided guidance on network bandwidth requirements for media traffic with Skype(https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/network-requirements/network-requirements). This helps provide large enteprise customers guidance during architectural decisions as well as assist with right sizing their current audio/video usage. This is missing for Team and is needed to assist customers sizing their environment correctly as well as assist with future planning. This can help decrease some of the network bandwidth asks as customers will have better guidance on what is expected with Teams over SfB

Teams app on win 10 is frustratingly slow to close after clicking red x. Taskbar lights up with new message but shows name of last conversation partner not new one. Opening up to see a new message starts you where you left off instead of new message. Badges on phone app don’t go away if I check on messages using Windows app. Nowhere near as snappy as like, AIM back in the day

scroll lag : scrolling performance (i.e. to previous messages in a chat/channel) is much worse than expected - messages don't render for a noticeable period of time