Repeat Conference IDs Generated when set to Dynamic

%3CLINGO-SUB%20id%3D%22lingo-sub-1788844%22%20slang%3D%22en-US%22%3ERepeat%20Conference%20IDs%20Generated%20when%20set%20to%20Dynamic%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1788844%22%20slang%3D%22en-US%22%3E%3CP%3EA%20few%20of%20our%20users%20have%20reported%20that%20occasionally%20the%20Conference%20ID%20that%20is%20generated%20for%20a%20new%20meeting%20is%20the%20same%20as%20an%20old%20meeting%20and%20therefore%20old%20comments%2C%20attendees%20etc.%20are%20linked%20to%20the%20new%20meeting%20which%20is%20a%20confidentiality%20concern.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20have%20Conference%20ID%20set%20to%20Dynamic%20for%20all%20users%20with%20an%20Audio%20Conferencing%20license.%20Any%20idea%20why%20this%20is%20happening%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1788844%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMeetings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1788952%22%20slang%3D%22en-US%22%3ERe%3A%20Repeat%20Conference%20IDs%20Generated%20when%20set%20to%20Dynamic%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1788952%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F606551%22%20target%3D%22_blank%22%3E%40acornies%3C%2FA%3E%26nbsp%3B%20Check%20if%20you%20have%20roaming%20profile%20enabled%20for%20users%20and%20exclude%20the%20Microsoft%20teams%20folder%20from%20roaming.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

A few of our users have reported that occasionally the Conference ID that is generated for a new meeting is the same as an old meeting and therefore old comments, attendees etc. are linked to the new meeting which is a confidentiality concern.

We have Conference ID set to Dynamic for all users with an Audio Conferencing license. Any idea why this is happening?

1 Reply
Highlighted

Hm, that's the second time a similar issue is mentioned today, so I strongly suggest you open a support case and report this for Microsoft to properly investigate.