pnp/cli-microsoft365

Minimal permissions for 'spo sitedesign related' commands

Open

#7,505 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 sitedesign rights grant
  • m365 spo sitedesign rights list
  • m365 spo sitedesign rights revoke
  • m365 spo sitedesign run list
  • m365 spo sitedesign run-status get
  • m365 spo sitedesign task get
  • m365 spo sitedesign task list
  • m365 spo sitedesign task remove

Contributor guide

Research direction
Inspect the existing markdown files for the listed sitedesign commands under the docs directory. Study the provided planner examples to understand the permissions documentation format. Use the linked resources to determine the minimal delegated and app only permissions for each command, then add a Permissions section before the Examples section in each command's documentation file.
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.
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.
Active
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