Forum Discussion

CPatMAV's avatar
CPatMAV
Copper Contributor
Apr 22, 2020

Split Teams meeting

Organizer created a single instance meeting using the Outlook Teams Add-in and sent out the invite to whole company. Total attendees would have been under the 250 limit. 10-15 mins before the meetin...
  • AV_Analyst's avatar
    Jun 17, 2021

    CPatMAV 

    I finally found my answer to this problem. Here's what was happening:

     

    (TL;DR: My User pasted the Teams Meeting info I created for her into ANOTHER Teams meeting thus having two separate meeting links in her invitation. Details follow)

     

    As an E5 license holder, I frequently create Teams Meetings with phone dial-in for others in my organization. I will only invite the person requesting the meeting and ask that s/he copy the "Join" link and phone info into her own Outlook invitation. I stress NOT TO MAKE A NEW TEAMS MEETING. This allows the requester to be the point person for inquiries and to make small changes to the date/time/body of text without having to come back to me for changes. This has worked out fairly well. 

     

    The person in this particular case has been working remotely and using Outlook in her browser. The tip-off came when she sent me a screen shot of her invitation - she had typed something into the "Location" field that didn't match any of our conference rooms. Next to this it said "Join Teams Meeting". Keep in mind the ONLY place to join the meeting should have been in the body of the invite, not the header. Turns out that the browser version of Outlook has a different way of turning a regular Outlook Calendar invitation into a Teams Meeting than the desktop version. When she followed my instructions, she saw an option to, as she thought, alert her invitees that the meeting was a Teams meeting. In reality, she created a separate Teams meeting. When the time came, some people scrolled to the bottom of the invite and used the link for the meeting I created. Others saw a "join" button at the top of their invite, clicked it, and went to a separate meeting. Case solved!

Resources