Minimal permissions for 'teams report' commands
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 413
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 21
Description
We're adding a new Permissions section to all commands. This section will document the minimal delegated and application permissions required to execute the command.
The goal is to:
- Make it easier to run the CLI with custom app registrations and application permissions.
- Ensure we only document the minimal set of permissions needed.
- Keep documentation consistent by placing the Permissions section right before the Examples section.
- If there are multiple resources, order them alphabetically
- If there are commands that only support one type of auth (like delegated or app-only), we have an example for that as well. E.g. m365 planner tenant settings list - Permissions
Resources
Commands in scope
This issue covers the following commands:
m365 teams report deviceusagedistributionusercountsm365 teams report deviceusageusercountsm365 teams report deviceusageuserdetailm365 teams report directroutingcallsm365 teams report pstncallsm365 teams report useractivitycountsm365 teams report useractivityusercountsm365 teams report useractivityuserdetail
Contributor guide
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 linked writing and minimal-permissions documentation, then inspect the documentation entry points for the eight listed teams report commands. Add a Permissions section before Examples for each command, ordering multiple resources alphabetically and documenting only the supported minimal delegated or application permissions. Done means all eight command pages follow the linked examples and guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100