The Teams Meeting button is missing from Outlook
The New Teams Meeting button is absent from the Outlook calendar ribbon. The add-in is installed by Teams rather than by Office, so it goes missing whenever the handshake between the two fails — most often after an update to either.
What you see
No Teams Meeting button on the Calendar tab, and the add-in either missing from File → Options → Add-ins or listed as inactive. Meetings can still be created in the Teams client itself.
What is actually wrong
Teams registers the add-in for Outlook, and the registration depends on both being installed for the same user, at the same architecture, with Teams signed in and Outlook not elevated. Any of those breaking leaves the add-in registered but not loading, or deregistered entirely. Running Outlook as administrator is a common and non-obvious cause.
Codes and articles
Start here — find out which fix applies
A script that runs the 5 inspection commands from the write-up below and prints what each one returned. It reads the machine and changes nothing — every command that could write, delete, start or stop is excluded from it by construction. Run this first, then pick the fix its output points at.
Fixes (3)
Rule out the three conditions that silently prevent it loading
Always check these first. Each takes seconds and each produces the symptom with no error message.
Confirm Outlook is not running elevated. An Outlook started as administrator will not load an add-in registered for the standard user.
Get-Process OUTLOOK -IncludeUserName -ErrorAction SilentlyContinue | Select-Object Name, UserNameThis is the most commonly missed cause. Someone starts Outlook as administrator once to fix something else, the shortcut keeps the setting, and the Teams button is gone from then on with nothing to explain it.
Confirm Teams is installed and has been signed in at least once on this profile. The add-in is not registered until Teams has run and authenticated.
Confirm Teams and Office are the same architecture. A 32-bit Teams add-in will not load into 64-bit Outlook.
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' | Select-Object PlatformClose both applications completely, start Teams first, let it sign in, then start Outlook.
The order matters. Teams performs the registration at startup, and Outlook reads the add-in list at its own startup — so Outlook first means Outlook looks before Teams has written anything.
Re-enable an add-in that is listed but inactive
The add-in appears in the Add-ins list as inactive or disabled.
Close Outlook.
Get-Process OUTLOOK -ErrorAction SilentlyContinue | Stop-Process -ForceRead the current LoadBehavior.
Get-ItemProperty 'HKCU:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect' -ErrorAction SilentlyContinue | Select-Object LoadBehavior, Description3 is loaded at startup. 2 means Outlook tried it, it failed, and it was turned off. 0 means someone disabled it deliberately.
Set it back to load at startup.
Set-ItemProperty 'HKCU:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect' -Name LoadBehavior -Type DWord -Value 3Clear the resiliency lists, which override LoadBehavior and are the reason it keeps reverting to 2.
Remove-Item 'HKCU:\Software\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems' -Recurse -Force -ErrorAction SilentlyContinueRemove-Item 'HKCU:\Software\Microsoft\Office\16.0\Outlook\Resiliency\CrashingAddinList' -Recurse -Force -ErrorAction SilentlyContinue
Setting LoadBehavior to 3 without clearing these puts it straight back to 2 on the next start, which is why this fix appears not to work when only half of it is done.
Start Outlook and confirm the button is back.
Get-ItemProperty 'HKCU:\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect' | Select-Object LoadBehaviorMake Teams register the add-in again
The add-in is not listed at all, usually after an update to Teams or Office.
Close Outlook and Teams completely.
Get-Process OUTLOOK,ms-teams,Teams -ErrorAction SilentlyContinue | Stop-Process -ForceCheck whether the add-in files are present before assuming they need reinstalling.
Get-ChildItem "$env:LOCALAPPDATA\Microsoft\TeamsMeetingAddin" -Recurse -Filter '*.dll' -ErrorAction SilentlyContinue | Select-Object FullName, LastWriteTimeIf the DLL is there, this is a registration problem and Teams can fix it itself. If it is absent, Teams needs repairing or reinstalling and no registry work will help.
Sign out of Teams, then sign back in. Teams re-registers the add-in as part of signing in, and this resolves it more often than anything manual.
If that does not work, repair Teams from Settings → Apps → Installed apps → Microsoft Teams → Advanced options → Repair. For the classic client, uninstall and let it reinstall on next sign-in.
Start Teams first and let it fully sign in, then start Outlook.
If it is still missing across many machines, check for a policy blocking the Outlook add-in in the Teams admin centre meeting policies — that is a supported setting and it will override everything done on the client.
Related faults
Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.