Join our Newsletter — 33% off our NHI Course

What would it take for Microsoft scoped consent to stay partial?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: A live grant can diverge from an app registration’s requested Microsoft identity platform permissions when scoped consent approves only part of the list, Senserva says. Reviews and revocation need to follow the effective entitlement set, or later flows can widen access again.

Editorial analysis by NHI Mgmt Group, based on content published by Senserva: “Scoped Consent for App Registrations: Granting Partial Permissions in Microsoft Entra ID”.

Key questions

Q: Why can .default undo a carefully scoped Microsoft consent decision?

A: Because .default reuses the configured permission set on the registration, and flows such as prompt=consent or /adminconsent can reprompt for the full list.

Q: How do security teams know if scoped consent is actually working?

A: Look for a consistent delta between requested permissions and live grants, then confirm that token scopes match the smaller approved set.

Q: What breaks when app registrations are treated as live permissions instead of requests?

A: Teams lose sight of the effective entitlement set and may assume an application can use every declared scope.

Practitioner guidance

  • Map declared scopes to live grants Compare requiredResourceAccess on the app registration with oauth2PermissionGrant and appRoleAssignment on the service principal.
  • Review .default and admin consent paths Identify any app or workflow that uses .default, prompt=consent, /adminconsent, or the portal’s admin consent button.
  • Gate features on effective scopes Check returned token scopes and the scp claim before enabling a feature such as calendar sync, file access, or mailbox actions.

Bottom line: Scoped consent exposes a basic IAM truth: a declared permission is not the same thing as an authorised entitlement.

Glossary terms: Scoped consent, App Registration, Oauth2PermissionGrant, Effective Permission Delta

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 3 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Scoped consent is an entitlement-lifecycle problem, not a UI problem: The article shows that Microsoft app registrations ask for permissions, but oauth2PermissionGrant records what the tenant actually approved. That distinction is the governance boundary, because the control exists in the grant object and not in the application’s declared wish list. Practitioners should stop treating consent as a deployment step and start treating it as an entitlement change with review, revocation, and audit requirements.

A question worth separating out:

Q: When should organisations use scoped consent instead of granting the full app permission list?

A: Use it whenever the vendor asks for more than the enabled feature set, or when compliance rules limit specific data paths such as mailbox content or directory write access. Scoped consent is the right control when the tenant can justify a subset and wants the app to function with less privilege.

👉 Read our full editorial: Scoped consent for Microsoft app registrations changes IAM control



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.