pnp/cli-microsoft365

Minimal permissions for 'spo term related' commands

Open

#7,512 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 term add
  • m365 spo term get
  • m365 spo term group add
  • m365 spo term group get
  • m365 spo term group list
  • m365 spo term list
  • m365 spo term set add
  • m365 spo term set get
  • m365 spo term set list

Contributor guide

Research direction
Review the existing documentation for similar commands, such as the Planner examples linked in the issue, to see how the Permissions section is formatted. For each of the listed 'm365 spo term' commands, find the minimal permissions required by examining the source code in the repository or the Microsoft Graph documentation for SharePoint term store APIs. Then add a Permissions section right before the Examples section for each command doc, ensuring resources are ordered alphabetically and noting if only one auth type is supported.
Tech stack
typescript
Domain
clidocumentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75