About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
If the New Teams Meeting button has vanished from the Calendar in classic Outlook for Windows, Microsoft's pages describe three situations: Outlook disabled the Teams Meeting add-in, the update to new Teams did not install it, or its installation or registration failed. Start by looking at the add-in list in Outlook Options, which takes a minute and changes nothing.
The new Outlook for Windows is a different case. Microsoft's administrator page says new Outlook does not support the Teams COM add-in and has a native Teams meeting capability instead, so everything below is for classic Outlook.
What the error means
Microsoft's support page describes the add-in's job: "The classic Teams Meeting add-in lets you schedule a Teams meeting from Outlook." It should be installed automatically when Teams and Office 2016, 2019 or 2021 are installed on the Windows PC, and you find it by switching to Calendar view and selecting New Teams Meeting.
When it is missing, the symptoms Microsoft lists on its known-issue page are that the Teams Meeting button is missing when you create a meeting in Outlook Desktop, and that the Teams Meeting Add-in is missing under File > Options > Add-ins when you select Go next to COM Add-ins. That page ties it to an update to new Teams that "did not properly install the Teams Meeting Add-in".
A second known-issue page covers a case where the option is missing from the ribbon because the add-in "becomes disabled". Microsoft says the Teams and Outlook product teams are fixing issues that cause Outlook to disable the add-in for performance reasons.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Add-in disabled by Outlook | Button missing; add-in under Disabled Application Add-ins | File > Options > Add-ins, check the Active and Disabled lists |
| Update to new Teams did not install the add-in | Button missing; add-in absent from the COM Add-ins list | The add-in is missing from File > Options > Add-ins > COM Add-ins, and from Settings > Apps > Installed apps |
| Add-in load behaviour not 3 | Add-in still missing after the other checks | LoadBehavior under the TeamsAddin.FastConnect key is not 3 |
| Policy setting (a managed user) | Add-in still missing after the other checks | Policy values under the Outlook Security key; the trusted add-ins list |
| Teams desktop client not installed | No add-in | Microsoft says the add-in cannot be installed if you use only the Teams web client |
| New Outlook in use | Microsoft says new Outlook does not support the Teams COM add-in | Microsoft says new Outlook does not support the Teams COM add-in |
Microsoft's pages do not rank these.
Prove the cause before changing anything
All of these read only.
- Work out which Outlook is in use. Microsoft's search page says to look for Settings on the ribbon: if there is no Settings option you are in classic Outlook.
- In classic Outlook, select File, then Options, then Add-ins. Check whether Microsoft Teams Meeting Add-in for Microsoft Office is in the Active Application Add-ins list or the Disabled Application Add-ins list.
- In Windows, select Start, Settings, Apps, Installed apps, and search for Teams Meeting Add-in. Note the version. Microsoft's administrator page uses the version to choose the clean-up script: a version starting 1.23 or no result at all calls for one script, and any other version calls for another. The page gives those scripts for non-VDI environments only.
- Check the Teams desktop client is installed and Outlook is version 2016 or later.
- Record the add-in's load behaviour:
reg query "HKCU\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" /v LoadBehavior
The reg query page documents /v <valuename> to query one value. Microsoft's page says the value should be 3.
- For managed users, check whether the Outlook object model prompt policy is set:
reg query "HKCU\SOFTWARE\Policies\Microsoft\Office\16.0\Outlook\Security" /v promptoomaddressinformationaccess
Microsoft's page says a value of 0 means Outlook automatically denies programmatic access requests from any program. If you applied the policy through Cloud Policy service, the page gives HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Cloud\Office\16.0\Outlook\Security as the key, and says Cloud Policy settings take precedence over Group Policy settings on Windows.
Example (illustrative): at contoso.com.au four staff on rds01 lose the button the morning after the company moved from classic Teams to new Teams. File > Options > Add-ins shows no Teams Meeting Add-in in either list, and Installed apps finds nothing for "Teams Meeting Add-in". That matches Microsoft's known issue for a move to new Teams, where the add-in is missing from the COM Add-ins list. The first fix to try is the reinstall through new Teams.
Fix
Try them in this order and stop when the button returns.
Add-in disabled
Microsoft's page says: if the add-in is in the Disabled Application Add-ins list, select Manage, COM Add-ins, Go, then select the check box next to it, select OK in every dialog box and restart Outlook. Note whether the add-in is in the Active or Disabled list.
Risk: The next steps switch on an add-in that Outlook had turned off, possibly because of slow start-up. It can be disabled again.
- In Outlook, select File, Options, Add-ins.
- Under Manage, select COM Add-ins, then Go.
- Select the check box next to Microsoft Teams Meeting Add-in for Microsoft Office.
- Select OK on every open dialog box and restart Outlook.
To undo it: repeat steps 1 to 2, clear the check box and restart Outlook.
If it is under Disabled Items instead, Microsoft's known-issue page says to select File > Options > Add-ins > Manage > Disabled items > Go, select Teams if you see it listed and select Enable, then restart Outlook. It is the same change as the section above, so the Risk and undo above apply. The page also describes File > Manage COM Add-ins and, under the add-in's options, Do not monitor this add-in for the next 30 days, or Always enable this add-in if the first is not offered. Those change how Outlook monitors the add-in and the page gives no way to reverse them, so they are not set out as steps.
Add-in missing after the move to new Teams
Microsoft's known-issue page gives these steps and says they make new Teams install the add-in.
Risk: The next steps uninstall the Teams Meeting Add-in, close Outlook and quit Teams. Anyone using Outlook or Teams meetings on that computer is interrupted. Save open messages first.
- Right-click the Windows Start button and select Settings > Apps > Installed Apps, and search for the Teams Meeting Add-in.
- Select the three dots and select Uninstall.
- Close Outlook.
- Right-click the Teams icon in the system tray and select Quit Teams.
- Restart new Teams. Microsoft says this forces new Teams to reinstall the add-in.
- When Teams Meeting Add-in appears in the list of installed apps again, restart Outlook.
To undo it: the uninstall is the step being undone, and Microsoft's page says that restarting new Teams reinstalls the add-in. If it does not return, the page gives no other route.
Microsoft's administrator page adds that if no result appears, or the version starts with 1.23, an UninstallOldTMA.ps1 script is run from an elevated PowerShell window, and for any other version an UninstallTMA.ps1 script is run from a PowerShell window. Microsoft's page gives these steps for non-VDI environments only, and links to the scripts for download. The scripts remove the Teams Meeting Add-in, and Microsoft's page gives no undo for either script, so they are not set out as steps here.
Re-register the add-in loader (administrators)
Microsoft says to check the Teams desktop client is installed, Outlook is 2016 or later and updates are applied, then exit Outlook and Teams.
Microsoft's page lists no registry key for this registration, so it cannot be saved as a whole; the load-behaviour key is saved in the next section. Before you start, note the folder under %LocalAppData%\Microsoft\TeamsMeetingAddin. Microsoft says to select the subfolder whose name matches the version number, or the highest build number if several match, and gives %LocalAppData%\Microsoft\TeamsMeetingAddin\1.0.23334.11 as an example of the path.
Risk: The next command registers Microsoft.Teams.AddinLoader.dll with the /n /i:user options that Microsoft gives. Microsoft's page gives no command to reverse it, so there is no way back from it other than the reinstall route above. Choose the command for the bitness of Office, not of Windows.
Open an elevated Command Prompt window and run the command for your Office installation. For 64-bit Office:
%SystemRoot%\System32\regsvr32.exe /n /i:user <path>\x64\Microsoft.Teams.AddinLoader.dll
For 32-bit Office:
%SystemRoot%\SysWOW64\regsvr32.exe /n /i:user <path>\x86\Microsoft.Teams.AddinLoader.dll
Replace <path> with the folder you noted. Then restart the Teams desktop client, sign out and back in, and restart Outlook, making sure Outlook is not running in Administrator mode.
There is no way back from the registration itself: Microsoft's page gives no command to reverse it. If the add-in still misbehaves afterwards, the route is the uninstall and reinstall through new Teams described above.
The load behaviour is not 3
Save first, with Outlook closed. Create C:\Temp first if it does not exist. If the export reports that the key does not exist, stop: the step below does not apply, because there is no LoadBehavior value to change:
reg export "HKCU\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect" C:\Temp\teamsaddin-before.reg
Risk: The next step edits a registry value that controls whether Outlook loads the Teams Meeting Add-in. Microsoft warns that incorrect registry entries can cause serious system problems.
- Open RegEdit.exe and go to
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect. - If there is no LoadBehavior value, stop. If LoadBehavior has a value other than 3, change it to 3.
- Restart Outlook.
To undo it: with Outlook closed, run the import, which writes back the value you saved:
reg import C:\Temp\teamsaddin-before.reg
Policy checks
If promptoomaddressinformationaccess is 0, Microsoft's page says to check the Configure trusted add-ins policy. An administrator can disable or unconfigure the policy, or keep it and make sure Microsoft.Teams.AddinLoader.dll is on the list with the correct hash, which the page says can be computed with the Get-FileHash cmdlet. Microsoft notes the DLL is updated with the Teams client, so the hash must be kept in step. Microsoft's page gives no steps for these policy edits.
Confirm the fix
- In Calendar view, New Teams Meeting is shown, and a new meeting carries a join link.
- File, Options, Add-ins lists the add-in under Active Application Add-ins.
- Installed apps lists Teams Meeting Add-in with a version.
What to watch afterwards
- A return of the button's absence after the next Outlook or Teams update. The known-issue page dated 2023-05-25 says there is "ongoing work to address this class of issue".
- Whether .NET 4.8 and WebView2 are installed. Microsoft's known-issue page cites message centre post MC392289 and notes that in some support cases installing them helped.
Read next
Related articles you may want next.
- TroubleshootingOutlook disabled an add-in because it was slow (Event ID 59): how to keep it enabledOutlook disabled an add-in for being slow and logged Event ID 59. Read the event, then use Always enable this add-in with the undo steps.Read article
- TroubleshootingClearing the Teams cache on Windows: the steps Microsoft gives and the problems it says not to clear it forMicrosoft says clearing the Teams cache does not fix missing messages or channels and deletes diagnostic logs. Steps for classic and new Teams on Windows.Read article
- TroubleshootingCannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened: causes and fixesOutlook says: The set of folders cannot be opened. Two documented causes and a repair tool, how to tell them apart and the order to try each.Read article
Risks and limits
These commands have not been run or lab-tested.
Microsoft's pages for this fault describe classic Outlook and the Teams desktop client. They do not give a fix for the new Outlook beyond a pointer to another Microsoft page. A different symptom, missing join details when a delegate schedules a meeting for a delegator whose mailbox is hidden from the address list, is described on Microsoft's administrator page and has its own Exchange Online PowerShell fix.
Sources
- Teams Meeting add-in is missing in Outlook Desktop after updating to New Teams — Microsoft Support, page dated 2024-08-06, accessed 22 November 2026
- Can't create a Teams Meeting in Outlook because the Teams Meeting add-in has become disabled — Microsoft Support, page dated 2023-05-25, accessed 22 November 2026
- Troubleshoot the Teams Meeting add-in in Outlook for Windows — Microsoft Support, date not shown, accessed 22 November 2026
- Resolve Teams Meeting add-in issues in classic Outlook — Microsoft Learn, page dated 2026-07-15, accessed 22 November 2026
- Troubleshooting Outlook search issues — Microsoft Support, date not shown, accessed 22 November 2026
- reg query — Microsoft Learn, page dated 2023-02-03, accessed 22 November 2026
- reg export — Microsoft Learn, page dated 2023-02-03, accessed 22 November 2026
- reg import — Microsoft Learn, page dated 2023-02-03, accessed 22 November 2026
This article was originally published on .