Added Client IP Preservation properties to Application Gateway model #28685
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
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Pull Request Overview
This PR adds support for client IP preservation in Azure Application Gateway by introducing two new properties: EnableL4ClientIpPreservation for backend settings and EnableProbeProxyProtocolHeader for probe configurations. These properties enable the Application Gateway to send proxy protocol headers to backend servers and health probes respectively.
Key changes:
- Added new boolean properties to PowerShell models for proxy protocol header support
- Updated cmdlet parameters and help documentation for backend settings and probe configurations
- Implemented default value handling (false) when parameters are not provided
Reviewed Changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| PSApplicationGatewayProbe.cs | Added EnableProbeProxyProtocolHeader property to probe model |
| PSApplicationGatewayBackendSettings.cs | Added EnableL4ClientIpPreservation property to backend settings model |
| AzureApplicationGatewayProbeConfigBase.cs | Implemented parameter handling and default value logic for probe proxy protocol |
| AzureApplicationGatewayBackendSettingsBase.cs | Implemented parameter handling and default value logic for client IP preservation |
| Help files (6 files) | Updated cmdlet documentation to include new parameter descriptions |
| ChangeLog.md | Documented the new features and affected cmdlets |
src/Network/Network/help/New-AzApplicationGatewayBackendSetting.md
Outdated
Show resolved
Hide resolved
…g.md Co-authored-by: Copilot <[email protected]>
|
/azp run |
|
Commenter does not have sufficient privileges for PR 28685 in repo Azure/azure-powershell |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
isra-fel
approved these changes
Oct 15, 2025
|
The check is behaving weirdly. Let me close and reopen |
|
It's the same. @akshimittal1310 can you try the instructions above? |
|
@microsoft-github-policy-service agree company="Microsoft" |
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
This PR adds support for sending proxy protocol headers to backends over TCP and TLS protocols in the Application Gateway Backend Settings and Probe PowerShell models and cmdlets.
Introduced EnableL4ClientIpPreservation and EnableProbeProxyProtocolHeader properties in the PS model class.
Updated the Help section for new properties for each cmdlet (Set, Get and Add)
Added details in ChangeLog file
Ensured default values align with the API spec when parameters are not provided.
Swagger PR to add these properties is already merged
https://github.com/Azure/azure-rest-api-specs/pull/37340/files
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.