Minimal permissions for 'spo user' 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 user ensurem365 spo user getm365 spo user listm365 spo user remove
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 four command documentation pages for m365 spo user ensure, get, list, and remove, using the linked writing and minimal-permissions guides first. Add a Permissions section immediately before Examples on each page, documenting minimal delegated and application permissions, with multiple resources alphabetized; done when all four pages follow the linked examples and guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cli
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100