Additional calendar-related features and issues within Microsoft Teams for business
For VDI users, one likely cause is the classic-to-new Teams transition. When users are assigned the "new Teams only" upgrade policy, the new Teams app can remove classic Teams after a period of time, and then the Teams Meeting add-in may stop loading and be removed from Outlook.
Checks and actions that are supported by the documented guidance:
- Confirm the add-in is active in classic Outlook
- In Outlook, go to File > Options > Add-ins.
- Verify Microsoft Teams Meeting Add-in for Microsoft Office appears in Active Application Add-ins.
- If it appears under Disabled Application Add-ins, select Manage > COM Add-ins > Go, enable it, select OK, and restart Outlook.
- Verify Teams desktop client is installed for affected users
- The meeting add-in cannot be installed if the user only uses the Teams web client.
- Also verify affected users are on Outlook 2016 or later and that Outlook desktop updates are applied.
- Restart in the correct order
- Close both apps.
- Start Teams first, sign in, then start Outlook.
- Check for common conditions that make the add-in disappear
- Make sure users are signed in to the Teams desktop app with a valid commercial account.
- Confirm Outlook and Teams are running in the same context and that Outlook is not running as administrator while Teams is not.
- If Office was installed from the Microsoft Store, the Teams Meeting add-in is not supported. A Click-to-Run Office installation is required.
- If the issue started after moving users to new Teams
- Check whether affected users were assigned the "new Teams only" policy.
- The documented symptom is that after the upgrade, the add-in can be removed from Outlook.
- For non-VDI environments, Microsoft documents reinstall steps for the Teams Meeting add-in after this transition. Since the reported issue is specifically in VDI, this points to the upgrade/policy state as an important differentiator to compare between affected and unaffected users.
- Advanced remediation
- If the add-in still does not appear, Microsoft documents reregistering
Microsoft.Teams.AddinLoader.dllfrom the%LocalAppData%\Microsoft\TeamsMeetingAddinfolder after exiting Outlook and Teams.
- If the add-in still does not appear, Microsoft documents reregistering
- If Outlook is disabling the add-in for performance
- In Outlook Desktop, go to File > Manage COM Add-ins.
- For Microsoft Teams Meeting Add-in for Microsoft Office, select Do not monitor this add-in for the next 30 days or Always enable this add-in.
- If needed, re-enable it from File > Options > Add-ins > Manage: Disabled items > Go.
- Risk: editing the registry is advanced and can affect Outlook behavior if done incorrectly. If using the documented prevention step, add
TeamsAddin.FastConnect=1underHKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Resiliency\DoNotDisableAddinListonly if standard re-enable steps do not hold.
- Verify prerequisites on affected VDI images/users
- Confirm .NET 4.8 and WebView2 are present, because they are required for the Teams Meeting Add-in in Outlook.
A practical way to narrow this down is to compare one affected VDI user and one working VDI user for these exact items: Teams upgrade policy, Office install type, Teams desktop client presence, Outlook elevation state, and whether the add-in files exist under %LocalAppData%\Microsoft\TeamsMeetingAddin.
- Can't create a Teams Meeting in Outlook because the Teams Meeting add-in has become disabled
- Understanding the Microsoft Teams Meeting Add-in for Outlook: Eligibility, Issues, and Troubleshooting
- Admin - Authentication requirements and functionality of the Teams Meeting add-in in Outlook
- Troubleshoot the Teams Meeting add-in in Outlook for Windows
- Resolve Teams Meeting add-in issues in classic Outlook
- Understanding the Microsoft Teams Meeting Add-in for Outlook: Eligibility, Issues, and Troubleshooting