Permalink for Teams meeting ID & phone

%3CLINGO-SUB%20id%3D%22lingo-sub-2628908%22%20slang%3D%22en-US%22%3EPermalink%20for%20Teams%20meeting%20ID%20%26amp%3B%20phone%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2628908%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20read%20the%20message%20boards%20on%20Teams%20meeting%20I%20permalinks%20and%20am%20aware%20of%20the%20security%20risk%20concerns%3B%20none%20that%20I%20found%20assisted%20with%20out%20issue.%20That%20said%2C%20looking%20for%20any%20advice%3A%3C%2FP%3E%3CP%3EWe%20have%20a%20recurring%20meeting%20(1st%20and%203rd%20Thursdays)%20of%20each%20month%20with%20200%2B%20invitees%20that%20cannot%20follow%20a%20native%20recurrence%20schedule%20via%20Teams%20or%20Outlook%20(this%20divergent%20style%20has%20yet%20to%20be%20a%20feature%2C%20as%20far%20as%20I%20have%20found%2C%20in%20O365).%20The%20majority%20(~97%25)%20of%20the%20attendees%20join%20by%20phone%20(our%20preference%2C%20we%20deleted%20the%20Teams%20link%20from%20the%20invite)%20and%20save%20the%20dial-in%20number%20in%20their%20phones%20for%20convenience%2C%20to%20include%20the%20unique%20meeting%20ID.%20Currently%20we%20believe%20our%20choices%20are%20to%20create%20blocks%20(e.g.%2C%20Aug-Sept%20then%20Oct-Dec)%20where%20we%20can%20follow%20the%20native%20two-week%20recurrence%20pattern%20or%20create%20a%20recurrence%20pattern%20for%20the%201st%20Thursday%20and%20a%20separate%20for%20the%203rd%20Thursday%2C%20both%20with%20unique%20meeting%20IDs.%20As%20you%20can%20imagine%2C%20both%20can%20cause%20some%20confusion%20with%20meeting%20participants%20if%20they%20dial%20into%20the%20wrong%20number%20(which%20has%20happened%20many%20times%20over%20the%20last%2017%2B%20months)%20which%20we%20are%20trying%20to%20avoid%2Fstreamline.%20Anyone%20have%20any%20better%20alternatives%20or%20information%20we%20are%20unaware%20of%3F%20TIA%20~Kristi%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2628908%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUser%20Interface%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

I have read the message boards on Teams meeting I permalinks and am aware of the security risk concerns; none that I found assisted with out issue. That said, looking for any advice:

We have a recurring meeting (1st and 3rd Thursdays) of each month with 200+ invitees that cannot follow a native recurrence schedule via Teams or Outlook (this divergent style has yet to be a feature, as far as I have found, in O365). The majority (~97%) of the attendees join by phone (our preference, we deleted the Teams link from the invite) and save the dial-in number in their phones for convenience, to include the unique meeting ID. Currently we believe our choices are to create blocks (e.g., Aug-Sept then Oct-Dec) where we can follow the native two-week recurrence pattern or create a recurrence pattern for the 1st Thursday and a separate for the 3rd Thursday, both with unique meeting IDs. As you can imagine, both can cause some confusion with meeting participants if they dial into the wrong number (which has happened many times over the last 17+ months) which we are trying to avoid/streamline. Anyone have any better alternatives or information we are unaware of? TIA ~Kristi

0 Replies