Creating a new ComplianceRecordingApplication in Set-CsTeamsComplianceRecordingPolicy no longer works in MicrosoftTeams powershell module 6.1.0 and higher #746
Starting with the MicrosoftTeams powershell module version 6.1.0 the example Set-CsTeamsComplianceRecordingPolicy from the PolicyRecordingBot sample no longer functions. The command:
executes in powershell without an error displayed but if you call Get-CsTeamsComplianceRecordingApplication after running the command, a new application is not created. Similarly if you call Get-CsTeamsComplianceRecordingPolicy after running the command, no ComplianceRecordingApplications are listed for the target policy.
This behavior seems to have started in version 6.1.0 of the module and continues to fail in 6.4.0 of the module. The command works in older versions of the MicrosoftTeams powershell module. I specifically tested from version 5.5.0 to 6.0.0 while trying to find what version it started failing in.
Starting with the MicrosoftTeams powershell module version 6.1.0 the example Set-CsTeamsComplianceRecordingPolicy from the PolicyRecordingBot sample no longer functions. The command:
Set-CsTeamsComplianceRecordingPolicy -Identity -ComplianceRecordingApplications ` @(New-CsTeamsComplianceRecordingApplication -Parent -Id )
executes in powershell without an error displayed but if you call Get-CsTeamsComplianceRecordingApplication after running the command, a new application is not created. Similarly if you call Get-CsTeamsComplianceRecordingPolicy after running the command, no ComplianceRecordingApplications are listed for the target policy.
This behavior seems to have started in version 6.1.0 of the module and continues to fail in 6.4.0 of the module. The command works in older versions of the MicrosoftTeams powershell module. I specifically tested from version 5.5.0 to 6.0.0 while trying to find what version it started failing in.