docs(internal): add rp-auto-onboarding linked access check summary#1736
Open
zanejohnson-azure wants to merge 5 commits into
Open
docs(internal): add rp-auto-onboarding linked access check summary#1736zanejohnson-azure wants to merge 5 commits into
zanejohnson-azure wants to merge 5 commits into
Conversation
Team brief on the ama-logs linked access check: what it is in ama-logs scope, why it's needed, why/whether/how it can be removed, with impact broken down by auth path (legacy shared-key vs managed-identity). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Retitle to '...Can & How We Remove It' and pull latest edits from the source team brief. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ck summary The synced brief had backslash-escaped '**' on bold spans that wrap across a line break, which renders as literal asterisks on GitHub. Restore proper bold; title change retained. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ted brief Add TL;DR two-group table; reframe #2 (workspaces/read) as the caller-side mirror of the workspace GET aks-rp does on both paths to inject the workspace GUID; mark preferred removal options; add MSI config-chunk GUID self-derivation detail; firm up Q3 region-build wording. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Correctness fix: #2 (workspaces/read) is the caller-side mirror of the workspace GET aks-rp does to read the GUID (CustomerID) it injects into the ama-logs helm chart. Drops the earlier 'read guard / association guard' framing that overstated #2 as a standalone access-control guard. Aligned across TL;DR, Q1, Q2, and both Q4 blocks. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
What
Adds an internal team brief on the ama-logs linked access check at:
Documentation/Internal/Projects/rp-auto-onboarding/linked-access-check-summary.mdContents
A concise, shareable overview organized as five questions:
managedClusters/writeto caller permissions on the workspace named inomsagent.config.logAnalyticsWorkspaceResourceID.Notes
⚠️ **TO BE CONFIRMED**/⚠️ **[TO BE DISCUSSED]**for review.Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com