Minimal Permissions for all commands

We want to add a new Permissions section to the documentation of all commands. This section lists the minimum permissions (both delegated and application) required to run the command successfully. By documenting only the minimal set of permissions, developers can more easily configure their own app registrations, which in turn simplifies running the CLI with application permissions.

We’ve already established the foundation for this work:

• Clear guide on how to add permissions to the docs: Writing docs page - Permissions
• Clear guidance on how to determine minimal permissions: How to document minimal permissions
• A concrete example of the final design in use:
  • m365 planner plan add - Permissions
  • m365 planner tenant settings list - Permissions

Scope

• Add a Permissions section to each command page.
• Document only the minimal required permissions. When multiple permissions are possible, list only the most restrictive one (e.g. GroupMember.Read.All instead of Group.ReadWrite.All).
• Place the Permissions section right before the Examples section for consistency across all commands.
• 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

Commands to Update

We’ll update all commands, grouped by CRUD operations. Each group will be tracked in a separate issue, so folks can easily pick them up.

Start with the Writing docs page on Permissions and the guide for documenting minimal permissions, then compare the existing planner command pages linked in the issue. Update each command page with delegated and application permissions immediately before Examples, ordering multiple resources alphabetically. Done means every command page in the assigned group has a minimal Permissions section following the documented format.