pnp/cli-microsoft365

Minimal permissions for 'spo miscellaneous' commands. Part 2

Open

#7,490 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 knowledgehub get
  • m365 spo knowledgehub remove
  • m365 spo knowledgehub set
  • m365 spo orgassetslibrary add
  • m365 spo orgassetslibrary list
  • m365 spo orgassetslibrary remove
  • m365 spo orgnewssite list
  • m365 spo orgnewssite remove
  • m365 spo orgnewssite set
  • m365 spo search
  • m365 spo set
  • m365 spo userprofile get
  • m365 spo userprofile set

Contributor guide

Research direction
For each listed command, inspect the source code to identify the API calls, then consult the linked documentation to determine the minimal delegated and application permissions. Add a Permissions section right before Examples, ordering resources alphabetically. If a command supports only one auth type, document that as in the planner examples.
Tech stack
nodejstypescript
Domain
clidocumentation
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.
Half day
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
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75