[release/v7.5.11] Use Azure CLI for early-access feed token - #27953
Merged
Aditya Patwardhan (adityapatwardhan) merged 1 commit intoSep 2, 2026
Conversation
Co-authored-by: Justin Chung <chungjustin@microsoft.com> Copilot-Session: 8784f802-9d66-4692-b64d-c0713fa213cb
Aditya Patwardhan (adityapatwardhan)
requested a review
from a team
as a code owner
September 2, 2026 22:50
Aditya Patwardhan (adityapatwardhan)
added
the
CL-BuildPackaging
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Copilot started reviewing on behalf of
Aditya Patwardhan (adityapatwardhan)
September 2, 2026 22:51
View session
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
The change alters authenticated token acquisition in CI, which is difficult to validate safely without observing PR pipeline execution across the target agent images and service connection behavior.
Pull request overview
This PR backports the pipeline-template change from #27849 to release/v7.5.11, switching early-access Azure DevOps feed token acquisition to use AzureCLI@2 so Linux agents no longer depend on a preinstalled Az.Accounts module.
Changes:
- Replace
AzurePowerShell@5withAzureCLI@2for acquiring the Azure DevOps access token. - Add explicit failure handling when
az account get-access-tokenfails or returns an empty token.
File summaries
| File | Description |
|---|---|
.pipelines/templates/insert-nuget-config-azfeed.yml |
Updates the early-access feed token acquisition step to use Azure CLI and fail fast on token acquisition failure. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Patrick Meinecke (SeeminglyScience)
approved these changes
Sep 2, 2026
Aditya Patwardhan (adityapatwardhan)
merged commit Sep 2, 2026
1aeea89
into
PowerShell:release/v7.5.11
35 checks passed
Aditya Patwardhan (adityapatwardhan)
deleted the
backport/release/v7.5.11/27849-174a75396
branch
September 2, 2026 23:02
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 of #27849 to release/v7.5.11
Triggered by Aditya Patwardhan (@adityapatwardhan) on behalf of Justin Chung (@jshigetomi)
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Required pipeline fix for SDK validation: acquire the early-access Azure DevOps feed token with AzureCLI@2 so Linux agents do not depend on a preinstalled Az.Accounts module, and fail explicitly when token acquisition fails.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Original change was motivated by Linux SDK validation build 707180 failing before its inline script while equivalent Windows and macOS jobs succeeded. On release/v7.5.11, the merge commit cherry-picked without conflicts; the target-relative diff was reviewed to contain only the intended pipeline-template change, and git diff --check passed. End-to-end service-connection and token acquisition behavior requires backport PR CI.
Risk
REQUIRED: Check exactly one box.
High risk because this changes the authenticated token-acquisition task used by SDK validation across platforms. The change is narrowly scoped to one pipeline template, preserves the existing service connection and token secret handling, adds explicit failure handling, and has already been merged and used on newer branches; PR CI remains required.