[Network] Add New/Get/Remove-AzVirtualNetworkApplianceCapability cmdlets For VNRA

[Mangilal Bishnoi (iml-v)]

Adds Azure PowerShell cmdlets to manage the Virtual Network Appliance capability child
resource (Microsoft.Network/virtualNetworkAppliances/capabilities, api-version 2026-03-01).

New cmdlets (Az.Network):

• New-AzVirtualNetworkApplianceCapability — create a capability on an appliance.
• Get-AzVirtualNetworkApplianceCapability — get one capability, or list all on an appliance.
• Remove-AzVirtualNetworkApplianceCapability — delete a capability.

The capability is a discriminated resource selected by -Kind, covering all four kinds:
PLGatewayFastpath, PLGateway, PLIPForwarders, and NAT64. -IpVersion is required for the
Private Link kinds (the service validates it against the kind: FastPath → DualStack;
PLGateway/PLIPForwarders → IPv6) and is not accepted for the property-less NAT64 kind.
kind, linkedResourceId, and provisioningState are read-only.

Includes: the generated SDK capability operations/models, PS model, AutoMapper-free projection,
ChangeLog.md, platyPS markdown help for all three cmdlets, module landing-page entries, and unit
tests for the client-side kind/ipVersion logic.

Cmdlet design review:

Notes for reviewers

• Target api-version is 2026-03-01; the SDK capability types will be aligned with the official
  Network SDK regeneration for that version.
• Full create/get/list/delete scenario test recordings are added in a follow-up once a
  feature-enabled dual-stack environment is available; client-side logic is covered by unit tests in
  this PR.

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.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Copilot review overview

🟡 Changes recommended

The base cmdlet contains a compilation error and does not fully validate documented capability/IP-version combinations.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1 · 2

Open (3)

• Missing System.Management.Automation import causes compilation failure · New
• Validate IP version against selected gateway kind · New
• Validate ARM resource ID provider and segment structure · New

What changed in this PR

Adds PowerShell cmdlets for managing Virtual Network Appliance capabilities, including generated SDK support, documentation, exports, changelog, and unit tests.

Changes:

• Added New, Get, and Remove cmdlets.
• Added capability models and SDK operations.
• Added help files, exports, and client-side unit tests.

File	Description
VirtualNetworkApplianceCapabilityBaseCmdlet.cs	Shared capability logic and payload creation
NewVirtualNetworkApplianceCapabilityCommand.cs	Creates capabilities
GetVirtualNetworkApplianceCapabilityCommand.cs	Retrieves capabilities
RemoveVirtualNetworkApplianceCapabilityCommand.cs	Removes capabilities
PSVirtualNetworkApplianceCapability.cs	PowerShell output model
Get-AzVirtualNetworkApplianceCapability.md	Get cmdlet help
New-AzVirtualNetworkApplianceCapability.md	New cmdlet help
Remove-AzVirtualNetworkApplianceCapability.md	Remove cmdlet help
ChangeLog.md	Release notes
Az.Network.psd1	Cmdlet exports
VirtualNetworkApplianceCapabilityUnitTests.cs	Unit coverage
Generated SDK files	API operations, models, polymorphism, and client wiring

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Copilot review overview

🟡 Changes recommended

The create path does not enforce the documented capability kind and IP-version combinations.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 2 · 1

Open (3)

• Validate PL gateway kind and IP version combinations · New
• Validate IP version against selected gateway kind
• Add ResourceId parser validation and malformed ID tests · New

Resolved since last review (2)

• Missing System.Management.Automation import causes compilation failure
• Validate ARM resource ID provider and segment structure

[Mangilal Bishnoi (iml-v)]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 30173 in repo Azure/azure-powershell

[Copilot]

Copilot review overview

🔵 Needs a closer look

The PR adds a new generated SDK surface without scenario recordings, so end-to-end API behavior requires human validation.

Review effort: Lite
Findings: 1

Open (1)

• Add ResourceId parser validation and malformed ID tests

Resolved since last review (2)

• Validate PL gateway kind and IP version combinations
• Validate IP version against selected gateway kind

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).

[Copilot]

Copilot review overview

🟡 Changes recommended

One or more issues must be addressed before approval.

Review effort: Lite
Findings: 1

Open (1)

• Update README spec and regenerate the SDK · New

Resolved since last review (1)

• Add ResourceId parser validation and malformed ID tests

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).