From 7c4d7e49f2a42e81136b8e60170fd1e262e9203f Mon Sep 17 00:00:00 2001 From: Jesper Schulz-Wedde Date: Fri, 10 Jul 2026 12:29:12 +0200 Subject: [PATCH] Remove Contributions welcome boilerplate from do-not-grant article for consistency Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- .../security/do-not-grant-rights-beyond-a-users-entitlement.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/microsoft/knowledge/security/do-not-grant-rights-beyond-a-users-entitlement.md b/microsoft/knowledge/security/do-not-grant-rights-beyond-a-users-entitlement.md index 387c778..bc9a4e8 100644 --- a/microsoft/knowledge/security/do-not-grant-rights-beyond-a-users-entitlement.md +++ b/microsoft/knowledge/security/do-not-grant-rights-beyond-a-users-entitlement.md @@ -9,8 +9,6 @@ application-area: [all] # Do not grant rights beyond a user's entitlement -> Contributions welcome — open a PR to refine or extend this article. - ## 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.