New Teams meeting add-in is missing from outlook

Anonymous
2023-10-22T10:55:25+00:00

Hi,

I have a PC with windows 11 and Office 365. I have installed the New Teams on it.
the user cannot create a teams meeting from outlook calendar.

When I looked for the add-in Options>Add-ins, I didnt see the add-in there, not even in the inactive or the disabled.

The add-in is installed when I looked in %AppData\local\microsoft\TeamsMeetingAddin..

I tried to uninstall Teams but again same problem.

I took the plugin from a PC that can launch teams meetings from outlook and put it in the folder of the PC that cant and it worked for a day now its not.

thank you

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

105 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-12T17:00:35+00:00

    The Private Message helps only the one user. Please place the resolution for everyone to see.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-03-06T09:54:37+00:00

    Hi,

    I have a PC with windows 11 and Office 365. I have installed the New Teams on it.
    the user cannot create a teams meeting from outlook calendar.

    When I looked for the add-in Options>Add-ins, I didnt see the add-in there, not even in the inactive or the disabled.

    The add-in is installed when I looked in %AppData\local\microsoft\TeamsMeetingAddin..

    I tried to uninstall Teams but again same problem.

    I took the plugin from a PC that can launch teams meetings from outlook and put it in the folder of the PC that cant and it worked for a day now its not.

    thank you

    This problem has really been resolved now as Microsoft have a working 64 bit plugin for the new Teams and a 64 bit install for the new teams.
    The steps are:

    With Microsoft Teams Classic "Switch to New Teams",

    Then:

    Look in programs and features and uninstall Teams Machine wide installer.

    Look in programs and features and try to uninstall Teams Classic - It will say it is already uninstalled,
    Look in programs and features and uninstall the Teams plugin
    Now:
    Restart the computer
    Start Teams and make sure it is logged in. - Very important.

    Open Outlook.
    Click on Calendar and hey presto the plugin is there and finally working correctly!
    What a faff.

    For the more technical we also found that Outlook was still reporting many instances of the Teams Plugin in Slow addins when we clicked File in Outlook. as a result of our many efforts to resolve this nonsense.
    This was solved by removing them from the registry. There are lots of notes on this on the internet.

    Colin

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-02-28T16:29:45+00:00

    A new version was released to fix the missing add-in issue, so you should be good now.

    Is the Teams version to fix this 24004.1307.2669.7070? Because I am on that version with Outlook on the latest version of 2401 (Build 17231.20236) And still not showing in the calendar with the Teams Meeting Addin.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-02-26T15:05:49+00:00

    I'd be interested in this link too ... can't see where to do the update

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-02-13T21:01:49+00:00

    Why is the TeamsMeetingAddIn.msi failing to install in your scenario?
    GPO? AppLocker?

    The best suggestion we can give would be to run a script that deploys TMA, as described here
    New Microsoft Teams for Virtualized Desktop Infrastructure (VDI) - Microsoft Teams | Microsoft Learn

    Is this ONLY supported for VDI? The article linked talks about cases like "DisableUserInstalls", and then goes on to suggest installing to a per machine location with ALLUSERS=1, etc. Is this valid for use on a fleet of many thousands of workstations where MSI per user installs are disabled?

    We are still looking for an answer on how to handle this in a supported way, that doesn't require us to remove the policy of "DisableUserInstalls"

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments