1:1 Call Recording Policy Controls Are (Almost!) Here

Published Mar 26 2021 11:06 AM 5,014 Views
Microsoft

**Important timeline update**

The Message Center Post announcing the policy change was updated April 29th to reflect new time lines, now releasing starting May 31st, 2021

 

Hi Teams Community,

A long outstanding request from Teams Administrators is the ability to control 1:1 Call recording independently of Teams Meeting Recording.  We're pleased to announce these controls are almost here.  

 

Today, any user allowed to record Teams meetings can also record 1:1 Calls.  This setting is currently governed by Teams Meeting Policy parameter AllowCloudRecording.  Very soon, 1:1 Call Recording will be governed by a new parameter in Teams Calling Policies, AllowCloudRecordingForCalls.  


For more information, be sure you're logged into your M365 Admin Portal as a Tenant Admin account and review the following Message Center Post:  (Updated) 1:1 Call recording policy introduction

 
In fact, the AllowCloudRecordingForCalls parameter is there now, and you should take immediate action to ensure your users have the desired experience once we begin enforcing this policy, current Plan of Record is to start the rollout May 31st, 2021.
 
What this means for you as a Teams Administrator depends on what your business requirements are.  If you are fine with your users recording 1:1 Calls, you will need to take action to ensure they can continue to do so after the new Policy goes into effect.  Because of the policy requirements of a significant majority of Teams customers, 1:1 Call Recording will be disabled by default.  Further, the new policy is only manageable through PowerShell.  

So, if you would like your users to continue to have the ability to record 1:1 Calls after May 31st, 2021 - you should take action now.  What action?  Set -AllowCloudRecordingForCalls to $True in the Calling Policy applied to the desired Users.  For many of you this will be the Global Default policy and for that, the change can be achieved with the following PowerShell cmdlet:
 
Set-CsTeamsCallingPolicy -Identity Global -AllowCloudRecordingForCalls $True
 
If however you want some users to be prevented from recording 1:1 Calls, you would modify the appropriate policy by setting -AllowCloudRecordingForCalls to $False.  Keep in mind, $False will be the default value for the Global and any out-of-the-box a.k.a. "OOB" Calling Policies when this change rolls out. 
 
OOB Calling Policies cannot be modified - so if you have users with OOB Calling Policies set you will need to move those users to a new policy if you want them to be able to record 1:1 Calls.  Based on customer feedback we expect this case to be somewhat rare - but just in case we've provided you an example PowerShell script that copies your existing Calling Policies and creates new policies with -AllowCloudRecordingForCalls set to $True.  We hope this eases the administrative burden of preparing for this change and also gives you a cool example of how to make a copy of a Teams Policy (yes, with appropriate modifications this script can make a copy of other Teams policies, not just Calling!).

You can find the script here: TeamsCallingPolicyUpdateIt was written by our good friend @andthom, thanks Andy!  
 
Side note - there are other very useful Sample Scripts there - take a moment and bookmark this shortcut: 
 
Be sure to read the ReadMe file there for important instructions (requires MicrosoftTeams ps module, 2.0.0 or higher, for example).  

From my test tenant, running the script example:
CallRecordingScriptRun.png
 
And, this is what it looks like in the Teams Admin Center after I've copied my Calling Policies with the script:
CallingPoliciesAfterScriptGUI.png
In my case, I had a 'CustomCalls' custom Calling Policy created as the only non-default (OOB) policy in my Tenant.  You may have others, and you can copy only select policies if you wish, the script will prompt you.
 
At this point I would use my preferred method of applying the new policies that allow 1:1 Call recording to my desired user set.  Remember, you do have to Grant these policies to users for the setting to take effect.  
 
TLDR: 1:1 Call Recording Policy controls are coming starting May 31st, 2021.  Default will be disabled.  If you want your users to be able to continue recording 1:1 Calls in Teams - you need to make policy changes now to ensure they can continue to do so.  If you are OK with the default (disabled) - no action is required!
 
Final notes:
First, you may be wondering what constitutes a 1:1 Call vs a Meeting?  If you schedule a Meeting with 1 other person only, is that a 1:1 Call?  Nope.  That's a Meeting, and will be governed by Meeting Policies.  So will a Meet Now.  If you call someone, then add video, or screensharing, and then decide to Record - that's a 1:1 Call and will be governed by Calling Policies.
 
Second, this new Calling Policy Parameter does not apply to PSTN calls, yet.  That's coming later.  For the moment you cannot record PSTN calls or calls with Skype for Business users in Teams.
 
And last but not least, this new policy setting relates to the Microsoft Teams Recording solution for 1:1 calls. This setting does not affect 1:1 Compliance Recording, which is still controlled via the Compliance Recording policy.
 
As always we hope this information is useful for you, please comment the blog with any questions or feedback.
Thanks!
Microsoft Teams Support
 

6 Comments
New Contributor

What about PSTN call recording feature? This has been part of the backlog for several months now I guess? 

Microsoft

hi @Amitksingh you can track progress of PSTN Recording here on the Roadmap: Microsoft 365 Roadmap | Microsoft 365

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

Microsoft

Hi @op5555790 best bet is to open a Support case and we can help you out with that issue.  

New Contributor

https://admin.microsoft.com/Adminportal/Home?source=applauncher&ref=MessageCenter/:/messages/MC23879...

 

Hi @Corbin Meek, it is found that the Message center post (MC238796) has been missing/removed. Is this due to any further change/update in this 1:1 call recording functionality.

Microsoft

Hi @Gokulnath_Vee MC posts are removed after some time, looks like 1:1 Call Recording Policy post has met this fate, for more information about that generally look here: Message center - Microsoft 365 admin | Microsoft Docs

Why can’t I see a message that was previously there? To manage the number of messages within Message center, each message will expire and be removed after a period of time. Generally, messages expire 30 days post the time period outlined in the message body.

 

If there are any changes to 1:1 Call Recording Policy in the future, you can expect Message Center to reflect those changes with a new or updated post.  As of now, no changes to the feature.  

