Fix Teams Meeting Add-in Missing from Outlook After New Teams Update

The panic version of this ticket is simple: users updated to New Teams, opened classic Outlook, and the Teams Meeting button disappeared. The calendar still works. Teams still works. But Outlook can no longer create a Teams meeting, which means executives, delegates, and help desk queues start escalating fast.

This guide focuses on the common enterprise failure path: Teams Meeting Add-in missing from classic Outlook after a New Teams update or classic Teams removal. It gives you a safe triage order, the registry keys to check, and PowerShell commands you can run without reinstalling Microsoft 365 Apps first.

Microsoft’s support guidance separates two important cases: the new Outlook for Windows does not use the classic Teams COM add-in, while classic Outlook still depends on the Teams Meeting Add-in for Microsoft Office. Do not troubleshoot both clients the same way.

Quick Fix Checklist

Use this order before you wipe a profile or reinstall Office:

Confirm the user is in classic Outlook, not new Outlook for Windows.
Close Outlook, Teams, and any OUTLOOK.EXE process left in Task Manager.
Start New Teams once and let it finish installing/updating the meeting add-in.
Open Settings → Apps → Installed apps and search for Microsoft Teams Meeting Add-in for Microsoft Office.
In Outlook, check File → Options → Add-ins and confirm Microsoft Teams Meeting Add-in for Microsoft Office is active.
If it is disabled, re-enable it from Manage: COM Add-ins.
Check LoadBehavior under TeamsAddin.FastConnect and set it to 3 if it was changed.
If the add-in files exist but Outlook will not load them, re-register Microsoft.Teams.AddinLoader.dll.
If the issue started immediately after moving from classic Teams to New Teams, remove the old Teams Meeting Add-in package and let New Teams reinstall it.
Check Office trusted add-in policy if the add-in appears on some machines but not on policy-managed devices.

Do not start with a full Office repair. Most cases are a disabled COM add-in, stale add-in registration, or a New Teams migration state where the old add-in was removed but the new one did not finish installing.

Symptoms

Admins usually see one of these reports:

The Teams Meeting button is missing from the Outlook calendar ribbon.
The add-in appears under Disabled Application Add-ins.
The add-in is not listed under active COM add-ins.
The user can schedule Teams meetings inside Teams, but not from Outlook.
The issue started after a New Teams update, a Teams upgrade policy change, or removal of classic Teams.
Delegates can create Outlook meetings, but Teams join details are not inserted.
The problem affects only some users in the same Microsoft 365 Apps channel.

That last clue matters. If only some users are affected, look for profile-level add-in state, missing per-user TeamsMeetingAddin files, or a policy difference before blaming the tenant.

Root Cause

Classic Outlook uses a COM add-in named Microsoft Teams Meeting Add-in for Microsoft Office. The registration lives under the current user’s Outlook add-in registry hive, and the loader DLL is installed under the user’s local Teams meeting add-in folder.

After a New Teams rollout, the add-in can disappear for four common reasons:

Classic Teams was removed before the Teams Meeting Add-in was reinstalled for New Teams. Microsoft documents this as a known upgrade path issue when moving from classic Teams to New Teams.
Outlook disabled the COM add-in. Outlook may disable add-ins after slow startup, crashes, or policy-controlled add-in behavior.
The LoadBehavior registry value changed from 3. A value other than 3 prevents normal load at Outlook startup.
Trusted add-in policy blocks the loader DLL. If your organization requires trusted add-ins, the Teams add-in DLL and hash must match policy.

There is also a separate case for new Outlook for Windows. New Outlook does not support the Teams COM add-in. It has native Teams meeting scheduling instead. If a user is in new Outlook, the absence of the classic COM add-in is expected.

Where to Check First

1. Confirm the Outlook client

Ask the user which Outlook they opened:

Classic Outlook for Windows: COM add-ins are supported. Continue this guide.
New Outlook for Windows: the Teams COM add-in is not supported. Use the built-in Teams meeting scheduling experience instead.
Outlook on the web: the classic COM add-in is not involved.

This prevents a common false positive where the help desk tries to re-register a COM add-in for a client that cannot load COM add-ins.

2. Check Outlook add-in state

On the affected device:

