Does anybody know if the new Teams Outlook plugin is supposed to look and do this? 1. While Outlook is open, you have 3 icons, a. One is Teams log with Sign In b. second Icon is "Meet now," but greyed out c. The third Icon is the New Teams meeting, but it grey out. When you click on the new Teams icon, it just opens new Teams, almost like it wants you to use it to schedule meetings and calls. Teams is signed in, so I am wondering if this is by design or not?

It works for me. How are you capturing profiles, what method did you use to install teams. Is federation working correctly. Does it work from a desktop versus a published app?

No published app, Windows 10 VDA 2311 with FSLogix HF3. Installer is one of the ways I tested for this instance. 1. NeverRed @Deyda ( Which does everything I need), But I wanted to try other ways as well. Which option 2 and 3 is me testing other ways. 2. .\teamsbootstrapper.exe -p -o "C:\Installs\newTeams\MSTeams-x64.msix" 3. .\teamsbootstrapper.exe -p Outlook Plugin Installer way 1.

#Installs Teams 2.0 Plugin in C:\Program Files (x86)\Microsoft\TeamsMeetingAddin

#New Microsoft Teams for Virtualized Desktop Infrastructure (VDI) - Microsoft Teams | Microsoft Learn

$teamsMsiPath = (Get-ChildItem -Path 'C:\Program Files\WindowsApps' -Filter 'MSTeams*').FullName

$teamsMsiFullPath = "$teamsMsiPath\MicrosoftTeamsMeetingAddinInstaller.msi"

$installDir = "C:\Program Files (x86)\Microsoft\TeamsMeetingAddin"

`$arguments = "/i `"$teamsMsiFullPath`" Reboot=ReallySuppress ALLUSERS=1 TARGETDIR=`"$installDir`" /qn"`

Start-Process "msiexec.exe" -ArgumentList $arguments -Wait -NoNewWindow

Start-Sleep -Seconds 25

#Add Registry Keys for loading the Add-in

New-Item -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins" -Name "TeamsAddin.FastConnect" -Force -ErrorAction Ignore

New-ItemProperty -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" -Type "DWord" -Name "LoadBehavior" -Value 3 -force

New-ItemProperty -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" -Type "String" -Name "Description" -Value "Microsoft Teams Meeting Add-in for Microsoft Office" -force

New-ItemProperty -Path "HKLM:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" -Type "String" -Name "FriendlyName" -Value "Microsoft Teams Meeting Add-in for Microsoft Office" -force

Verified keys

@Ray Davis sorry I don't have any experience with the plug-in

When you say it works for you, @Jeff Riechers, What exactly works? Guessing it does not say sign in, and the other 2 plug-ins are lit up?

I haven't had to install the teams outlook add-in at all. Just installing with the -p command added it to my environment. Once you have SSO setup with the Teams, then the sign-in portion will go away and it just directly integrates within Outlook.

Alright, that makes sense. But I am also testing it again all methods. • FSLogix Profile Containers only • Test Windows 10 with FSLogix HF 3 • Test Windows 11 with FSLogix HF 3 • Test Windows 2019 with FSLogix HF 4 ( Only for 2019 issues) • Test Windows 22 with FSLogix 3 • • FSLogix OFDC only captures Teams with CPM FIles for profiles • Test Windows 10 with FSLogix HF 3 • Test Windows 11 with FSLogix HF 3 • Test Windows 2019 with FSLogix HF 4 ( Only for 2019 issues) • Test Windows 2202 with FSLogix 3 • CPM containers only Ongoing testing

I have had to enable it to make sure that all the hooks and registrations worked correctly in the environments. It's a little different than the CPM container version, as that one creates a shared point for users to all pull from. The one for fslogix just handles the appx registration if an appx app is launched after being installed in your profile container.

Are you seeing "Error Message: MSTeams installation error: Windows cannot perform the RegisterByPackageFamilyName operation because it could not find MSTeams_8wekyb3d8bbwe in the repository" in the Profile log file? I posted a question about this just before yours. It is my technical opinion upon looking looking at this furthe, the user initiated install of the new MS Teams client installs Teams using the Package name starting "Microsoft.Teams" where as FSLogix HF3 is looking for the package name starting with "MSTeams"

I just read yours again. Honestly I’m following the bootstrap install -p, so I haven’t even went down that side of manual installs. My focus was around the bootstrap install. But that is dang good catch and details.

Yep I find also this error. Use the bootstrap method and it’s ok 😅 😀

@Ray Davis This all worked for me. Non-persistent VDi, W11 (hybrid joined), FSlogix (2210 HF3) full profiles. Removed Classic Teams, installed Teams 2.1 with the bootstrapper method, used your script above to install the plugin.

@Bill Pennie, thanks, man, for confirming this. Appreciate it.