New Teams for work only installs per user

Encourage users to sign out of Teams completely when they finish their session on a shared computer. This ensures their credentials aren't saved for the next user.

How does anyone type this with a straight face?

We are a SMB experiencing the same (very frustrating) issue.

Any time someone logs onto a computer, Teams gets installed under their profile. When users don't log on for a while, Teams client gets stale/outdated. Our network vulnerability scanner picks up on this and shows Teams as being outdated...for every user profile on every computer that has not been logged onto for a while.

Forgive me if I haven't explained the situation well but...I'm very verklempt. It is stunningly unbelievable that Microsoft handles Teams this way. If anyone has a fix for this that does not involve GPO or scripting (shouldn't have to do either of those things to address this incredibly annoying Microsoft-caused issue), please let me know.

The Teams Web App doesn't function as needed in our shared Operations environment. I cannot believe this issue was ALLOWED to occur. How many shared computers at other organizations are experiencing this problem? I used to support University equipment and computer lab environments as well as Emergency Response organizations with a different user (IE PROFILE!) signing into the same computer on each of 3 shifts over 24 hours. Microsoft HAS TO FIX THIS ISSUE and I have submitted a case to Microsoft that is over two months old now. If NON-Microsoft (NOT MS Employees) are responding to these submissions, then WHY ARE WE WASTING OUR TIME WITH IT?

Said it all along - Mr. Gates, you can go straight to the cesspool you created when you stole MS DOS from Digital.

Hello Muazzam,

You're right; Microsoft Teams by default doesn't offer a built-in way to install it as a machine-wide application on shared devices. This can be inconvenient for educational institutions like yours where multiple users utilize the same computers. While the lack of a native machine-wide installation might seem like a limitation, Microsoft might be prioritizing user-specific configurations and security considerations.

Alternative Solutions: While a true machine-wide installation isn't currently available, here are some alternative approaches you can consider:

1. Deploying MSIX App via GPO (as you mentioned): This seems like a promising solution. Deploying the MSIX Teams app via Group Policy can automate the installation process for all users who need it on the shared machines.
2. Leveraging Teams Web App: Encourage users to access Teams through the web app (https://www.microsoft.com/microsoft-teams/log-in) whenever possible. This eliminates the need for per-user installations on the shared devices.

Hope this helps.

• Stephen N.

Hi Stephen,

Many thanks for replying so quickly. Although the machines are shared, each users has their own network login. So where Teams might be installed for one user, it won't be installed for another user on that same machine. I find this a highly bizarre move from Microsoft. I'm currently looking into deploying the MSIX app via GPO, hopefully we can find a solution sooner rather than later.

Thank you

Muazzam