Open classic Outlook.
Go to File → Options → Add-ins.
Look for Microsoft Teams Meeting Add-in for Microsoft Office.
If it is under Disabled Application Add-ins, select Manage → COM Add-ins → Go.
Check the box for the Teams meeting add-in.
Restart Outlook.

If the add-in returns after this step, capture the device name and Outlook version. A group of similar machines may have the same add-in resiliency issue.

3. Check the installed Teams Meeting Add-in package

Open Settings → Apps → Installed apps and search for:

Teams Meeting Add-in

You should see Microsoft Teams Meeting Add-in for Microsoft Office. If it is not present, start New Teams and wait a few minutes. Microsoft guidance for New Teams migration says the New Teams app can reinstall the Teams meeting add-in after it starts.

If it still does not appear, move to the removal and reinstall workflow below.

PowerShell Triage Commands

Run these from the affected user’s session, not as a different admin account. The add-in is user-scoped.

Check Outlook processes

Get-Process OUTLOOK,ms-teams,Teams -ErrorAction SilentlyContinue |
  Select-Object ProcessName, Id, Path

Close Outlook before re-registering the add-in:

Get-Process OUTLOOK -ErrorAction SilentlyContinue | Stop-Process -Force

Find the TeamsMeetingAddin folder

$addinRoot = Join-Path $env:LOCALAPPDATA "Microsoft\TeamsMeetingAddin"
Get-ChildItem $addinRoot -Directory -ErrorAction SilentlyContinue |
  Sort-Object Name -Descending |
  Select-Object -First 5 FullName

If the folder does not exist, the meeting add-in is not installed for that user. Start New Teams, wait, and check Installed apps again.

Check Outlook COM add-in registration

$regPath = "HKCU:\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect"
Get-ItemProperty $regPath -ErrorAction SilentlyContinue |
  Select-Object FriendlyName, Description, LoadBehavior, Manifest

The key value to inspect is:

LoadBehavior = 3

If it is missing or set to another value, set it back to 3:

New-Item -Path "HKCU:\SOFTWARE\Microsoft\Office\Outlook\Addins" -Name "TeamsAddin.FastConnect" -Force | Out-Null
Set-ItemProperty -Path $regPath -Name LoadBehavior -Type DWord -Value 3

Restart Outlook and check whether the button returns.

Re-register the Teams Add-in Loader

Use the highest version folder under %LocalAppData%\Microsoft\TeamsMeetingAddin. Then run the registration command for the matching DLL path.

$addinRoot = Join-Path $env:LOCALAPPDATA "Microsoft\TeamsMeetingAddin"
$latest = Get-ChildItem $addinRoot -Directory |
  Sort-Object Name -Descending |
  Select-Object -First 1

$loader64 = Join-Path $latest.FullName "x64\Microsoft.Teams.AddinLoader.dll"
$loader32 = Join-Path $latest.FullName "x86\Microsoft.Teams.AddinLoader.dll"

if (Test-Path $loader64) {
  & "$env:SystemRoot\System32\regsvr32.exe" /n /i:user $loader64
}

if (Test-Path $loader32) {
  & "$env:SystemRoot\SysWOW64\regsvr32.exe" /n /i:user $loader32
}

Then restart Teams first, followed by Outlook. Also confirm Outlook is not running as administrator. Outlook running elevated can cause add-in loading and identity behavior that does not match the user’s normal session.

New Teams Upgrade Repair Workflow

Use this when the failure started after classic Teams was removed or a Teams upgrade policy moved the user to New Teams.

Close Outlook and Teams.
Check Installed apps for Microsoft Teams Meeting Add-in for Microsoft Office.
If the add-in is missing or stuck on an old package, remove the Teams Meeting Add-in from Installed apps.
Start New Teams.
Wait for the Teams Meeting Add-in to reappear in Installed apps.
Restart Outlook.
Re-check File → Options → Add-ins.

Microsoft’s troubleshooting article calls out this exact pattern: after moving from classic Teams to New Teams, the Teams meeting add-in may not load and may be removed from Outlook. The fix is to remove the stale Teams Meeting Add-in package and let New Teams reinstall the supported add-in.

For scripted remediation, test on a pilot device first. Package names and uninstall behavior can vary by Teams Meeting Add-in version and app deployment channel.

