Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 17:36:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Remove Contributions welcome boilerplate from do-not-grant article for consistency

Browse source 
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Jesper Schulz-Wedde 2026-07-10 12:29:12 +02:00
parent 2350e10966
commit 7c4d7e49f2
1 changed files with 0 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
microsoft/knowledge/security/do-not-grant-rights-beyond-a-users-entitlement.md
View file

@ -9,8 +9,6 @@ application-area: [all]
# Do not grant rights beyond a user's entitlement # Do not grant rights beyond a user's entitlement
> Contributions welcome — open a PR to refine or extend this article.
## Description ## Description
Entitlements are license-level caps on what a user can access, derived automatically from the BC license tier. Permission sets are application-level grants administered on top of the entitlement. A permission set can only grant within the entitlement's boundaries; grants beyond those boundaries are silently clipped at runtime. This means a permission set authored and validated in a developer sandbox (with a broad license) can appear to work correctly there and fail silently in a customer tenant where users hold a narrower entitlement. Entitlements are license-level caps on what a user can access, derived automatically from the BC license tier. Permission sets are application-level grants administered on top of the entitlement. A permission set can only grant within the entitlement's boundaries; grants beyond those boundaries are silently clipped at runtime. This means a permission set authored and validated in a developer sandbox (with a broad license) can appear to work correctly there and fail silently in a customer tenant where users hold a narrower entitlement.