Teams Wide Machine Installer - "ProductLanguage" option

Hi, IBM and I have been working on this. This depends on if you are using the Microsoft Teams Classic which orphans' inactive users that remain vulnerable to data breaches in the c:\users\xxxxx\appdata folders. Orphaned users folders can be compromised if bad actors gain access and begin to move laterally as we know.  Thus we have developed scripts to remove all teams once per month from the c:\users\xxxxx\appdata folders and then update the Teams Machine Wide Installer once per month with SCCM, Intune or group policy so that only active users get the current version.

The big unanswered question we are vetting in our sandbox at this time is with the New Teams MSIX package that installs the New Microsoft Teams Meeting Add-In for Microsoft Office that installs as a c:\Program Files app. Our groups in IBM and BFB Security promote zero trust and we are evaluating the cadence of the New Teams and how it operates in smaller SMBs without SCCM or Intune.