While it's wonderful you can view docs shared with a team and said doc gets placed in share-point. The moment you edit the doc you get sent to a web-browser. Considering it's literally HTML, it would be nice if that session presented with within Teams rather than a separate browser pop up. It would make the collaboration process more seamless as well s allow people to continue their persistent chat in teams while editing and not be tempted to use the suddenly disjointed chat built into word/excel.

I feel the more seamless this experience is (only pop up word if I ask for it, otherwise just present it all through teams), the happier people will be.

The recent MSI installer isn't really what people are asking for. It doesn't actually install to program files. It just puts an installer in program files which then installs to the users app data. This doesn't work for me at all.

In a non-persistent VDI environment the application has to install on every login (unless I roam appdata/local which I don't want to do). This isn't the end of the world as it's fairly quick but the problem comes when you also use Yammer. Yammer has the same weird install method and when both teams and yammer try to install they cause a process conflict so only one of them actually installs.

Can we have some proper deployment methods like the rest of Office please? Or at the very least a way of deploying Teams and Yammer together?

Please make MacOS default interactions (keyboard shortcuts/nav, menus, prefs, notifications). Other Office 365 apps are more native than this.

--

Request that text navigation shortcuts follow the system standard:
cmd+left arrow – jumps cursor to beginning of text
cmd+right arrow – jumps cursor to end of text
option + left arrow – jumps cursor left one word
option + right arrow – jumps cursor right one word

One of the issues with this is that the native notifications from other apps cover up the Team ones when both are active. If it was a native app, these notifications would stack.

Recent builds have Option-A on mac hardcoded as keyboard shortcut for attachment.

It’s a problem that this keyboard shortcut cannot be changed or disabled. Option-A is used globally by some Apple standard keyboard layouts, and the Teams shortcut overrides this within the Teams app.

Specifically Apple Dvorak layout uses Option-A as shortcut to access a national character, and the Teams shortcut prevents typing this national char when writing messages is Teams.

When I click Chat and then Option-N (alt), I get ñ instead of a new chat. So I have to click somewhere else and then use the keyboard shortcut which defeats the purpose of a keyboard shortcut!

Please change the Mac shortcuts to use Command like any other Mac app.

Multiple problems reported:

1

It seems whenever the OSX client updates, we get a "An update is ready to install. Microsoft Teams is trying to add a new helper tool." authentication request, then the app quits. Or sometime the app just quits on it's own without any notification. When it launches again, the "loading" box then sometimes doesn't disappear. I really want to roll this out for our teams to start playing with, but having the app quit on us ~10 times a day without notification makes it unusable.

2

On most Macs I’ve tried, the automatic update framework is pretty aggressive, and apparently cannot be unconfigured. However, it consistently fails to update the app when I’m logged in with a standard account. The app occasionally prompts for admin creds (I assume it’s making an update helper daemon), and I supply them, but the only Helper process Teams ever runs is owned by the standard account. I’m not sure exactly what to suggest here, because there are several opportunities for change, some of which might obviate usefulness of others. Ideas might be some user interaction to defer the forced relaunch during updates, options for scheduling deferred updates, options to manually supply admin credentials at each update, improve reliability around whatever helper proc is supposed to facilitate updates.

3

It seems every time Mac app updates itself, it stores the update file to Library/Application Support/Microsoft/Teams/tmp folder.
The update files are named as Teamsosx (1).zip, Teamsosx (2).zip etc. Each file seems to be around 80 MB. Since the Mac app updates itself constantly (microsoftteams.uservoice.com/forums/555103-..), they start consuming significant amount of disk space. When I first noticed this, there was ~70GB of update files! Garbage collection would be welcome.

4

Every time there is an update for the desktop client (at least on Mac) the client updates automatically without prompting the user, which always seems to invalidate the session. There should be an option to prompt the user before the client is updated. (similar to how VS Code does it, perhaps)
There have been many times where teams has updated while it’s been minimized on my machine, causing me to not see any new messages until the next time I’ve manually re-opened and logged in again.