microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Creating a new ComplianceRecordingApplication in Set-CsTeamsComplianceRecordingPolicy no longer works in MicrosoftTeams powershell module 6.1.0 and higher
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PolicyRecordingBot sample and reproduce the exact Set-CsTeamsComplianceRecordingPolicy command using MicrosoftTeams module versions 6.0.0 and 6.1.0. Check the results with Get-CsTeamsComplianceRecordingApplication and Get-CsTeamsComplianceRecordingPolicy; done means the sample creates and lists the compliance recording application, or the incompatibility and required update are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100