The original version of this article covered the missing Skype for Business / Lync meeting button in Outlook. Skype for Business reached end of life on July 31, 2021 — it has been replaced by Microsoft Teams. This updated guide covers the current equivalent problem: the Microsoft Teams Meeting add-in disappearing from Outlook, which remains one of the most persistent helpdesk tickets in any Microsoft 365 environment. The fix depends on which of several distinct root causes applies to your situation — this guide covers all of them.

Detail
Last UpdatedMarch 2026
Applies ToClassic Outlook (2016, 2019, M365 Apps), New Outlook
Add-in NameMicrosoft Teams Meeting Add-in for Microsoft Office
COM Registry KeyHKCU\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect
DifficultyBeginner to Intermediate

Quick Diagnosis — Which Situation Are You In?

The Teams Meeting button disappears for several completely different reasons. Identify yours first to skip straight to the right fix:

  • Button was there, now gone after an update → Outlook’s resilience mechanism auto-disabled the add-in. Go to Fix 1.
  • Button missing after migrating from Classic Teams to New Teams → Classic Teams uninstall removed shared registry keys. Go to Fix 4.
  • Add-in visible in COM Add-ins but greyed out / cannot enable it → LoadBehavior registry issue or Outlook admin mode mismatch. Go to Fix 3.
  • Using New Outlook (not Classic) → No COM add-in needed — built-in toggle. Go to Fix 6.
  • Button keeps disappearing after every Outlook restart → Outlook performance resilience keeps disabling it. Go to Fix 2 and Fix 3.

Fix 1: Re-enable from Disabled Add-ins (Quickest Fix)

Outlook automatically disables add-ins it detects as slow or unstable. The Teams add-in frequently ends up here after an update. This is the simplest fix and resolves the issue in the majority of cases.

  1. Open Outlook → File → Options → Add-ins
  2. At the bottom next to Manage, change the dropdown from “COM Add-ins” to “Disabled Items” → click Go
  3. If Microsoft Teams Meeting Add-in for Microsoft Office appears here, select it and click Enable
  4. Restart Outlook

If the add-in keeps disappearing after each restart, continue to Fix 2 to prevent Outlook from disabling it again.

Fix 2: Prevent Outlook from Auto-Disabling the Add-in

Outlook has a resilience mechanism that disables add-ins that slow it down. Add the Teams add-in to the DoNotDisableAddinList registry key to permanently prevent Outlook from disabling it:

# Prevent Outlook from auto-disabling the Teams Meeting add-in
$resiliencyPath = "HKCU:\Software\Microsoft\Office\16.0\Outlook\Resiliency\DoNotDisableAddinList"

if (-not (Test-Path $resiliencyPath)) {
    New-Item -Path $resiliencyPath -Force | Out-Null
}

# Add TeamsAddin.FastConnect to the DoNotDisable list
Set-ItemProperty -Path $resiliencyPath -Name "TeamsAddin.FastConnect" -Value 1 -Type DWord

Write-Host "Teams add-in added to DoNotDisableAddinList. Restart Outlook to apply."

Also clear any existing disabled add-in entries that may reference Teams:

# Clear DisabledItems entries that may include the Teams add-in
$disabledItemsPath = "HKCU:\Software\Microsoft\Office\16.0\Outlook\Resiliency\DisabledItems"

if (Test-Path $disabledItemsPath) {
    $items = Get-ItemProperty -Path $disabledItemsPath
    $items.PSObject.Properties |
        Where-Object { $_.Name -notlike "PS*" } |
        ForEach-Object {
            Write-Host "Removing disabled item: $($_.Name)"
            Remove-ItemProperty -Path $disabledItemsPath -Name $_.Name -ErrorAction SilentlyContinue
        }
    Write-Host "Disabled items cleared. Restart Outlook."
} else {
    Write-Host "No DisabledItems registry key found — nothing to clear."
}

Fix 3: Set LoadBehavior to 3 in Registry

The LoadBehavior registry value for the Teams add-in should be set to 3. If it has any other value, the add-in will not load correctly. Check and fix this via PowerShell:

# Fix Teams add-in LoadBehavior registry key
$addinPath = "HKCU:\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect"

if (Test-Path $addinPath) {
    $loadBehavior = (Get-ItemProperty -Path $addinPath).LoadBehavior
    Write-Host "Current LoadBehavior: $loadBehavior"

    if ($loadBehavior -ne 3) {
        Set-ItemProperty -Path $addinPath -Name "LoadBehavior" -Value 3 -Type DWord
        Write-Host "LoadBehavior set to 3. Restart Outlook."
    } else {
        Write-Host "LoadBehavior is already correct (3)."
    }
} else {
    Write-Host "TeamsAddin.FastConnect registry key not found."
    Write-Host "Teams may not be installed or the add-in registration is missing."
    Write-Host "Proceed to Fix 4 or Fix 5."
}

If the entire TeamsAddin.FastConnect key is missing, the add-in registration is gone — typically caused by a Classic Teams uninstall. Continue to Fix 4.

Fix 4: Repair New Teams to Restore Missing Registry Keys

When Classic Teams is uninstalled as part of a migration to New Teams, the uninstall can remove the shared registry keys for the Teams meeting add-in. Reinstalling or repairing New Teams recreates the required registry keys. This is the most common cause of the button disappearing after a Classic → New Teams migration.

  1. Close both Outlook and Teams completely (including from the system tray)
  2. Go to Settings → Apps → Installed apps → find Microsoft Teams
  3. Click the three dots → Modify → Repair
  4. Once repair completes, start Teams first, then Outlook

The repair process reinstalls the add-in and recreates all required registry keys. After Outlook loads, go to File → Options → Add-ins → COM Add-ins → Go and verify the Teams add-in is now listed and checked.

Fix 5: Check Prerequisites — .NET 4.8 and WebView2

The Teams Meeting add-in requires both .NET Framework 4.8 and Microsoft Edge WebView2 Runtime to function. If either is missing, the add-in will fail to load or become disabled. This is a common cause on freshly imaged machines or after major Windows upgrades.

# Check .NET Framework 4.8 installation
$dotNetPath = "HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full"
if (Test-Path $dotNetPath) {
    $release = (Get-ItemProperty -Path $dotNetPath).Release
    # 528040 = .NET 4.8 on Win10 1903+
    if ($release -ge 528040) {
        Write-Host ".NET Framework 4.8 is installed (Release: $release)"
    } else {
        Write-Host "WARNING: .NET Framework 4.8 not found (Release: $release). Install from Microsoft."
    }
} else {
    Write-Host "WARNING: .NET Framework 4.x not found."
}

# Check WebView2 Runtime installation
$webView2Paths = @(
    "HKLM:\SOFTWARE\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}",
    "HKLM:\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}"
)

$webView2Found = $false
foreach ($path in $webView2Paths) {
    if (Test-Path $path) {
        $version = (Get-ItemProperty -Path $path -ErrorAction SilentlyContinue).pv
        Write-Host "WebView2 Runtime installed: v$version"
        $webView2Found = $true
        break
    }
}

if (-not $webView2Found) {
    Write-Host "WARNING: WebView2 Runtime not found. Download from Microsoft Edge developer site."
}

Fix 6: New Outlook — No COM Add-in Needed

In New Outlook, the Teams meeting experience is integrated differently — instead of a separate COM add-in, there is a built-in Teams meeting toggle directly in the event creation window. If you are using New Outlook and the toggle is missing:

  1. Ensure you are signed in to both Outlook and Teams with the same work or school account
  2. Confirm you are using the New Teams client (not Classic Teams)
  3. If the toggle is still missing, force a re-sync: close Outlook → right-click Teams in the system tray → Quit → start Teams and sign in → start Outlook again

Note: if you switch between New Outlook and Classic Outlook on the same machine, the COM add-in approach applies to Classic Outlook and the built-in toggle applies to New Outlook — they are separate systems.

Fix 7: Check Outlook Is Not Running as Administrator

