[Az.Accounts] Fix ClientRequestId being overwritten in telemetry payload#29014
Merged
DanielMicrosoft merged 3 commits intoAzure:mainfrom Jan 4, 2026
Merged
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes an issue where the ClientRequestId telemetry value was being incorrectly overwritten by server-side response headers. The fix ensures that once ClientRequestId is set from client-side request headers in OnBeforeCall, it will not be overwritten when OnResponseCreated processes the response headers.
Key changes:
- Added a guard condition in
OnResponseCreatedto prevent overwritingClientRequestIdif it's already populated - Preserves the client-side request ID as the source of truth for telemetry
Member
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
|
@dolauli , could you review this PR? Thanks. |
dolauli
approved these changes
Jan 4, 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
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
Fixes #23555
Previously, the value in telemetry for
ClientRequestIdwould be derived from the client sidex-ms-client-request-id, however it would be overwritten by thex-ms-request-idcoming back from the server side.This would also set
Properties['x-ms-client-request-id']in telemetry to be that value from the server responsex-ms-request-id.This issue would be inherited by AutoRest generated modules.
This PR will adjust behaviour of setting telemetry values to use the client side
x-ms-client-request-idas theClientRequestIdin telemetry, and preserve it in theProperties['x-ms-client-request-id']value also.Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.