Adding New Property DisableDefaultServerHeaderInResponse - #30025
Merged
ZelinWang (wangzelin007) merged 4 commits intoAug 20, 2026
Conversation
abhi20091999
requested review from
santoshgh317
and
a lite review from Copilot
August 17, 2026 17:23
Contributor
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds support for the DisableDefaultServerHeaderInResponse Application Gateway global setting to Az.Network by surfacing it on the PSApplicationGateway output type and exposing it as a new parameter on New-AzApplicationGateway, along with corresponding help and changelog updates.
Changes:
- Added
DisableDefaultServerHeaderInResponsetoPSApplicationGatewayso it appears on Application Gateway output objects. - Added
-DisableDefaultServerHeaderInResponsetoNew-AzApplicationGatewayand wires it into the created gateway’s global configuration (where applicable). - Updated cmdlet reference help and Network ChangeLog entry to document the new capability.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| src/Network/Network/Models/PSApplicationGateway.cs | Adds a top-level output property that forwards to GlobalConfiguration.DisableDefaultServerHeaderInResponse. |
| src/Network/Network/ApplicationGateway/NewAzureApplicationGatewayCommand.cs | Introduces the new cmdlet parameter and maps it into the created Application Gateway model. |
| src/Network/Network/help/New-AzApplicationGateway.md | Documents the new parameter in syntax blocks and parameter reference section. |
| src/Network/Network/ChangeLog.md | Notes the new output/parameter capability in the upcoming release notes. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Member
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
Member
|
abhi20091999 |
Member
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
Member
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
The new DisableDefaultServerHeaderInResponse assertions in Test-ApplicationGatewayGlobalConfig fail in playback because the existing session recording predates the property. Reverting until the test can be re-recorded. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
ZelinWang (wangzelin007)
approved these changes
Aug 20, 2026
ZelinWang (wangzelin007)
merged commit Aug 20, 2026
cfc1ca4
into
Azure:release-network-2025-09-01
12 checks passed
1 task done
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.
🤖 PR Validation —⚠️ Review suggested
️✔️Az.Accounts
️✔️Az.ApplicationInsights
️✔️Az.CognitiveServices
️✔️Az.Compute
️✔️Az.Dns
️✔️Az.Maintenance
️✔️Az.ManagedServiceIdentity
️✔️Az.Monitor
️✔️Az.OperationalInsights
️✔️Az.PrivateDns
️✔️Az.RecoveryServices
️✔️Az.Resources
️✔️Az.Security
️✔️Az.ServiceBus
️✔️Az.Sql
️✔️Az.Storage
Description
In this PR we are adding a new property called "DisableDefaultServerHeaderInResponse" to disable default server header from response.
Swagger PR has already been merged for this new property. :- Azure/azure-rest-api-specs#44796
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.