pnp/cli-microsoft365

Minimal permissions for 'spo tenant related' commands

Open

#7,511 opened on Aug 9, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)TypeScript (399 forks)auto 404
docshelp wanted

Repository metrics

Stars
 (1,390 stars)
PR merge metrics
 (PR metrics pending)

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 add
  • m365 spo tenant appcatalogurl get
  • m365 spo tenant recyclebinitem list
  • m365 spo tenant recyclebinitem remove
  • m365 spo tenant recyclebinitem restore
  • m365 spo tenant settings list
  • m365 spo tenant settings set
  • m365 spo tenant site get

Contributor guide

Research direction
Review the linked documentation guidelines and existing planner examples to understand the required format. Then locate the docs for each listed command and add a Permissions section before the Examples section, ensuring minimal permissions and alphabetical order of resources.
Tech stack
typescript
Domain
cliapi
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitMarkdown
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75