If Outlook is running with elevated privileges (Run as Administrator) and Teams is not, the add-in will not appear. Both applications must run in the same privilege context.

  1. Right-click the Outlook shortcut → Properties → Compatibility
  2. Ensure Run this program as an administrator is unchecked
  3. Repeat for the Teams shortcut
  4. Restart both applications

Fleet-Wide Fix via Intune Remediation or SCCM Script

If many users are affected simultaneously — typically after a Teams or Office update — deploy the combined fix as an Intune Remediation or SCCM script. This script applies the three most effective registry fixes in a single pass:

# Remediation script: Fix Teams Meeting add-in for all users on machine
# Run as SYSTEM via Intune Platform Script or SCCM

$userProfiles = Get-ChildItem "C:\Users" | Where-Object { $_.Name -notmatch "^(Public|Default|All Users)" }

foreach ($profile in $userProfiles) {
    $sid = (New-Object System.Security.Principal.NTAccount($profile.Name)).Translate(
        [System.Security.Principal.SecurityIdentifier]).Value

    $hivePath = "HKU:\$sid"

    # Load user hive if not already loaded
    if (-not (Test-Path $hivePath)) {
        reg load "HKU\$sid" "$($profile.FullName)\NTUSER.DAT" 2>$null
    }

    $addinPath = "HKU:\$sid\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect"
    $resiliencyPath = "HKU:\$sid\Software\Microsoft\Office\16.0\Outlook\Resiliency"

    if (Test-Path $addinPath) {
        # Fix LoadBehavior
        Set-ItemProperty -Path $addinPath -Name "LoadBehavior" -Value 3 -Type DWord -ErrorAction SilentlyContinue
    }

    if (Test-Path $resiliencyPath) {
        # Clear DisabledItems
        $disabledPath = "$resiliencyPath\DisabledItems"
        if (Test-Path $disabledPath) {
            Remove-Item -Path $disabledPath -Recurse -Force -ErrorAction SilentlyContinue
        }

        # Add to DoNotDisable list
        $doNotDisablePath = "$resiliencyPath\DoNotDisableAddinList"
        if (-not (Test-Path $doNotDisablePath)) {
            New-Item -Path $doNotDisablePath -Force | Out-Null
        }
        Set-ItemProperty -Path $doNotDisablePath -Name "TeamsAddin.FastConnect" -Value 1 -Type DWord -ErrorAction SilentlyContinue
    }

    # Unload hive if we loaded it
    reg unload "HKU\$sid" 2>$null
}

Write-Host "Teams add-in registry fix applied for all user profiles."

Fix Summary — Quick Reference

FixWhen to UseEffort
1. Re-enable from Disabled ItemsButton was there, now gone after updateLow
2. DoNotDisableAddinList registryButton keeps disappearing after every restartLow
3. Set LoadBehavior to 3Add-in greyed out or cannot be enabledLow
4. Repair New TeamsGone after Classic → New Teams migrationLow
5. Install .NET 4.8 and WebView2Fresh image or after major OS upgradeLow
6. New Outlook toggleUsing New Outlook — no COM add-in appliesLow
7. Remove Run as Administrator flagAdd-in not loading, Outlook running elevatedLow
Fleet script (Intune / SCCM)Multiple users affected after an updateMedium

Summary

The missing Teams Meeting button in Outlook has been a persistent helpdesk staple since 2020 and shows no sign of going away — every Teams update can corrupt the add-in registration, and the problem reappears for users across organisations regularly in 2025 and 2026. The fix tree is well-understood: start with re-enabling from Disabled Items, add the DoNotDisableAddinList registry key to prevent recurrence, check LoadBehavior, and repair Teams if the registry keys are missing entirely.

  • Start with File → Options → Add-ins → Disabled Items — resolves the majority of cases in under a minute
  • Add TeamsAddin.FastConnect = 1 to DoNotDisableAddinList to prevent Outlook from auto-disabling it again
  • Ensure LoadBehavior = 3 at HKCU\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect
  • After a Classic → New Teams migration, repair New Teams to restore missing registry keys
  • For fleet-wide recurrence, deploy the combined registry fix script via Intune Remediation