Forum Discussion
teams live event participants hitting core meeting lobby
Hi David Phillips ,
When scheduling the meeting, did you enable the "allow external presenters" option? If this is enabled, and the wrong link is used (meaning, you send out the internal event link, and not specifically the one for attendees) you can see this behavior.
MicrosoftHi David Phillips,
Not sure what would be fixed per se... it's by design. The main invites already have a "do not forward" in the body as you noted (but yes, it's not enforced). Ideally though, the only time you would need that toggle is if you are allowing *anonymous* external presenters. If your external presenters already have Teams work accounts, this toggle isn't necessary.
We have experienced this issue as well. One very helpful way to address some of the confusion over the presenter link vs the attendee link for Teams Live Events would be to programmatically change the label on the presenter link from the current "Join Live Event", which sounds like it is for everybody, to the more accurate/specific "Presenter Link".
I have also seen that MS Forms has added an integrated URL shortener. Would be excellent if TLE scheduler could include that for attendee links and/or perhaps automatically alter the displayed text of the attendee link to show up as "Watch the (Live Event Title)"
We used to edit the body of live event notices (sent to organizers and presenters) to include attendee invite instructions and a shortened/formatted attendee link for admins/organizers to easily copy and paste into a separate attendee invite. Unfortunately a change made to the platform in November caused any event that included an additional link in the body to become corrupted upon editing the event in any way (add/remove presenters, add Q&A, etc.). That corruption showed up as the meeting reverting to what looks like a standard Teams meeting. The live event information is still in the body, but you loos all access to edit the live event or access event resources. We have had an open premier ticket on this matter going on 2 months [Case #:28371802].