%3CLINGO-SUB%20id%3D%22lingo-sub-2276661%22%20slang%3D%22en-US%22%3ERe%3A%201%3A1%20Call%20Recording%20Policy%20Controls%20Are%20(Almost!)%20Here%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276661%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20about%20PSTN%20call%20recording%20feature%3F%20This%20has%20been%20part%20of%20the%20backlog%20for%20several%20months%20now%20I%20guess%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2385715%22%20slang%3D%22en-US%22%3ERe%3A%201%3A1%20Call%20Recording%20Policy%20Controls%20Are%20(Almost!)%20Here%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2385715%22%20slang%3D%22en-US%22%3E%3CP%3Ehi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1028860%22%20target%3D%22_blank%22%3E%40Amitksingh%3C%2FA%3E%26nbsp%3Byou%20can%20track%20progress%20of%20PSTN%20Recording%20here%20on%20the%20Roadmap%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D68777%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20365%20Roadmap%20%7C%20Microsoft%20365%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2217668%22%20slang%3D%22en-US%22%3E1%3A1%20Call%20Recording%20Policy%20Controls%20Are%20(Almost!)%20Here%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2217668%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20color%3D%22%23008000%22%3E%3CEM%3E%3CSTRONG%3E**Important%20timeline%20update**%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23008000%22%3E%3CSTRONG%3EThe%20Message%20Center%20Post%20announcing%20the%20policy%20change%20was%20updated%20April%2029th%20to%20reflect%20new%20time%20lines%2C%20now%20releasing%20starting%20May%2031st%2C%202021%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHi%20Teams%20Community%2C%3C%2FP%3E%0A%3CP%3EA%20long%20outstanding%20request%20from%20Teams%20Administrators%20is%20the%20ability%20to%20control%201%3A1%20Call%20recording%20independently%20of%20Teams%20Meeting%20Recording.%26nbsp%3B%20We're%20pleased%20to%20announce%20these%20controls%20are%20almost%20here.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EToday%2C%20any%20user%20allowed%20to%20record%20Teams%20meetings%20can%20also%20record%201%3A1%20Calls.%26nbsp%3B%20This%20setting%20is%20currently%20governed%20by%20Teams%20Meeting%20Policy%20parameter%20%3CSTRONG%3EAllowCloudRecording%3C%2FSTRONG%3E.%26nbsp%3B%20Very%20soon%2C%201%3A1%20Call%20Recording%20will%20be%20governed%20by%20a%20new%20parameter%20in%20Teams%26nbsp%3B%3CEM%3E%3CSTRONG%3ECalling%3C%2FSTRONG%3E%3C%2FEM%3E%20Policies%2C%20%3CSTRONG%3EAllowCloudRecordingForCalls%3C%2FSTRONG%3E.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EFor%20more%20information%2C%20be%20sure%20you're%20logged%20into%20your%20M365%20Admin%20Portal%20as%20a%20Tenant%20Admin%20account%20and%20review%20the%20following%20Message%20Center%20Post%3A%26nbsp%3B%26nbsp%3B%3CA%20title%3D%22MC238796%22%20href%3D%22https%3A%2F%2Fadmin.microsoft.com%2FAdminportal%2FHome%3Fsource%3Dapplauncher%26amp%3Bref%3DMessageCenter%2F%3A%2Fmessages%2FMC238796%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3E(Updated)%201%3A1%20Call%20recording%20policy%20introduction%3C%2FA%3E%3C%2FP%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EIn%20fact%2C%20the%26nbsp%3B%3CSTRONG%3EAllowCloudRecordingForCalls%3C%2FSTRONG%3E%20parameter%20is%20there%20now%2C%20and%20%3CEM%3E%3CSTRONG%3Eyou%20should%20take%20immediate%20action%3C%2FSTRONG%3E%3C%2FEM%3E%20to%20ensure%20your%20users%20have%20the%20desired%20experience%20once%20we%20begin%20enforcing%20this%20policy%2C%20current%20Plan%20of%20Record%20is%20to%20start%20the%20rollout%20%3CFONT%20color%3D%22%23008000%22%3E%3CSTRONG%3EMay%2031st%2C%202021%3C%2FSTRONG%3E%3C%2FFONT%3E%3CSTRONG%3E.%3C%2FSTRONG%3E%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EWhat%20this%20means%20for%20you%20as%20a%20Teams%20Administrator%20depends%20on%20what%20your%20business%20requirements%20are.%26nbsp%3B%20If%20you%20are%20fine%20with%20your%20users%20recording%201%3A1%20Calls%2C%20you%26nbsp%3B%3CSTRONG%3Ewill%20need%20to%20take%20action%3C%2FSTRONG%3E%20to%20ensure%20they%20can%20continue%20to%20do%20so%20after%20the%20new%20Policy%20goes%20into%20effect.%26nbsp%3B%20Because%20of%20the%20policy%20requirements%20of%20a%20significant%20majority%20of%20Teams%20customers%2C%201%3A1%20Call%20Recording%20will%20be%26nbsp%3B%3CSTRONG%3Edisabled%20by%20default.%3C%2FSTRONG%3E%26nbsp%3B%20Further%2C%20the%20new%20policy%20is%20only%20manageable%20through%20PowerShell.%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CBR%20%2F%3ESo%2C%20if%20you%20would%20like%20your%20users%20to%20continue%20to%20have%20the%20ability%20to%20record%201%3A1%20Calls%20after%20%3CFONT%20color%3D%22%23008000%22%3E%3CSTRONG%3EMay%2031st%2C%202021%3C%2FSTRONG%3E%3C%2FFONT%3E%20-%20you%20should%20take%20action%20now.%26nbsp%3B%20What%20action%3F%26nbsp%3B%20Set%20%3CSTRONG%3E-AllowCloudRecordingForCalls%3C%2FSTRONG%3E%20to%20%24True%20in%20the%20Calling%20Policy%20applied%20to%20the%20desired%20Users.%26nbsp%3B%20For%20many%20of%20you%20this%20will%20be%20the%20Global%20Default%20policy%20and%20for%20that%2C%20the%20change%20can%20be%20achieved%20with%20the%20following%20PowerShell%20cmdlet%3A%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3ESet-CsTeamsCallingPolicy%20-Identity%20Global%20-AllowCloudRecordingForCalls%20%24True%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EIf%20however%20you%20want%20some%20users%20to%20be%20prevented%20from%20recording%201%3A1%20Calls%2C%20you%20would%20modify%20the%20appropriate%20policy%20by%20setting%20-AllowCloudRecordingForCalls%20to%20%24False.%26nbsp%3B%20Keep%20in%20mind%2C%20%24False%20will%20be%20the%20default%20value%20for%20the%20Global%20and%20any%20out-of-the-box%20a.k.a.%20%22OOB%22%20Calling%20Policies%20when%20this%20change%20rolls%20out.%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EOOB%20Calling%20Policies%20%3CU%3Ecannot%3C%2FU%3E%20be%20modified%20-%20so%20if%20you%20have%20users%20with%20OOB%20Calling%20Policies%20set%20you%20will%20need%20to%20%3CSTRONG%3Emove%20those%20users%20to%20a%20new%20policy%3C%2FSTRONG%3E%20if%20you%20want%20them%20to%20be%20able%20to%20record%201%3A1%20Calls.%26nbsp%3B%20Based%20on%20customer%20feedback%20we%20expect%20this%20case%20to%20be%20somewhat%20rare%20-%20but%20just%20in%20case%20we've%20provided%20you%20an%20example%20PowerShell%20script%20that%20copies%20your%20existing%20Calling%20Policies%20and%20creates%20new%20policies%20with%20-AllowCloudRecordingForCalls%20set%20to%20%24True.%26nbsp%3B%20We%20hope%20this%20eases%20the%20administrative%20burden%20of%20preparing%20for%20this%20change%20and%20also%20gives%20you%20a%20cool%20example%20of%20how%20to%20make%20a%20copy%20of%20a%20Teams%20Policy%20(yes%2C%20with%20appropriate%20modifications%20this%20script%20can%20make%20a%20copy%20of%20other%20Teams%20policies%2C%20not%20just%20Calling!).%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CBR%20%2F%3EYou%20can%20find%20the%20script%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FTeamsAdminSamples%2FPowerShell%2Ftree%2Fmain%2FTeamsCallingPolicyUpdate%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ETeamsCallingPolicyUpdate%3C%2FA%3E.%26nbsp%3B%20%3CSPAN%3EIt%20was%20written%20by%20our%20good%20friend%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F918517%22%20target%3D%22_blank%22%3E%40andthom%3C%2FA%3E%2C%26nbsp%3Bthanks%20Andy!%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CSPAN%3E%3CSPAN%3ESide%20note%20-%20there%20are%20other%20very%20useful%20Sample%20Scripts%20there%20-%20take%20a%20moment%20and%20bookmark%20this%20shortcut%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fteamspowershellsamples%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3E%3CSPAN%3Eaka.ms%2Fteamspowershellsamples%3C%2FSPAN%3E%3C%2FA%3E%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EBe%20sure%20to%20read%20the%20ReadMe%20file%20there%20for%20important%20instructions%20(requires%20MicrosoftTeams%20ps%20module%2C%202.0.0%20or%20higher%2C%20for%20example).%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CBR%20%2F%3EFrom%20my%20test%20tenant%2C%20running%20the%20script%20example%3A%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22CallRecordingScriptRun.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F267511i2FBF7945C51CDCB2%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22CallRecordingScriptRun.png%22%20alt%3D%22CallRecordingScriptRun.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CSPAN%3EAnd%2C%20this%20is%20what%20it%20looks%20like%20in%20the%20Teams%20Admin%20Center%20after%20I've%20copied%20my%20Calling%20Policies%20with%20the%20script%3A%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22CallingPoliciesAfterScriptGUI.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F267512iF4153A6E7BEFED85%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22CallingPoliciesAfterScriptGUI.png%22%20alt%3D%22CallingPoliciesAfterScriptGUI.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EIn%20my%20case%2C%20I%20had%20a%20'CustomCalls'%20custom%20Calling%20Policy%20created%20as%20the%20only%20non-default%20(OOB)%20policy%20in%20my%20Tenant.%26nbsp%3B%20You%20may%20have%20others%2C%20and%20you%20can%20copy%20only%20select%20policies%20if%20you%20wish%2C%20the%20script%20will%20prompt%20you.%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EAt%20this%20point%20I%20would%20use%20my%20preferred%20method%20of%20applying%20the%20new%20policies%20that%20allow%201%3A1%20Call%20recording%20to%20my%20desired%20user%20set.%26nbsp%3B%20Remember%2C%20you%20do%20have%20to%20Grant%20these%20policies%20to%20users%20for%20the%20setting%20to%20take%20effect.%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%3CSTRONG%3ETLDR%3A%26nbsp%3B%3C%2FSTRONG%3E1%3A1%20Call%20Recording%20Policy%20controls%20are%20coming%20starting%20%3CFONT%20color%3D%22%23008000%22%3E%3CSTRONG%3EMay%2031st%2C%202021%3C%2FSTRONG%3E%3C%2FFONT%3E.%26nbsp%3B%20Default%20will%20be%20%3CSTRONG%3E%3CU%3Edisabled%3C%2FU%3E%3C%2FSTRONG%3E.%26nbsp%3B%20If%20you%20want%20your%20users%20to%20be%20able%20to%20continue%20recording%201%3A1%20Calls%20in%20Teams%20-%20you%20need%20to%20make%20policy%20changes%26nbsp%3B%3CSTRONG%3Enow%3C%2FSTRONG%3E%20to%20ensure%20they%20can%20continue%20to%20do%20so.%26nbsp%3B%20If%20you%20are%20OK%20with%20the%20default%20(disabled)%20-%20no%20action%20is%20required!%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EFinal%20notes%3A%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EFirst%2C%20you%20may%20be%20wondering%20what%20constitutes%20a%201%3A1%20Call%20vs%20a%20Meeting%3F%26nbsp%3B%20If%20you%20schedule%20a%20Meeting%20with%201%20other%20person%20only%2C%20is%20that%20a%201%3A1%20Call%3F%26nbsp%3B%20Nope.%26nbsp%3B%20That's%20a%20Meeting%2C%20and%20will%20be%20governed%20by%20Meeting%20Policies.%26nbsp%3B%20So%20will%20a%20Meet%20Now.%26nbsp%3B%20If%20you%20call%20someone%2C%20then%20add%20video%2C%20or%20screensharing%2C%20and%20then%20decide%20to%20Record%20-%20that's%20a%201%3A1%20Call%20and%20will%20be%20governed%20by%20Calling%20Policies.%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3ESecond%2C%20this%20new%20Calling%20Policy%20Parameter%20does%26nbsp%3B%3CSTRONG%3Enot%3C%2FSTRONG%3E%20apply%20to%20PSTN%20calls%2C%20yet.%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D68777%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EThat's%20coming%20later.%3C%2FA%3E%26nbsp%3B%20For%20the%20moment%20you%20cannot%20record%20PSTN%20calls%20or%20calls%20with%20Skype%20for%20Business%20users%20in%20Teams.%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EAnd%20last%20but%20not%20least%2C%20this%20new%20policy%20setting%20relates%20to%20the%20Microsoft%20Teams%20Recording%20solution%20for%201%3A1%20calls.%20This%20setting%20%3CSTRONG%3Edoes%20not%20affect%3C%2FSTRONG%3E%201%3A1%20Compliance%20Recording%2C%20which%20is%20still%20controlled%20via%20the%20Compliance%20Recording%20policy.%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EAs%20always%20we%20hope%20this%20information%20is%20useful%20for%20you%2C%20please%20comment%20the%20blog%20with%20any%20questions%20or%20feedback.%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3EThanks!%3CBR%20%2F%3EMicrosoft%20Teams%20Support%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3CDIV%20class%3D%22ms-TooltipHost%20root-249%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3E%3CLI-WRAPPER%3E%3C%2FLI-WRAPPER%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2217668%22%20slang%3D%22en-US%22%3E%3CP%3EAllowCloudRecordingForCalls%20in%20Teams%20Calling%20Policies%20Give%20Admins%20More%20Control%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2558957%22%20slang%3D%22en-US%22%3ERe%3A%201%3A1%20Call%20Recording%20Policy%20Controls%20Are%20(Almost!)%20Here%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2558957%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%3CLINGO-SUB%20id%3D%22lingo-sub-2562897%22%20slang%3D%22en-US%22%3ERe%3A%201%3A1%20Call%20Recording%20Policy%20Controls%20Are%20(Almost!)%20Here%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2562897%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1106069%22%20target%3D%22_blank%22%3E%40op5555790%3C%2FA%3E%26nbsp%3Bbest%20bet%20is%20to%20open%20a%20Support%20case%20and%20we%20can%20help%20you%20out%20with%20that%20issue.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2597746%22%20slang%3D%22en-US%22%3ERe%3A%201%3A1%20Call%20Recording%20Policy%20Controls%20Are%20(Almost!)%20Here%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2597746%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fadmin.microsoft.com%2FAdminportal%2FHome%3Fsource%3Dapplauncher%26amp%3Bref%3DMessageCenter%2F%3A%2Fmessages%2FMC238796%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fadmin.microsoft.com%2FAdminportal%2FHome%3Fsource%3Dapplauncher%26amp%3Bref%3DMessageCenter%2F%3A%2Fmessages%2FMC238796%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%26nbsp%3B%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F15788%22%20target%3D%22_blank%22%3E%40Corbin%20Meek%3C%2FA%3E%2C%20it%20is%20found%20that%20the%20Message%20center%20post%20(MC238796)%20has%20been%20missing%2Fremoved.%20Is%20this%20due%20to%20any%20further%20change%2Fupdate%20in%20this%201%3A1%20call%20recording%20functionality.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2606653%22%20slang%3D%22en-US%22%3ERe%3A%201%3A1%20Call%20Recording%20Policy%20Controls%20Are%20(Almost!)%20Here%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2606653%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1113654%22%20target%3D%22_blank%22%3E%40Gokulnath_Vee%3C%2FA%3E%26nbsp%3BMC%20posts%20are%20removed%20after%20some%20time%2C%20looks%20like%201%3A1%20Call%20Recording%20Policy%20post%20has%20met%20this%20fate%2C%20for%20more%20information%20about%20that%20generally%20look%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Fmicrosoft-365%2Fadmin%2Fmanage%2Fmessage-center%3FWT.mc_id%3D365AdminCSH_inproduct%26amp%3Bview%3Do365-worldwide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMessage%20center%20-%20Microsoft%20365%20admin%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CTABLE%20class%3D%22table%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%3EWhy%20can%E2%80%99t%20I%20see%20a%20message%20that%20was%20previously%20there%3F%3C%2FTD%3E%0A%3CTD%3ETo%20manage%20the%20number%20of%20messages%20within%20Message%20center%2C%20each%20message%20will%20expire%20and%20be%20removed%20after%20a%20period%20of%20time.%20Generally%2C%20messages%20expire%2030%20days%20post%20the%20time%20period%20outlined%20in%20the%20message%20body.%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20there%20are%20any%20changes%20to%201%3A1%20Call%20Recording%20Policy%20in%20the%20future%2C%20you%20can%20expect%20Message%20Center%20to%20reflect%20those%20changes%20with%20a%20new%20or%20updated%20post.%26nbsp%3B%20As%20of%20now%2C%20no%20changes%20to%20the%20feature.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎May 27 2021 02:16 PM
Updated by: