MS Teams Continued Recording After Meeting Ends

%3CLINGO-SUB%20id%3D%22lingo-sub-1665323%22%20slang%3D%22en-US%22%3EMS%20Teams%20Continued%20Recording%20After%20Meeting%20Ends%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1665323%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20experienced%20an%20issue%20with%20MS%20Teams%20continuing%20to%20record%20when%20the%20meeting%20ended.%26nbsp%3B%20The%20person%20who%20originally%20started%20the%20meeting%20does%20not%20have%20the%20STOP%20RECORDING%20option%20in%20their%20%22...%22%20menu%20nor%20do%20they%20have%20the%20%22End%20Meeting%22%20menu%20option.%26nbsp%3B%20Here's%20what%20happened...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOrganizer%20joined%20the%20meeting%20and%20started%20the%20recording%20in%20MS%20Teams%20while%20logged%20into%20VPN.%26nbsp%3B%20The%20meeting%20organizer%20was%20also%20logged%20into%20Office%20365.%26nbsp%3B%20The%20organizer%20had%20to%20share%20content%20behind%20the%20company%20firewall%20that%20was%20in%20an%20%22on%20prem%22%20enviroment%20-%20hence%20the%20VPN%20login.%26nbsp%3B%20The%20organizer%20started%20the%20recording%20but%20learned%20after%20the%20meeting%20ended%20that%20the%20recoding%20kept%20going%20even%20after%20all%20users%20exited%20the%20meeting%20(except%20possibly%20the%20Office%20365%20login%20of%20the%20organizer).%26nbsp%3B%20%26nbsp%3BDuring%20this%20meeting%20the%20organizer%20lost%20the%20VPN%20connection%20and%20had%20to%20restart%20it.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIt%20would%20seem%20the%20MS%20Teams%20has%20an%20issue%20recognizing%20when%20a%20VPN%20connection%20has%20dropped%20while%20that%20same%20user%20is%20simultaneously%20logged%20into%20Office%20365%20even%20though%20the%20meeting%20was%20launched%20under%20VPN%20vs.%20via%20the%20browser.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20addition%20to%20this%2C%20because%20the%20organizer%20lacked%20the%20menu%20option%20to%20Stop%20Recording%20or%20End%20Meeting%2C%20the%20meeting%20continued%20to%20record%20for%20over%204%20hours%20because%20it%20assumed%20that%20the%20organizer%20was%20still%20logged%20into%20the%20meeting%20even%20though%20it%20was%20never%20launched%20from%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHopefully%20this%20information%20helps%20Microsoft%20solve%20the%20issue%20because%20it%20is%20really%20annoying.%26nbsp%3B%20Also%20Microsoft%20-%20we%20need%20an%20ability%20to%20edit%20the%20Microsoft%20Stream%20that%20is%20created%20when%20a%20Teams%20recording%20is%20made.%26nbsp%3B%20This%20will%20help%20us%20truncate%20those%20streams%20that%20accidentally%20record%20for%20numerous%20unintended%20hours.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1665323%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ERecording%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

We have experienced an issue with MS Teams continuing to record when the meeting ended.  The person who originally started the meeting does not have the STOP RECORDING option in their "..." menu nor do they have the "End Meeting" menu option.  Here's what happened...

 

Organizer joined the meeting and started the recording in MS Teams while logged into VPN.  The meeting organizer was also logged into Office 365.  The organizer had to share content behind the company firewall that was in an "on prem" enviroment - hence the VPN login.  The organizer started the recording but learned after the meeting ended that the recoding kept going even after all users exited the meeting (except possibly the Office 365 login of the organizer).   During this meeting the organizer lost the VPN connection and had to restart it. 


It would seem the MS Teams has an issue recognizing when a VPN connection has dropped while that same user is simultaneously logged into Office 365 even though the meeting was launched under VPN vs. via the browser.

 

In addition to this, because the organizer lacked the menu option to Stop Recording or End Meeting, the meeting continued to record for over 4 hours because it assumed that the organizer was still logged into the meeting even though it was never launched from 365.

 

Hopefully this information helps Microsoft solve the issue because it is really annoying.  Also Microsoft - we need an ability to edit the Microsoft Stream that is created when a Teams recording is made.  This will help us truncate those streams that accidentally record for numerous unintended hours.

 

Regards

 

1 Reply
Highlighted

Hi @mmambros   You might want to open a specific bug report on our Uservoice forum.  Also, you might be interested in voting for this feature proposal: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/33965176-stop-recording