microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
UpdateRecordingStatus fails with message API call not allowed for non-Compliance Recording call
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Hi guys, I created a compliance recording policy by following the steps on the Policy Recording Bot documentation using the bot application Id and applied that policy to a specific user.
To call the bot on demand and not every time the user joins into a call or a meeting, the Teams compliance recording application was created with the properties RequiredBeforeMeetingJoin, RequiredBeforeCallEstablishment, RequiredDuringMeeting and RequiredDuringCall set to false.
Teams Compliance Recording Application created.

Teams Compliance Recording Policy created.

User with the policy assigned.

I was able to join the user (with the policy applied) into a meeting and join the bot using the meeting URL. However, when the bot tries to change the meeting recording state by calling the method UpdateRecordingStatus it throws an error which indicates that the call is not a compliance recording call.
API call not allowed for non-Compliance Recording call.

I do not why the call is not considered as a Compliance Recording call despite the user who has the policy applied was already in the meeting. Is there something in the configuration I am missing?
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 Policy Recording Bot documentation and the Teams compliance recording application configuration described in the report. Trace the UpdateRecordingStatus call and compare its meeting setup with the stated policy settings; done means identifying whether a configuration or API prerequisite is missing and documenting the confirmed behavior.
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
- Needs clarification
- Newbie friendliness
- 25/100