[v17] Support resolving Azure identities from VM scale set for SQL Server connections#52267
Merged
gabrielcorado merged 1 commit intobranch/v17from Feb 24, 2025
Conversation
greedy52
approved these changes
Feb 18, 2025
Contributor
greedy52
left a comment
There was a problem hiding this comment.
@gabrielcorado do we need a doc update on the permission for scale set? The current doc says Microsoft.Compute/virtualMachines/read.
probakowski
approved these changes
Feb 24, 2025
Merged
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
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.
Backport #51671 to branch/v17
changelog: Fix Azure SQL Servers connect failures when the database agent runs on a VM scale set.