pnp / pnp/cli-microsoft365

Working with Entra ID permissions

Open
#5,666 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

epic
Dominant language
TypeScript
Stars
1.5k
Forks
413
Avg merge
5d 6h
Merged PRs (30d)
21

Description

We've recently added app permission add for working with permissions of app registrations. But that command can only be used when you are working with a m365rc.json file.

We also have:

  • aad approleassignment add but that only adds app-only permissions to service principals, not to App Registrations.
  • aad oauth2grant add but that only adds delegated permissions to service principals, not to App Registrations.
  • We're currently building aad app permission add to add app-only as well as delegated permissions to App registrations.

I think we need a couple more commands to be able to cover the entire permissions thing and to make the experience of working with permissions a little more consistent:

Working with App Registrations
  • #4922
  • #5668
  • #5691
  • #5786
Working with Service Principals

Service Principals can be instances of App Registrations, but they don't have to be. (as in the case of managed identities). We already support working with service principals, but the experience is not very consistent and clear. Bundling this in a single command and allowing users to work with resource URL's and scopes would be a great step forward in my opinion.

  • #5777
  • #5778
  • #5779

From this list, aad sp permission add would in time be able to replace aad approleassignment add and aad oauth2grant add.

Shared code

There's also quite some duplicated code among all these commands that's actually doing the same. I'd suggest we move some code to utils:

  • #5720
Fixes

We're also implementing a rename of entra serviceprincipal <verb> commands.

  • #5680

Other fixes

  • #6115

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked issues under the App Registrations, Service Principals, Shared code, and Fixes sections, especially the unchecked #5777, #5778, and #6115. The issue is a broad permissions roadmap rather than a self-contained task; done would require the relevant command coverage and consistency work to be defined and completed.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authorization, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.