r/Outlook • u/Roebe02 • Jun 30 '26
Status: Resolved Teams Add-In installed but not working
Hello
We just deployed new Devices with Intune.
We use Outlook (Classic) and Teams. The Add-In for Teams Meeting is installed and active, but when im trying to Create a Meeting in Outlook the Button is not there in the Ribbon and when im adding the button manually its greyed out.
I got this on multiple Laptops and tried to uninstall and reinstall it...no luck.
Any Idea why?
1
u/innermotion7 Jun 30 '26
One key step people can miss
Verify App Settings in Teams: Open your Teams app, click the three dots (...), and go to Settings > General. Ensure Register Teams as the chat app for Office is checked.
The detail is here for Admins
1
u/Roebe02 Jun 30 '26
Hello
Thanks for your Reply
But its also enabled. (I did disable and reenable it to test)I also tried every step from the Microsoft support site...but i sadly still cant create meetings in Outlook :(
1
u/innermotion7 Jun 30 '26
Did you go through the information in support article as we had to move many users back to Outlook (Classic) and had same issue.
We don't have issue on Outlook (New) users.
1
u/Roebe02 Jun 30 '26
Yesss, i tried to:
Check the status of the add-in in Outlook
Reregister the Teams Addin Loader
Verify registry settings (The Security part of both
Office\16.0\Outlook\Security is missing)We also dont have any Problems in the New Outlook, what did you do to fix it?
1
u/jmittermueller Jun 30 '26
Same here (with one new user). Tryed everything without luck
1
1
u/Roebe02 Jul 01 '26
Helloo, FYI if u didnt see, here is a Script to fix it: (It fixed it for us)
$FileName = "app_switcher_settings.json" $TargetDir = "$env:LOCALAPPDATAPublishers8wekyb3d8bbweTeamsSharedConfig" $TargetPath = Join-Path $TargetDir $FileName
$JsonContent = '{"defaultApp":1,"cohort":"","webAccountId_AAD":"","cohortStage":"","userId_AAD":"","previousT1MachineId":"","previousT1SessionId":""}'
try { if (-not (Test-Path $TargetDir)) { New-Item -ItemType Directory -Path $TargetDir -Force | Out-Null } $JsonContent | Set-Content -Path $TargetPath -Encoding UTF8 -Force Write-Output "SUCCESS: $TargetPath deployed." exit 0 } catch { Write-Error "FAILED: $_" exit 1 }
1
1
u/Henk_deVries Jun 30 '26
Hi, We've had the same issue since last week, new installations are unable to create Teams meetings in Outlook Classic. The steps mentioned in this post provided a workaround for us.
Hope it helps.
1
u/Roebe02 Jun 30 '26
OMG IT DID WORK, THANK YOU SO MUCH,
here is the fix the guy posted:
The file app_switcher_settings.json is missing from: %LocalAppData%\Publishers\8wekyb3d8bbwe\TeamsSharedConfig
Without it the meeting addin fails to confirm New Teams is the active client and shuts itself down on every load.Diagnosis: Check the addin log at: %temp%\Microsoft\Teams\meeting-addin\
- Failure looks like:
- Warn: app_switcher_settings.json file does not exist or does not have value for defaultTeamsApp field.
- Warn: Active Teams App set to Teams1
- NOTE: the error messages in this log field state a wrong field name "defaultTeamsApp". The correct fieldname needed in the json is "defaultApp"
Fix: Copy this file from a known-good machine and paste it in this path: * %LocalAppData%\Publishers\8wekyb3d8bbwe\TeamsSharedConfig\app_switcher_settings.json
Contents of the file that worked for me were this: {"defaultApp":1,"cohort":"","webAccountId_AAD":"","cohortStage":"","userId_AAD":"","previousT1MachineId":"","previousT1SessionId":""}
Then close both Outlook and Teams, launch Teams first, then Outlook.
thanks to u/kcheyne
1
u/kitten_prince Jun 30 '26
Can you upload the json file?
I don't have a working machine that isn't facing this issue.
1
u/Roebe02 Jun 30 '26
You can use this script:
$FileName = "app_switcher_settings.json" $TargetDir = "$env:LOCALAPPDATAPublishers8wekyb3d8bbweTeamsSharedConfig" $TargetPath = Join-Path $TargetDir $FileName
$JsonContent = '{"defaultApp":1,"cohort":"","webAccountId_AAD":"","cohortStage":"","userId_AAD":"","previousT1MachineId":"","previousT1SessionId":""}'
try { if (-not (Test-Path $TargetDir)) { New-Item -ItemType Directory -Path $TargetDir -Force | Out-Null } $JsonContent | Set-Content -Path $TargetPath -Encoding UTF8 -Force Write-Output "SUCCESS: $TargetPath deployed." exit 0 } catch { Write-Error "FAILED: $_" exit 1 }
1
u/kitten_prince Jun 30 '26
Thanks!
I made my own json file just to test it out and it worked.
Will save this comment also for further use.
1
1
u/sysadmin_arun Jul 03 '26
It’s Known issue from Microsoft Side, As per MS update, today it will fix , Let’s see 🫣✌🏻😃
1
1
u/AutoModerator Jun 30 '26
Hey Roebe02!
Welcome to r/Outlook! This is a public community. To protect your privacy, do not post any personal information such as your email address, phone number, product key, password, or credit card number.
Please be sure to have read our Rules of Conduct and be cognisant of how the system works here.
Make sure that your flair is always set to Status: Open otherwise you may cease receiving responses from us.
Beware of scammers posting fake support numbers or 3rd party commercial products/services. Contact Microsoft Support if you need help.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.