pnp/cli-microsoft365

Minimal permissions for 'viva engage related' commands

Open

#7,538 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 viva engage community-user add
  • m365 viva engage community-user list
  • m365 viva engage community-user remove
  • m365 viva engage message-like set
  • m365 viva engage network list
  • m365 viva engage role list
  • m365 viva engage role-member list
  • m365 viva engage role-member remove
  • m365 viva engage search
  • m365 viva engage user get
  • m365 viva engage user list

Contributor guide

Research direction
Review the existing docs for planner commands to see the Permissions section format. Read the provided guides to learn how to find minimal permissions. For each viva engage command listed, add the Permissions section before Examples, ordering resources alphabetically. Use the planner examples as templates. Verify permissions by checking the command source or Graph API docs.
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.
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.
80