feat: azure per-operation runner managed identities#1946
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
im-Amitto
force-pushed
the
am/azure-perop-identities
branch
from
July 19, 2026 22:40
8bd7cf4 to
a8937fc
Compare
… don't report outputs
im-Amitto
added
the
promote-all
Comment on lines
+174
to
+175
| "--server-id", | ||
| "6dae42f8-4368-4678-94ff-3960e28e3630", |
Contributor
Author
There was a problem hiding this comment.
it's azure k8s AAD Server application ID, constant
erickyellott
approved these changes
Jul 20, 2026
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
2 participants
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.
Adds Azure per-operation user-assigned managed identities so the install runner assumes a scoped identity per operation (provision/maintenance/deprovision/custom/break-glass) instead of holding broad standing grants — the Azure equivalent of AWS assume-role / GCP impersonation. When Azure roles are configured, the broad grants (Contributor/RBAC-Admin/AKS-Admin/register-action) are stripped from the runner's VMSS system identity; installs without Azure roles keep legacy behavior. App config gains
azure_actions/azure_built_in_roles, and the ARM template creates + attaches the identities and surfaces their client IDs via phone-home.