Minimal permissions for 'spo 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 spo report activityfilecountsm365 spo report activitypagesm365 spo report activityusercountsm365 spo report activityuserdetailm365 spo report siteusagedetailm365 spo report siteusagefilecountsm365 spo report siteusagepagesm365 spo report siteusagesitecountsm365 spo report siteusagestorage
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 eight SharePoint report command documentation pages and read the Writing the docs and minimal permissions guides linked in the issue. Check how each command authenticates and identify the minimal delegated and application permissions, ordering multiple resources alphabetically. Done means every listed page has a Permissions section immediately before Examples, including auth-type-specific cases where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cli
- Domain
- authentication, cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100