microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
[Policy Based Recording] One bot per the set of users who have the same policy
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
We have a scenario where if say 3 different people, who are all covered by a policy in some way to require compliance recording, and they join the same meeting, bot is called 3 separate times.
We had originally thought we’d be asked to record once (since it is one meeting), but it is more that there are 3 individuals of interest, and so each trigger a request for the bot to join and record, resulting in potentially recordings that contain the same information… is that correct? Or is it that we’re not crafting our policy/policies correctly?
Is there any bot grouping that can be done to optimize it as one BOT per the set of user who have the same policy?
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-based recording scenario described in the issue and determine how recording requests are grouped when several users share a meeting and policy. Done would require a documented answer on whether one bot can serve the user set and whether the reported behavior reflects policy configuration or a product limitation.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100