MicrosoftToday I started testing the Outlook AddIn and ran into some issues.
Outlook AddIn isn't installed until the user launches New Teams. Then a per-user install of the Outlook Addin is done. If user launches Outlook before New Teams, AddIn isn't working. Because the Outlook AddIn isn't saved in the FSLogix ODFC Container, when the user roams to a new machine the Outlook Addin is again not installed and user has to do the start New Teams before Outlook all over again.
The Outlook AddIn should be installed per machine when package is deployed, this would have saved us trying to fix this mess again. In an enterprise organisation with lots of roaming users we really prefer per machine installs!
We are going to try to install the Outlook AddIn per machine when we install Teams using the bootstrapper. And then at logon check if the installed version of the AddIn still matches the AddIn MSI in the Teams folder, if not install the new one. We have to update the AddIn ourselves as MS did not think of this, only the per-user install is updated. We also found that the per-user install overrules the per-machine install, so also have to uninstall the per-user install at logon, and then repair the per-machine install. After this we at least should have the AddIn available in Outlook even if user first launches Outlook instead of Teams, or if user roams to a new machine. Unfortunately all those tricks we have to pull slows down logon, also not sure if AddIn will be functional before Teams is started...
Anyone else managed to fix the Outlook AddIn issues?
