Add late-bound idToken support with telemetry to AzureCLIV3 task #21601
+409
−2
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
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
tpavlovi
force-pushed
the
users/tpavlovi/idToken
branch
from
093629a to
17e65c3
Compare
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
tpavlovi
force-pushed
the
users/tpavlovi/idToken
branch
from
17e65c3 to
3cc03ba
Compare
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
rm-dmiri
approved these changes
Dec 18, 2025
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.
Context
This PR implements late-bound idToken support in the AzureCLIV3 task, controlled by the
EnableLateBoundIdTokenfeature flag.AB#2341991
Task Name
AzureCLIV3
Description
Modified
getIdToken()method to check for late-bound idToken when feature flag is enabledThe same change was added for the AzureCLIV2 task in this PR: #21580
Risk Assessment (Low / Medium / High)
Low
Change Behind Feature Flag (Yes / No)
Yes (
EnableLateBoundIdToken)Tech Design / Approach
Documentation Changes Required (Yes/No)
No
Unit Tests Added or Updated (Yes / No)
Yes
Additional Testing Performed
Logging Added/Updated (Yes/No)
Yes
Telemetry Added/Updated (Yes/No)
Rollback Scenario and Process (Yes/No)
Revert dynamic FF
EnableLateBoundIdTokenDependency Impact Assessed and Regression Tested (Yes/No)
Yes
Checklist