Skip to content

Add Managed HSM support to Application Gateway SSL certificate cmdlets#29418

Open
srijanee wants to merge 1 commit intoAzure:release-network-2025-07-01from
srijanee:feature/appgw-managed-hsm-ssl-cert
Open

Add Managed HSM support to Application Gateway SSL certificate cmdlets#29418
srijanee wants to merge 1 commit intoAzure:release-network-2025-07-01from
srijanee:feature/appgw-managed-hsm-ssl-cert

Conversation

@srijanee
Copy link
Copy Markdown

Description

Adds Managed HSM (Hardware Security Module) support to Application Gateway SSL certificate PowerShell cmdlets, based on swagger changes from Azure/azure-rest-api-specs#42137.

New model: ApplicationGatewayManagedHsm

  • KeyId — URI of a key stored in Managed HSM
  • PublicCertData — Base-64 encoded public certificate data (read-only from service)

New cmdlet parameters

  • -HsmKeyId — Key identifier of a key stored in Managed HSM
  • -HsmPublicCertData — Base-64 encoded public certificate data

Affected cmdlets

  • New-AzApplicationGatewaySslCertificate
  • Set-AzApplicationGatewaySslCertificate
  • Add-AzApplicationGatewaySslCertificate

Changes

Layer Files
SDK models ApplicationGatewayManagedHsm.cs (new), ApplicationGatewaySslCertificate.cs, ApplicationGatewaySslCertificatePropertiesFormat.cs
PS models PSApplicationGatewayManagedHsm.cs (new), PSApplicationGatewaySslCertificate.cs
AutoMapper NetworkResourceManagerProfile.cs — bidirectional mapping
Cmdlet base AzureApplicationGatewaySslCertificateBase.cs — new parameters + NewObject()
Help docs New/Set/Add SSL certificate help markdown
ChangeLog Entry added

Note: SDK model files were manually created to match what AutoRest would generate. These will be overwritten once full SDK generation from the 2025-07-01 TypeSpec-consolidated swagger is completed.

Testing

  • SDK project builds: dotnet build src/Network/Network.Management.Sdk/Network.Management.Sdk.csproj — 0 errors, 0 warnings
  • Network project builds: dotnet build src/Network/Network/Network.csproj — 0 errors, 0 warnings

@azure-client-tools-bot-prd
Copy link
Copy Markdown

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

@VeryEarly
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@VeryEarly
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@@ -0,0 +1,2 @@
"Module","Sdk","Severity","ProblemId","Description","Remediation"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please do not manually update SDK code, regenerate with a new commit ID instead

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am making changes for new Swagger branch 2025-07-01. How do I make PS changes for 2025-07-01, should I wait for SDK to be generated officially and merge on this release branch on work on it?

- Updated README.md to 2025-07-01 TypeSpec-consolidated swagger specs
  (commit 906c9971ea, 16 files replacing 66 individual 2025-05-01 files)
- Regenerated SDK via autorest (1940 files)
- Added PSApplicationGatewayManagedHsm PS model
- Updated PSApplicationGatewaySslCertificate with Hsm property
- Added AutoMapper bidirectional mappings for ManagedHsm
- Added -HsmKeyId and -HsmPublicCertData parameters to
  New/Set/Add-AzApplicationGatewaySslCertificate cmdlets
- Updated help docs with HSM examples and parameter documentation
- Updated ChangeLog

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@srijanee srijanee force-pushed the feature/appgw-managed-hsm-ssl-cert branch from 456b4f7 to 7d6e211 Compare April 24, 2026 07:02
@VeryEarly
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants