User action logging for in meeting functions such as Spotlight

%3CLINGO-SUB%20id%3D%22lingo-sub-3475724%22%20slang%3D%22en-US%22%3EUser%20action%20logging%20for%20in%20meeting%20functions%20such%20as%20Spotlight%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3475724%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECovering%20part%20of%20an%20old%20Uservoice%20item%3B%20we%20have%20a%20curious%20issue%20of%20aberrant%20spotlighting%20occurring%20during%20a%20meeting.%20It%20is%20suspected%20that%20a%20user%20is%20%22playing%20with%20the%20controls%22%20during%20the%20meeting.%20However%20we%20are%20seeking%20verification%20that%20this%20is%20not%20an%20issue%20and%20one%20simply%20of%20human%20factors%20and%20training.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20the%20Debug%20logs%2Fsupport%20files%20that%20can%20be%20generated%20in%20a%20call%20and%20are%20not%20encoded%20we%20can%20see%20the%20SpotlightMixin%20entries%20identifying%20the%20users%20transitioning%20into%20spotlight%20and%2For%20being%20removed%20from%20spotlight.%20What%20appears%20to%20be%20omitted%20in%20the%20clear-text%20log%20is%20that%20of%20the%20userID%20initiating%20the%20request.%3C%2FP%3E%3CP%3EIs%20there%20a%20simple%20way%20of%20identifying%20the%20requestor%20userID%20this%20within%20the%20toolset%20and%20capabilities%20available%3F%20Indeed%20are%20these%20details%20captured%20and%20audited%3F%3CBR%20%2F%3E%3CBR%20%2F%3ENaturally%20appreciate%20that%20there%20are%20other%20elements%20to%20aid%20the%20unwanted%20activity%20such%20as%20restricting%20presenters%20list%20etc.%20but%20interested%20to%20see%20if%20there%20is%20a%20simple%20way%20of%20identifying%20the%20requesting%20user.%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20thoughts%20and%20guidance%20on%20this%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ESJ%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3475724%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eauditing%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Edebug%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDIagnostics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Elogging%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMeetings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Frequent Visitor

Hi all,

 

Covering part of an old Uservoice item; we have a curious issue of aberrant spotlighting occurring during a meeting. It is suspected that a user is "playing with the controls" during the meeting. However we are seeking verification that this is not an issue and one simply of human factors and training.

 

From the Debug logs/support files that can be generated in a call and are not encoded we can see the SpotlightMixin entries identifying the users transitioning into spotlight and/or being removed from spotlight. What appears to be omitted in the clear-text log is that of the userID initiating the request.

Is there a simple way of identifying the requestor userID this within the toolset and capabilities available? Indeed are these details captured and audited?

Naturally appreciate that there are other elements to aid the unwanted activity such as restricting presenters list etc. but interested to see if there is a simple way of identifying the requesting user.

Any thoughts and guidance on this would be greatly appreciated.

Thanks

SJ

 

1 Reply
Sorry, heard about the request of auditing for these type of events before but as far as I know still not possible and not logged. So for now you better go with the roles in the Teams meetings, i.e. make the majority Attendees to avoid meeting disturbance.

Simply adding for reference https://support.microsoft.com/en-us/office/roles-in-a-teams-meeting-c16fa7d0-1666-4dde-8686-0a0bfe16...