Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)

New Diagnostic: 1:1 Call Recording in Teams

Published May 28 2021 12:14 PM 1,937 Views
Microsoft

Hi Teams Community,

In conjunction with the upcoming release of 1:1 Call Recording Policy, @Sorin Duta has coded up a new Diagnostic for us.  Before you check out the diagnostic we highly recommend reviewing this earlier blog post which explains the upcoming changes, so please go review that first: 1:1 Call Recording Policy Controls Are (Almost!) Here - Microsoft Tech Community

 

After the policy takes effect, some users might experience a greyed out "Start Recording" button in 1:1 Calls.  This new diagnostic is pretty simple and will check the user's Teams Calling Policy for the AllowCloudRecordingForCalls parameter - if that's $false (and it will be by default), the user will not be allowed to record 1:1 Calls.  


Here's what it looks like in the Admin Portal (reminder, in your Admin Portal click on "need help" or under Support - New service request" - type in the shortcut Diag: Teams 1:1 Call Recording 

1-1CallRecDiagFail.png

 

In this case, the user's policy setting AllowCloudRecordingForCalls is set to $false, and they're not allowed to record 1:1 calls.  The Diagnostic returns detailed instructions on how to change that policy setting.  We also cover that in depth on the previous blog post mentioned above.

 

In the case AllowCloudRecordingForCalls is set to $true - we'll display the following: 

1-1CallRecDiagSuccessOD.png

It's possible due to policy change replication time a user might still have the "Start Recording" button greyed out after a policy change to allow it - so be sure to wait a couple hours and try again if you've recently made a change.


While this one is pretty simple, we hope it helps you determine if a user's 1:1 Call Recording policy is what is preventing them from recording calls.  On the other hand, if you want to prevent users from recording 1:1 Calls, this diag can help you confirm you have it set correctly.

 

As always we hope this helps, and welcome your feedback in the comments below.  

Thanks!
Microsoft Teams Support

1 Comment
Microsoft

Hi I performed a TEAMS recording -and I recived this message

Your recording was not saved you ran out of storage in Stream

so I dleted few fils from Stream but I sill can not view my recording

24 hours passed.

Please assit

%3CLINGO-SUB%20id%3D%22lingo-sub-2396766%22%20slang%3D%22en-US%22%3ENew%20Diagnostic%3A%201%3A1%20Call%20Recording%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2396766%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Teams%20Community%2C%3C%2FP%3E%0A%3CP%3EIn%20conjunction%20with%20the%20upcoming%20release%20of%201%3A1%20Call%20Recording%20Policy%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F121435%22%20target%3D%22_blank%22%3E%40Sorin%20Duta%3C%2FA%3E%26nbsp%3Bhas%20coded%20up%20a%20new%20Diagnostic%20for%20us.%26nbsp%3B%20Before%20you%20check%20out%20the%20diagnostic%20we%20highly%20recommend%20reviewing%20this%20earlier%20blog%20post%20which%20explains%20the%20upcoming%20changes%2C%20so%20please%20go%20review%20that%20first%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-teams-support%2F1-1-call-recording-policy-controls-are-almost-here%2Fba-p%2F2217668%22%20target%3D%22_blank%22%3E1%3A1%20Call%20Recording%20Policy%20Controls%20Are%20(Almost!)%20Here%20-%20Microsoft%20Tech%20Community%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20the%20policy%20takes%20effect%2C%20some%20users%20might%20experience%20a%20greyed%20out%20%22Start%20Recording%22%20button%20in%201%3A1%20Calls.%26nbsp%3B%20This%20new%20diagnostic%20is%20pretty%20simple%20and%20will%20check%20the%20user's%20Teams%20Calling%20Policy%20for%20the%20AllowCloudRecordingForCalls%20parameter%20-%20if%20that's%20%24false%20(and%20it%20will%20be%20by%20default)%2C%20the%20user%20will%20not%20be%20allowed%20to%20record%201%3A1%20Calls.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EHere's%20what%20it%20looks%20like%20in%20the%20Admin%20Portal%20(reminder%2C%20in%20your%20Admin%20Portal%20click%20on%20%22need%20help%22%20or%20under%20Support%20-%20New%20service%20request%22%20-%20type%20in%20the%20shortcut%26nbsp%3B%3CSTRONG%3EDiag%3A%20Teams%201%3A1%20Call%20Recording%3C%2FSTRONG%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%221-1CallRecDiagFail.png%22%20style%3D%22width%3A%20455px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F284704i5FE03D4341362D1E%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%221-1CallRecDiagFail.png%22%20alt%3D%221-1CallRecDiagFail.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20this%20case%2C%20the%20user's%20policy%20setting%20AllowCloudRecordingForCalls%20is%20set%20to%20%24false%2C%20and%20they're%20not%20allowed%20to%20record%201%3A1%20calls.%26nbsp%3B%20The%20Diagnostic%20returns%20detailed%20instructions%20on%20how%20to%20change%20that%20policy%20setting.%26nbsp%3B%20We%20also%20cover%20that%20in%20depth%20on%20the%20previous%20blog%20post%20mentioned%20above.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20case%20AllowCloudRecordingForCalls%20is%20set%20to%20%24true%20-%20we'll%20display%20the%20following%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%221-1CallRecDiagSuccessOD.png%22%20style%3D%22width%3A%20451px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F284705iE9937D35648BCD3B%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%221-1CallRecDiagSuccessOD.png%22%20alt%3D%221-1CallRecDiagSuccessOD.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EIt's%20possible%20due%20to%20policy%20change%20replication%20time%20a%20user%20might%20still%20have%20the%20%22Start%20Recording%22%20button%20greyed%20out%20after%20a%20policy%20change%20to%20allow%20it%20-%20so%20be%20sure%20to%20wait%20a%20couple%20hours%20and%20try%20again%20if%20you've%20recently%20made%20a%20change.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EWhile%20this%20one%20is%20pretty%20simple%2C%20we%20hope%20it%20helps%20you%20determine%20if%20a%20user's%201%3A1%20Call%20Recording%20policy%20is%20what%20is%20preventing%20them%20from%20recording%20calls.%26nbsp%3B%20On%20the%20other%20hand%2C%20if%20you%20want%20to%20prevent%20users%20from%20recording%201%3A1%20Calls%2C%20this%20diag%20can%20help%20you%20confirm%20you%20have%20it%20set%20correctly.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20always%20we%20hope%20this%20helps%2C%20and%20welcome%20your%20feedback%20in%20the%20comments%20below.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3CBR%20%2F%3EMicrosoft%20Teams%20Support%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2396766%22%20slang%3D%22en-US%22%3E%3CP%3ENew%20Teams%20Diagnostic%201%3A1%20Call%20Recording%20Policy%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2396766%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDiagnostics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESupport%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esupportability%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2558985%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Diagnostic%3A%201%3A1%20Call%20Recording%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2558985%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20I%20performed%20a%20TEAMS%20recording%20-and%20I%20recived%20this%20message%3C%2FP%3E%0A%3CP%3EYour%20recording%20was%20not%20saved%20you%20ran%20out%20of%20storage%20in%20Stream%3C%2FP%3E%0A%3CP%3Eso%20I%20dleted%20few%20fils%20from%20Stream%20but%20I%20sill%20can%20not%20view%20my%20recording%3C%2FP%3E%0A%3CP%3E24%20hours%20passed.%3C%2FP%3E%0A%3CP%20class%3D%22%22%3EPlease%20assit%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎May 28 2021 12:14 PM
Updated by:
www.000webhost.com