DOC-299: Update Azure Role Definition and Role Assignment articles - #900
Open
quetzalliwrites wants to merge 1 commit into
Open
DOC-299: Update Azure Role Definition and Role Assignment articles#900quetzalliwrites wants to merge 1 commit into
quetzalliwrites wants to merge 1 commit into
Conversation
The opt-in RBAC enforcement section and most limitations were already documented on both pages. Add the gaps called out in the ticket: data-plane coverage is partial (Storage File, Service Bus, and Cosmos DB aren't covered; SQL/PostgreSQL/MySQL are out of scope since they use Entra database auth, not RBAC data actions), Key Vault keys are not yet enforced, and group role assignments aren't expanded to their members. Also note that management group scope is the only scope level without inheritance support.
quetzalliwrites
requested review from
HarshCasper and
remotesynth
as code owners
August 28, 2026 14:26
Deploying localstack-docs with
|
| Latest commit: |
1e60571
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b1b2519b.localstack-docs.pages.dev |
| Branch Preview URL: | https://doc-299-update-azure-role-de.localstack-docs.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The ticket asked to update the
role-definitionandrole-assignmentarticles to reflect the new opt-in Azure RBAC enforcement engine (LS_AZURE_ENFORCE_RBAC). On inspection, the "RBAC enforcement" section and most of the updated limitations were already present on both pages (role-assignment.mdxhas a full## Enabling RBAC enforcementsection, androle-definition.mdxcross-links to it). This PR fills in the remaining gaps called out in the ticket's target limitations list, rather than duplicating the whole block onto both pages:role-assignment.mdx: added "Data-plane coverage is partial" (Storage File, Service Bus data plane, and Cosmos DB aren't covered; Azure SQL/PostgreSQL/MySQL are out of scope since they use Microsoft Entra database auth, not RBAC data actions), "Key Vault keys" (not yet enforced), and "Groups and transitive membership" (not expanded to members) limitation bullets. Also clarified that subscription/resource-group/resource scopes support inheritance, unlike management group scope.role-definition.mdx: added the "Key Vault keys" bullet, which the ticket calls out as the most relevant addition for this page (role definitions can declareDataActionsfor keys, but that data plane isn't enforced yet).Linear ticket
https://linear.app/localstack/issue/DOC-299/update-azure-role-definition-and-role-announcement-articles
Test plan
npx astro buildcompletes successfully (404 pages built)