Forum Discussion
Teams addin missing in Classic outlook in Azure virtual desktop
- Feb 12, 2025
Hi Axel,
Thank you for your response! It looks like I came to your response a little late. I already found the solution with this link, which has the script that you can directly deploy to install the addin.
https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy#teams-meeting-add-in
With the latest Teams versions, they got rid of those registries and made it simpler with one. The above link will give you more information.
But I'm very happy to get so many helps on this topic. Thank you, Axel and everyone. I truly appreciate all your help. <3
If (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator') ){ Write-Error "Need to run as administrator. Exiting.." exit 1 } # Get Version of currently installed new Teams Package if (-not ($NewTeamsPackageVersion = (Get-AppxPackage -Name MSTeams).Version)) { Write-Host "New Teams Package not found. Please install new Teams from https://aka.ms/GetTeams ." exit 1 } Write-Host "Found new Teams Version: $NewTeamsPackageVersion" # Get Teams Meeting Addin Version $TMAPath = "{0}\WINDOWSAPPS\MSTEAMS_{1}_X64__8WEKYB3D8BBWE\MICROSOFTTEAMSMEETINGADDININSTALLER.MSI" -f $env:programfiles,$NewTeamsPackageVersion if (-not ($TMAVersion = (Get-AppLockerFileInformation -Path $TMAPath | Select-Object -ExpandProperty Publisher).BinaryVersion)) { Write-Host "Teams Meeting Addin not found in $TMAPath." exit 1 } Write-Host "Found Teams Meeting Addin Version: $TMAVersion" # Install parameters $TargetDir = "{0}\Microsoft\TeamsMeetingAddin\{1}\" -f ${env:ProgramFiles(x86)},$TMAVersion $params = '/i "{0}" TARGETDIR="{1}" /qn ALLUSERS=1' -f $TMAPath, $TargetDir # Start the install process write-host "executing msiexec.exe $params" Start-Process msiexec.exe -ArgumentList $params write-host "Please confirm install result in Windows Eventlog"
We had a similar issue and discovered, that we have made a change in a config profile for Outlook Add-Ins. When we started Outlook we have had a message regarding a certificate, which was not trusted.
If you have that kind of settings which restrict Add-Ins it's worth to check that.
- Dharani_RajJan 30, 2025Copper Contributor
Hi Marc,
Thank you for the response! I don't remember having such a configuration in our environment. But I'll definitely dig that up and see if I missed anything :)