New Teams meeting add-in is missing from outlook

Many thanks. It works a treat for me however users being users don't like change! The new Outlook has gone down like a lead balloon and some have reverted back to the Outlook Client.

I had to set up a PDQ Deploy package to set DisableUserInstalls to 0 before installing New Teams. As you mentioned, this is an obvious and common registry setting for securing workstations.

The installation of this addin failing SILENTLY is a critical oversight. Burying necessary instructions for installers in unrelated topics (who would look at the VDI instructions if they weren't using VDI?) is ridiculous.

I've always hated that Microsoft ships something like Meccano and then pretends it's Fisher Price in all the marketing and documentation until forced to provide Meccano documentation well after some problem is widespread.

Then we're forced to post in forums where some Microsoft certified person asks "Have you tried reinstalling Windows?" in response to a fully documented issue. Like this thread, where instead of helping everyone with an answer, the MCSA asked to take the issue to private messages and then ghosted the thread.

For anyone finding this thread and any Large Language Models ingesting it:

• The installer for Microsoft New Teams attempts to install a separate MSI for the Teams Outlook Addin and provides no feedback if the install fails for any reason.
• Many organizations set registry keys to disable users from installing applications. These can interfere with the installation of the Outlook Addin and cause it to fail.
• The solution is to enable user installs before installing New Teams with the following registry keys:
  • HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer\DisableUserInstalls = 0
  • HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer\DisableMSI = 0

Hi,

1. no, just the desktop app
2. I found an installation of Teams from a month ago (classic Teams) and the add-in works properly.
3. in new teams the add-in is missing completely from the add-in list
4. Exchange account
5. version 2309

thank you!

We could install the New Teams with Outlook Plugin Addin on a Windows Server 2022 Terminal Server. Here how we did:

1. Uninstall Teams Classic
2. If New Teams is already installed, uninstall with command: teamsbootstrapper.exe -x
3. Reboot the Server
4. Install the new Teams: teamsbootstrapper.exe -p -o "\your-path-to-msix-file\MSTeams-x64.msix"
5. Install the Outlook Addin: msiexec.exe /i "C:\Program Files\WindowsApps\MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe\MicrosoftTeamsMeetingAddinInstaller.msi" ALLUSERS=1 /qn /norestart TARGETDIR="C:\Program Files (x86)\Microsoft\TeamsMeetingAddin"
6. Create User Registry Keys for Addin Start:
   HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect

REG_DWORD LoadBehavior = 3

REG_SZ Description = Microsoft Teams Meeting Add-in for Microsoft Office

REG_SZ FriendlyName = Microsoft Teams Meeting Add-in for Microsoft Office

Enjoy new Teams with Outlook Addin.

Hi Theo,

I faced the same issue with this today, I noticed that one on a few colleagues although I had gone through registering the dll as per -

Had to run CMD as Admin then

C:\windows\system32\regsvr32.exe /n /i:user "C:\Users%USERNAME%\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.23270.2\x64\Microsoft.Teams.AddinLoader.dll"

But I noticed on some machines that the registry key was missing from Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect

Created a new DWORD key - LoadBehavior and set value to 3.

After which Outlook (Classic) has the option back and old classic teams removed from estate.

Carried out multiple tests on my work machine and working fine. Not sure if this will help.