Minimal permissions for 'spo tenant related' 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 tenant appcatalog addm365 spo tenant appcatalogurl getm365 spo tenant recyclebinitem listm365 spo tenant recyclebinitem removem365 spo tenant recyclebinitem restorem365 spo tenant settings listm365 spo tenant settings setm365 spo tenant site get
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 Writing the docs page and the guide on documenting minimal permissions, then review the documentation entries for the eight listed spo tenant commands. Add a Permissions section before Examples for each command, documenting only the minimal delegated and application permissions and ordering multiple resources alphabetically. Done means all listed command pages follow the documented format, including auth-specific examples where needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100