I have been using Microsoft Teams from the start. I understand that you want to engage with every end user to monitor what they are doing and so forth. But in that you have built is a system process of a dinosaur. I have been around for a while working with computers and I remember Windows 3.1 and Windows 3.11. And the design of Microsoft Teams brings back associations to Windows 3.x. It was just a Window with some icons in it, and it was pretty unreliable. And it was not unusual that files broke. Just back in the day, get my point? When you open a document with in Microsoft Teams you don´t get all the features of the desktop application, and it pretty much breaks the files that you open. sometimes its ok to open it in the desktop version and sometimes it is better to open it Microsoft Teams. For someone that knows computers and how it works, its fine for a standard end user it is not. One just want to open a file and work with it. It is like a catch 22 problem. It is even worse when one user edits the file from Microsoft Teams and other user edits a file desktop application. The correction performed of the file is all over the place when several users work in a file.
It is like you guys released Microsoft Teams before it was complete. A quick and dirty version of some code base that was lying around that you wanted to test on users to see if it works. And as looks very much like Windows 3.x, Is the developer that worked with Windows 3.x got to be the software designer job of Microsoft Teams? My point here is that you have built something that makes the office life harder and more time consuming.
What is good though is the cloud version of it, that you automatically can mount a team to your computer and sync it. That makes life easier, the problem is the the sync is not working very well either. If someone has a file open for a long time the sync times out, and leave local copies of documents, that is not synced. And you dont need mount and unmount using a letter for every network resource.
If I was a software designer I would concentrate on the following. You have a working platform that is called Microsoft Windows, build Microsoft teams functions in to it. Not the interface though, we don´t want to go back to Window 3.x again do we. My point is scrap the Microsoft Teams interface. As you want to monitor how users work, behavior and so forth. As cloud services is the way to go, that is no doubt about it, see to that several users can work in the same file and edit it simultaneously, without the file breaking. From any Microsoft platform, no Microsoft Teams is not a platform. Not an easy task I know, but is what is important for an end user. Even the big the complicated files. Let me elaborate on the integration of Microsoft teams in Microsoft Windows platform. Develop the Office365 to be the master of multitasking of managing files, today it is not but it can be. you are very close to making it work. As Skype is out the door, let the chat function be a standard symbol in taskbar. Build in the planner, tasks, and so on a standard features in Microsoft Windows. But for those that do not want to utilize them please let it be an option for none corporate users. My point here is, end users only want one thing. They want to work seamlessly, and and whenever. That is how I would go about it. Next time you release something, think it through. Lets face it, Microsoft Teams is far from a complete product to be used in current version.