Policy Checks for Managed Devices

If the add-in works on unmanaged devices but not on corporate builds, check Outlook add-in policy.

Registry locations to inspect:

HKCU\SOFTWARE\Policies\Microsoft\Office\16.0\Outlook\Security
HKCU\SOFTWARE\Policies\Microsoft\Cloud\Office\16.0\Outlook\Security

If your organization uses Configure trusted add-ins, make sure Microsoft.Teams.AddinLoader.dll is trusted and that the hash matches the deployed DLL.

You can calculate the hash with:

Get-FileHash "$env:LOCALAPPDATA\Microsoft\TeamsMeetingAddin\<version>\x64\Microsoft.Teams.AddinLoader.dll" -Algorithm SHA256

Replace <version> with the actual folder name. Keep the placeholder in backticks if you document this in an internal runbook so MDX or wiki parsers do not treat it as an HTML tag.

Delegate and GAL Edge Case

There is one extra symptom that looks like an add-in failure but has a different root cause: the meeting is created, but Teams join details are missing for a delegate-created meeting.

Microsoft documents a case where this happens if the delegator’s mailbox is hidden from the Global Address List. The add-in cannot retrieve the required mailbox information to populate Teams meeting details.

Check the mailbox visibility before reinstalling anything:

Get-Mailbox user@contoso.com | Select-Object DisplayName, HiddenFromAddressListsEnabled

If the mailbox is hidden, test with a visible mailbox or adjust the GAL visibility according to your organization’s policy. Then have the delegate restart Outlook and create a new meeting request.

Logs and Evidence to Collect

For a repeat incident, collect these items before rebuilding the profile:

Outlook version and channel from File → Office Account.
Teams client version from New Teams settings.
Installed version of Microsoft Teams Meeting Add-in for Microsoft Office.
Screenshot or export of Outlook File → Options → Add-ins.
Value of HKCU\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect\LoadBehavior.
Contents of %LocalAppData%\Microsoft\TeamsMeetingAddin.
Whether the machine is under Cloud Policy or Group Policy for trusted add-ins.
Whether the user recently moved from classic Teams to New Teams.

A quick evidence bundle:

$report = [ordered]@{
  User = $env:USERNAME
  Computer = $env:COMPUTERNAME
  AddinRootExists = Test-Path "$env:LOCALAPPDATA\Microsoft\TeamsMeetingAddin"
  LoadBehavior = (Get-ItemProperty "HKCU:\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" -ErrorAction SilentlyContinue).LoadBehavior
  OutlookRunning = [bool](Get-Process OUTLOOK -ErrorAction SilentlyContinue)
}

[pscustomobject]$report | Format-List

Prevention

For a clean New Teams rollout, add these checks to your deployment plan:

Pilot the New Teams upgrade policy with users who schedule meetings from classic Outlook every day.
Include delegates and executive assistants in the pilot, not only standard users.
Monitor whether Microsoft Teams Meeting Add-in for Microsoft Office remains installed after classic Teams removal.
Avoid aggressive cleanup scripts that remove Teams-related per-user folders before New Teams finishes add-in setup.
Document the LoadBehavior = 3 check for help desk technicians.
If you enforce trusted add-ins, update the trusted DLL hash whenever the Teams Meeting Add-in version changes.
Train support staff to separate classic Outlook, new Outlook, and Outlook on the web before troubleshooting.

When to Escalate

Escalate to Microsoft support or your Microsoft 365 Apps owner when:

The add-in disappears repeatedly after being re-enabled.
Multiple users lose the add-in immediately after the same Teams upgrade policy applies.
The TeamsMeetingAddin folder is recreated but the loader DLL fails to register.
Policy-managed devices block the add-in while unmanaged devices load it normally.
Outlook crashes when loading TeamsAddin.FastConnect.

For most incidents, the fix is not a reinstall of Office. Confirm the client, restore the COM add-in state, repair LoadBehavior, re-register the loader if needed, and let New Teams reinstall the meeting add-in after migration.

Sources

Microsoft Learn: Resolve issues that affect the Teams Meeting add-in for classic Outlook
Microsoft Support: Schedule a Microsoft Teams meeting from Outlook