-
Notifications
You must be signed in to change notification settings - Fork 112
Consul Docs: Azure auto-join MSI clarification #1346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
nphilbrook
merged 4 commits into
hashicorp:main
from
nphilbrook:nphilbrook_azure_auto_join
Dec 4, 2025
Merged
Consul Docs: Azure auto-join MSI clarification #1346
nphilbrook
merged 4 commits into
hashicorp:main
from
nphilbrook:nphilbrook_azure_auto_join
Dec 4, 2025
Conversation
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
Contributor
Vercel Previews Deployed
|
Contributor
Broken Link CheckerNo broken links found! 🎉 |
boruszak
reviewed
Nov 26, 2025
Contributor
boruszak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please implement suggestions for style guide alignment.
content/consul/v1.22.x/content/docs/deploy/server/cloud-auto-join.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
boruszak
approved these changes
Dec 3, 2025
Contributor
boruszak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
While figuring out how to use Azure auto-join from VMs with both a System-managed identity and a User-managed identity, when I needed to use the User-managed identity, I stumbled on some serious pain. This is probably not the best way to explain it, but I wanted others to benefit from my journey of pain. I will happily accept any suggestions on wording, organization, or verbiage. The 2 main points I want to get across that I discovered from reading both the go-discover code and the Azure/go-autorest code are that:
AZURE_CLIENT_IDand NOTARM_CLIENT_ID. Code references from Azure/go-autorest:Direct Preview link
Contributor checklists
Review urgency:
Pull request:
Content:
Reviewer checklist