Skip to content

Swagger changes for afc configuration - Azfw - #42245

Merged
Sai Sujith Reddy Mankala (saisujithreddym) merged 21 commits into
Azure:release-microsoft-network-2025-07-01from
saisujithreddym:release-microsoft-network-2025-07-01
Apr 21, 2026
Merged

Sai Sujith Reddy Mankala (saisujithreddym) merged 21 commits into
Azure:release-microsoft-network-2025-07-01from
saisujithreddym:release-microsoft-network-2025-07-01

Conversation

@saisujithreddym

@saisujithreddym Sai Sujith Reddy Mankala (saisujithreddym) commented Apr 9, 2026 •

Copy link
Copy Markdown
Contributor

Azure Firewall for Container Control Plane:

  • Azure Firewall will expose a new field called afcConfiguration in the GET call if there is an afc control plane deployed.
  • We are introducing a new query param called createAfcControlPlane=True which will create the new control plane.
  • If the param is not present/true, the firewall operations will be the same as the existing ones in prod

@github-actions

github-actions Bot commented Apr 9, 2026 •

Copy link
Copy Markdown

Next Steps to Merge

Important checks have failed. As of today they are not blocking this PR, but in near future they may.
Addressing the following failures is highly recommended:
  • ⚠️ The check named SDK Validation Status has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide
If you still want to proceed merging this PR without addressing the above failures, refer to step 4 in the PR workflow diagram.

Comment generated by summarize-checks workflow run.

@github-actions github-actions Bot added ARMReview resource-manager TypeSpec Authored with TypeSpec WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required BreakingChange-Go-Sdk BreakingChange-JavaScript-Sdk labels Apr 9, 2026
….com/saisujithreddym/azure-rest-api-specs into release-microsoft-network-2025-07-01

# Conflicts:
#	specification/network/resource-manager/Microsoft.Network/Network/stable/2025-07-01/firewall.json
@saisujithreddym

Copy link
Copy Markdown
Contributor Author

rebuild

@mentat9

Copy link
Copy Markdown
Contributor

Sai Sujith Reddy Mankala (@saisujithreddym) - Please fix the required CI checks (Swagger Avocado) before ARM review.

@mentat9 Chris Stackhouse (mentat9) added ARMChangesRequested and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Apr 11, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the Azure Firewall ARM control-plane spec (2025-07-01) to support an AFC (Azure Firewall for Containers) control plane by adding a read-only configuration block in responses and introducing a new create-time query parameter, along with corresponding Swagger/TypeSpec examples.

Changes:

  • Add afcControlPlaneConfiguration (read-only) to Azure Firewall properties in Swagger + TypeSpec models.
  • Add createAfcControlPlane optional query parameter to AzureFirewall PUT (CreateOrUpdate).
  • Add new GET/PUT examples demonstrating AFC control plane presence/creation.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
specification/network/resource-manager/Microsoft.Network/Network/stable/2025-07-01/firewall.json Adds PUT query param + adds read-only AFC control plane configuration to the Azure Firewall schema; wires new examples.
specification/network/resource-manager/Microsoft.Network/Network/stable/2025-07-01/common.json Introduces AfcControlPlaneConfiguration schema.
specification/network/resource-manager/Microsoft.Network/Network/stable/2025-07-01/examples/AzureFirewallPutWithAfcControlPlane.json New Swagger example for PUT with createAfcControlPlane=true and AFC config in response.
specification/network/resource-manager/Microsoft.Network/Network/stable/2025-07-01/examples/AzureFirewallGetWithAfcControlPlane.json New Swagger example for GET returning AFC control plane configuration.
specification/network/resource-manager/Microsoft.Network/Network/Network/models.tsp Adds TypeSpec model + read-only property on AzureFirewallPropertiesFormat.
specification/network/resource-manager/Microsoft.Network/Network/Network/AzureFirewall.tsp Adds createAfcControlPlane query parameter to the TypeSpec createOrUpdate operation.
specification/network/resource-manager/Microsoft.Network/Network/Network/examples/2025-07-01/AzureFirewallPutWithAfcControlPlane.json New TypeSpec example for PUT with AFC control plane.
specification/network/resource-manager/Microsoft.Network/Network/Network/examples/2025-07-01/AzureFirewallGetWithAfcControlPlane.json New TypeSpec example for GET returning AFC control plane configuration.

@saisujithreddym

Sai Sujith Reddy Mankala (saisujithreddym) commented Apr 13, 2026 •

Copy link
Copy Markdown
Contributor Author

Chris Stackhouse (@mentat9) The avacado checks are failing because of some unrelated changes that were already there. Looks like it was caused by having different api versions in the readme: https://github.com/Azure/azure-rest-api-specs/blob/release-microsoft-network-2025-07-01/specification/network/resource-manager/Microsoft.Network/Network/readme.md?plain=1#L56. I was told to get a review/approval to bypass this

@saisujithreddym

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Commenter does not have sufficient privileges for PR 42245 in repo Azure/azure-rest-api-specs

@saisujithreddym Sai Sujith Reddy Mankala (saisujithreddym) changed the title Swagger changes for afc control plane Swagger changes for afc configuration Apr 13, 2026
@github-actions github-actions Bot added ARMAutoSignedOff-IncrementalTSP ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review labels Apr 18, 2026
@github-actions github-actions Bot added ARMAutoSignedOff-IncrementalTSP ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMAutoSignedOff-IncrementalTSP ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review labels Apr 18, 2026
@github-actions github-actions Bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 18, 2026
@saisujithreddym

Copy link
Copy Markdown
Contributor Author

Both the C# and Python SDK generation failures are pre-existing issues unrelated to the AfcConfiguration changes. C# fails due to 55 DuplicateSchema errors (missing lenient-model-deduplication in C# config — Go and Python already have it). Python SDK generation actually succeeded (built azure-mgmt-network-30.3.0b1), but the pipeline reports failure because changelog generation timed out (900s) which caused stable.json to be deleted before the breaking changes checker could read it (FileNotFoundError). These failures reproduce on any PR touching the 2025-07-01 Network spec.

@tadelesh

Copy link
Copy Markdown
Member

/azp run SDK Validation - Python

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@github-actions github-actions Bot added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required ARMAutoSignedOff-IncrementalTSP ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMAutoSignedOff-IncrementalTSP ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Apr 20, 2026
@saisujithreddym
Sai Sujith Reddy Mankala (saisujithreddym) merged commit 3fd8250 into Azure:release-microsoft-network-2025-07-01 Apr 21, 2026
33 of 40 checks passed
shubhika1795 pushed a commit that referenced this pull request Apr 21, 2026
* Swagger changes for afc control plane

* Add afcControlPlaneConfiguration to Azure Firewall TypeSpec and generated swagger for 2025-07-01

* Renamed the response

* Swap parameter order
Rajkumar Chepala (rchepala) pushed a commit to rchepala/azure-rest-api-specs that referenced this pull request Apr 28, 2026
* Swagger changes for afc control plane

* Add afcControlPlaneConfiguration to Azure Firewall TypeSpec and generated swagger for 2025-07-01

* Renamed the response

* Swap parameter order
DevBaburaj pushed a commit that referenced this pull request May 19, 2026
* Add API version 2025-07-01 for Microsoft.Network (#41904)

* Add API version 2025-07-01 for Microsoft.Network

* Add stable/2025-07-01 OpenAPI specs and examples

* Fix tsp format indentation in main.tsp

* Add cspell suppressions for stable/2025-07-01 spell check errors

* Fixed some issues based on suggestions from Reviewer

* Fixed some values in the examples folder

---------

Co-authored-by: Santosh Lokarapu <v-slokar@microsoft.com>

* [Ddos] Add ILPIP DCP in 2025-07-01 TypeSpec/Swagger (#42075)

* [Network] Add ILPIP DCP in 2025-07-01 TypeSpec/Swagger

* Update DCP references and regenerate 2025-07-01 network swagger

* Add version gates for DCP properties in 2025-07-01

* Revert "Add version gates for DCP properties in 2025-07-01"

This reverts commit 8ffec04.

* Fix: Reorder decorators to match file formatting standard

- Move #suppress decorators before @visibility decorators
- Fixes TypeSpec format validation (tsp format --check)
- Both properties have camelCase naming from REST spec, suppress documents this

* Update 2025-05-01 virtualNetwork.json

* Regenerate vmssNetwork swagger for DDoS custom policy updates

* Scope DCP changes to 2025-07 and revert non-target generated files

* Add back-compat gates for DCP properties across Network and Vmss

* Apply TypeSpec format updates for Network DCP compatibility

* Fix shared/vmss compatibility gates for DCP compile

---------

Co-authored-by: Venkata M <venm@microsoft.com>

* Sync network from main (#42251)

* Replace Network/Common NameSpace (#42225)

* update

* update

* update

* update client.tsp

* format

* replace

* update client.tsp

* add versions in common

* compile

* Add ddosSettingsProperty on loadbalancer's frontendIpConfiguration. Also all list command for DdosCustomPolicy resource (#42054)

* Add tsp changes

* Add swagger changes

* Add examples

* remove supress for casing

* remove missing example

* address comments

* fix avaocado MULTIPLE_API_VERSION rule

* Supress Avacado MULTIPLE_API_VERSION

* Revert "fix avaocado MULTIPLE_API_VERSION rule"

This reverts commit c84ca6f.

* Revert "Supress Avacado MULTIPLE_API_VERSION"

This reverts commit f1f769f.

* addall files generated

* Add missing file

* update examples folder

* fix version

* reset older changes

* remove remaining

* Add version check

* add version check on DCP list and listAll too

* fix tsp validation because of version check on common resource.Moved the check upstream

* use new way

* Update with checks after release rebase

---------

Co-authored-by: Giri Bhatnagar <gibhatna@microsoft.com>

* Add New Resource Network Manager Commit (#42070)

* Add New Resource Network Manager Commit

Port changes from PR #40919 to release-microsoft-network-2025-07-01 branch.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix  references in networkManagerCommit.json

Replace broken ./network.json refs with correct paths:
- SubscriptionIdParameter/ApiVersionParameter -> common-types/v5
- CloudError/ChildResource/ProvisioningState -> ./common.json
- SystemData -> common-types/v5/systemData
- ConfigurationType -> ./common.json

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Merge networkManagerCommit.json into networkManager.json

- Moved commit paths, definitions, and parameters into networkManager.json
- Inlined parameters to match networkManager.json conventions
- Added pattern validation on networkManagerName parameter
- Removed separate networkManagerCommit.json file
- Removed networkManagerCommit.json suppressions from readme.md
- Removed networkManagerCommit.json from readme.md input-file list

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add Commits tag to networkManager.json tags list

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix Avocado and TypeSpec Validation failures

- Revert networkManagerCommit.json merge into networkManager.json
  (networkManager.json is TypeSpec-generated, cannot be manually edited)
- Keep networkManagerCommit.json as a separate swagger file
- Add MULTIPLE_API_VERSION avocado suppression for vmssNetwork.json
- Restore ResourceNameRestriction and SystemDataDefinitionsCommonTypes
  suppressions for networkManagerCommit.json

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add Commit resource via TypeSpec instead of separate swagger

- Created Commit.tsp defining Commit as a child resource of NetworkManager
  with GET, PUT (async), DELETE (async), and List operations
- Added @added(Versions.v2025_07_01) to scope Commit to 2025-07-01 only
- Regenerated networkManager.json with tsp compile (includes Commit CRUD)
- Removed separate networkManagerCommit.json (now generated via TypeSpec)
- Removed networkManagerCommit.json suppressions from readme.md

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Remove MULTIPLE_API_VERSION suppression from readme.md

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Update suppression reasons in Commit.tsp with explicit justifications

Replace generic FIXME placeholders with specific reasons documenting
why ChildResource pattern is used (consistency with all existing
Network Manager child resources like ScopeConnection, AdminRuleCollection,
ConnectivityConfiguration, etc.) rather than ProxyResource<T>.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Address ravimeda's review feedback on Commit resource

- Fix example resource IDs: add leading / to all id fields (EX-RESOURCE-ID)
- Fix nextLink URL: managedNetworks -> networkManagers (EX-PAGINATION)
- Add operationId to all example files for autorest emitter discovery
- Copy examples to TypeSpec examples/2025-07-01/ folder
- Regenerated swagger now includes x-ms-examples for all Commit ops
- Fix forceUpdateTag description to clarify force-update semantics
- Fix list operation description: 'Lists all commits for the specified
  network manager' instead of 'Lists the specified commit'

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Document rationale for omitting PATCH operation on Commits

Commits are immutable deployment records where partial updates are not
semantically meaningful, consistent with other Network Manager child
resources (ScopeConnection, ConnectivityConfiguration, etc.).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix ModelValidation: add 200 response to Commits_Delete example

The generated swagger includes a 200 response code for the delete
operation but the example file only had 202/204. Added 200: {} to
match, consistent with other Network Manager delete examples.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix Avocado, ModelValidation and LintDiff failures

Avocado: Re-add MULTIPLE_API_VERSION suppression for vmssNetwork.json

ModelValidation:
- Fix nextLink URL: replace {baseurl} with https://management.azure.com
- Fix PUT example: rename body param 'parameters' to 'resource'

LintDiff:
- Add @pattern to commitName parameter (ResourceNameRestriction)
- Remove 200 from delete responses (DeleteResponseCodes: LRO delete
  must only have 202, 204 and default)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix nextLink: use relative path instead of absolute URL

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix ModelValidation: use full URI for nextLink, remove 200 from delete example

- nextLink must be a valid URI (relative path fails format validation)
- Delete example had stale 200 response not in swagger

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Run tsp format on Commit.tsp to fix TypeSpec Validation

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix Avocado MULTIPLE_API_VERSION suppression format

Move suppression from 'suppressions' section (LintDiff format) to
'directive' section with 'suppress:' keyword (Avocado format).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix LintDiff: suppress ProvisioningStateMustBeReadOnly for Commit

Add targeted suppressions for 3 new Commit-specific violations only.
provisioningState IS readOnly in CommitProperties definition but the
linter does not follow \ chains to verify in response schemas.
Same pattern exists for all other NM resources (pre-existing).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix broken $ref pointers in networkManager.json (2025-07-01)

Fix 5 unresolvable references in networkManager.json:
- 4x CloudError -> Common.CloudError
- 1x ProvisioningState -> Common.ProvisioningState

These broken refs caused SemanticValidation, LintDiff, and SDK Validation CI failures.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add missing Common import to Commit.tsp

Add import '../Common/main.tsp' and 'using Common' to resolve
unknown identifier errors for ProvisioningState, Features, and CloudError.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add common useDependency 2025-07-01 in VMSS (#42312)

* update

* remove @removed

* Arjun/vna vnet changes 2025 07 01 (#42049)

* Update VNA and VNet properties: add PrivateIPAddressVersion and SummarizedGatewayPrefixes

- bandwidthInGbps: string to float64
- Add privateIPAddressVersion property with VirtualNetworkApplianceIpVersionType enum (IPv4, DualStack)
- Add summarizedGatewayPrefixes on VirtualNetworkPropertiesFormat
- Add versioning decorators for v2025_07_01 API version changes
- Update all VNA example files with new properties

* Update swagger: add privateIPAddressVersion, VirtualNetworkApplianceIpVersionType, summarizedGatewayPrefixes, and fix bandwidthInGbps type

* Fix TypeSpec compilation errors: suppress casing-style and remove Versions ref from Common

* Add @@added versioning for summarizedGatewayPrefixes via augment decorator

Use augment syntax from Network/models.tsp since Versions is not available in Common/main.tsp (shared with Vmss which only has v2018_10_01).

* Align swagger with TypeSpec compiler output

Accept tsp compile generated swagger: move VirtualNetworkApplianceIpVersionType to common.json, add format:double, fix ref path, revert example changes to match generated output.

* Regenerate vmssNetwork swagger from TypeSpec

* Fix lint: update enum descriptions to not match node names

* Fix examples: bandwidthInGbps must be number not string

* Fix source examples: bandwidthInGbps must be number not string

* Address ARM review feedback for VNA VNet changes 2025-07-01

- Fix bandwidthInGbps type versioning: use @typeChangedFrom to keep string
  type in 2025-05-01 and change to float64 only in 2025-07-01
- Revert 2025-05-01 examples to use string value for bandwidthInGbps
- Remove summarizedGatewayPrefixes from 2018-10-01 vmssNetwork.json
  (violates API version immutability)
- Update summarizedGatewayPrefixes description to clarify it is configurable
- Fix FIXME suppression placeholder for privateIPAddressVersion casing

* Fix summarizedGatewayPrefixes leaking into 2018-10-01 Vmss output

Add @@removed decorator in Vmss/back-compatible.tsp to prevent
summarizedGatewayPrefixes from appearing in the 2018-10-01 vmssNetwork.json.
The property is defined in Common/main.tsp (shared across projects) but
should only appear in 2025-07-01+. The @@added gate in the Network project
does not apply during Vmss compilation.

* Fix ambiguous Versions reference in Vmss back-compatible.tsp

Fully qualify as Microsoft.Compute.Versions.v2018_10_01 to resolve
ambiguity between Microsoft.Compute.Versions and Microsoft.Network.Versions.

* Add MULTIPLE_API_VERSION suppression for default tag

The default tag includes 2018-10-01/vmssNetwork.json alongside 2025-07-01
files. This is expected since the Vmss APIs are a separate TypeSpec project
(Microsoft.Compute) with only a 2018-10-01 version.

* Fix MULTIPLE_API_VERSION suppression: use directive/suppress format

The suppressions/code format doesn't work for this rule. Use the
directive/suppress format as done in AlertsManagement Legacy readme.

* undo suppression

* Regenerate swagger JSON files from TypeSpec

* Move @added decorator to Common/main.tsp and remove @@removed from Vmss/back-compatible.tsp per PR #42054 pattern

* remove whitespace

* Users/anjbal/nat64 ts (#42176)

* Nat64 Changes

* Auto generated code

* Changed file

* Description Fix

* NIT Fix

* Auto generate code

* TypeSpec Validation

* Add description

* Description updated

* Add Managed HSM support to Application Gateway for 2025-07-01 (#42137)

* Add Managed HSM support to Application Gateway for 2025-07-01

Add ApplicationGatewayManagedHsm type definition and hsm property
to ApplicationGatewaySslCertificatePropertiesFormat in both TypeSpec
source (models.tsp) and generated JSON (applicationGateway.json).

Original PR: Azure/azure-rest-api-specs-pr#23831

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add @added(Versions.v2025_07_01) decorators to HSM model and property

Mark ApplicationGatewayManagedHsm model and hsm property with version
decorator to properly indicate they are new in the 2025-07-01 API version,
following the same pattern as PR #42054.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix TypeSpec validation: replace @Format with url scalar type

Remove @Format("uri") decorator (forbidden by no-format rule) and use
the built-in url scalar type instead. Also replace boilerplate suppression
justification with a real one.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Regenerate applicationGateway.json from tsp compile

Run tsp compile to regenerate JSON output matching the TypeSpec source.
Fixes TypeSpec Validation CI check.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Srijani Sen <srijanisen@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add DisablePeeringRoute property to RouteTable TypeSpec for API version 2025-07-01 (#42058)

* Add DisablePeeringRoute property to RouteTable TypeSpec (2025-07-01)

* Remove unnecessary TypeSpec.Versioning import from models.tsp

* Retrigger CI checks

* Fix Vmss compilation: use augment decorators for versioning and regenerate vmssNetwork swagger

* Regenerate swagger after merging prerequisite PR #42312

---------

Co-authored-by: Sonal Singh (from Dev Box) <sonalsingh@microsoft.com>

* Add ECMP routing support for Network Route Tables. (typespec update) (#42053)

* NRP ECMP support.

* Adding Examples and AVNM updates.

* Resolved review comments from ravimeda.

* Revert changes to 2018-10-01/vmssNetwork.json to fix lint/breaking-change checks

* Revert "Revert changes to 2018-10-01/vmssNetwork.json to fix lint/breaking-change checks"

This reverts commit 3f0ca7a.

* Fix DescriptionMustNotBeNodeName lint error for None enum values

* Adding Examples and AVNM updates.

* Trigger CI

* Fix duplicate ECMP example reference in virtualNetwork.json

---------

Co-authored-by: nsiddabasapp <nsiddabasapp@microsoft.com>
Co-authored-by: Sonal Singh (from Dev Box) <sonalsingh@microsoft.com>

* Detail level parameter new (#42056)

* Added work necessary for detailLevelParameter

Added work necessary for detailLevel parameter in Get LB call.

* Prettier

* Sku name fix on Scope examples

* Add suppression

* TSP changes

* Suppression and examples

* Compile tsp

* Fix readme.md: remove duplicate tag section and correct suppression placement

* Add MULTIPLE_API_VERSION suppression for pre-existing vmssNetwork.json in default tag

* Address comments

* Remove instructions file

* Readme

* fix: remove where clause from ParametersInPointGet suppression in readme.md

The where clause used single-quoted JSONPath which is non-standard.
Removing the where clause to use a simpler, proven suppression pattern
(similar to DevTestLabs and other services).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix: restore where clause to ParametersInPointGet suppression with correct JSONPath

Two bugs in the original where clause:
1. Single quotes in JSONPath brackets (non-standard, evaluates to nothing)
2. Path ended at .get instead of .get.parameters (rule reports at parameters level)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Swagger changes for afc configuration (#42245)

* Swagger changes for afc control plane

* Add afcControlPlaneConfiguration to Azure Firewall TypeSpec and generated swagger for 2025-07-01

* Renamed the response

* Swap parameter order

* [NSP] ResourceAssociable API - release swagger update (#42403)

* [NSP] ResourceAssociable API - release swagger update

* Resolving Comments

* Remving Custom Name for Enum for SDK

* Removing Custom Property

* Adding Custom Property

* Add new properties to PerimeterAssociableResourceProperties via TypeSpec and regenerate swagger

* TypeSpec Related Changes

* Updating Descriptions

* Updating TSP file to have correct description

---------

Co-authored-by: Chenjie Shi <tadelesh.shi@live.cn>

* Add RoutingConfiguration property for hubBgpConnection and virtualNetworkGatewayConnection (#42409)

* Add RoutingConfiguration support for VirtualNetworkGatewayConnection and HubBgpConnection

* push generated swagger files

---------

Co-authored-by: Ira Ramtirth <irramtir@microsoft.com>

* update the captcha expiration property (#42106)

* update the captcha expiration property

* Regenerate Network swagger from TypeSpec

* Make propagateStaticRoutes read/write (#42616)

Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com>

* Swagger changes for Vwan Express Route Gateway Failover and Insights (#42560)

* swagger changes for vwan express route gateway apis

* fixed errros

* fixed errros

* fixed errros

* fixed errros

* add suppression

* Delete specification/network/resource-manager/Microsoft.Network/Network/sdk-suppressions.yaml

* reverted back compatible.tsp

---------

Co-authored-by: Shubhika Jain <shujai@microsoft.com>
Co-authored-by: judy <1002946066@qq.com>
Co-authored-by: Chenjie Shi <tadelesh.shi@live.cn>
Co-authored-by: Venu Sivanadham <56538710+venu-sivanadham@users.noreply.github.com>

* Connection policy changes (#42745)

Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com>

* Swagger changes for Circuit link failover APIs (#42555) (#42729)

* link fialover swagger

* fixed errors

* added in readme

* add suppression

* update suppression

* updated doc

* reverted back-compatible changes

* Merging Circuit link failover final cp 2 branch with latest pull (#42690)

* Make propagateStaticRoutes read/write (#42616)



* Swagger changes for Vwan Express Route Gateway Failover and Insights (#42560)

* swagger changes for vwan express route gateway apis

* fixed errros

* fixed errros

* fixed errros

* fixed errros

* add suppression

* Delete specification/network/resource-manager/Microsoft.Network/Network/sdk-suppressions.yaml

* reverted back compatible.tsp

---------






---------








* resolved merged conflicts:1 (#42715)



---------

Co-authored-by: Shubhika Jain <shujai@microsoft.com>
Co-authored-by: judy <1002946066@qq.com>
Co-authored-by: Venu Sivanadham <56538710+venu-sivanadham@users.noreply.github.com>
Co-authored-by: Rajkumar Chepala <rchepala+github@microsoft.com>
Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com>
Co-authored-by: Chenjie Shi <tadelesh.shi@live.cn>

* Remove tags from DDoS protection plan properties (#42850)

Co-authored-by: Santosh Lokarapu <v-slokar@microsoft.com>

* Added Private Endpoint Billing Sku Property in 2025-07-01 (#42367) (#42888)

* Added PrivateEndpoints to 2025-07-01

* Added billing sku property to private endpoint

* Update references in PrivateEndpoint to Common file and Update Readme with 2025-07-01 PrivateEndpoint

* Reverted changes- Added BillingSku to PrivateEndpoint resource in VirtualNetwork file

* Restored and Updated/Generated swagger change with TypeSpec

* Removed extra line

* added vmss for typespec validation

* Default description

* Descriptions

* CP Add Microsoft.Network/InterconnectGroups TypeSpec for 2025-07-01 (#42331) (#42933)

* Add Microsoft.Network/InterconnectGroups TypeSpec for 2025-07-01
- Add InterconnectGroup tracked resource with CRUD operations
- Add Subgroup nested resource with Get and List operations
- Add GetNodeAvailability async POST action
- Models aligned with NRP source: InterconnectGroupScope, SubgroupProfile,
  SubgroupProperties (internalSubgroupId),
  InterconnectGroupNodeAvailability, SubgroupNodeAvailabilityEntry

* Refactor Commit to use ProxyResource<T> per review feedback

Switch Commit model from ChildResource to ProxyResource<CommitProperties>
per markcowl's review:
- Remove @Http.Private.includeInapplicableMetadataInPayload (unnecessary
  with ProxyResource)
- Remove explicit systemData property (included by ProxyResource)
- Remove no-private-usage, arm-custom-resource-usage-discourage, and
  composition-over-inheritance suppressions (no longer applicable)
- Use 'is' instead of 'extends' for composition over inheritance

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Revert "Refactor Commit to use ProxyResource<T> per review feedback"

This reverts commit 93949e3.

* Addressing PR comments (#43106)

Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com>

* Apply TypeSpec formatting fixes for Network validation (#43251)

Co-authored-by: Santosh Lokarapu <v-slokar@microsoft.com>

---------

Co-authored-by: Santosh Lokarapu <v-slokar@microsoft.com>
Co-authored-by: venkatasaimaram7 <venkatasaimaram7@gmail.com>
Co-authored-by: Venkata M <venm@microsoft.com>
Co-authored-by: mcgallan <88413158+mcgallan@users.noreply.github.com>
Co-authored-by: Giri Bhatnagar <giri1gb@gmail.com>
Co-authored-by: Giri Bhatnagar <gibhatna@microsoft.com>
Co-authored-by: yanfa317 <53584318+yanfa317@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Arjun Patel <94936045+arjun-d-patel@users.noreply.github.com>
Co-authored-by: anjbal <137822143+anjbal@users.noreply.github.com>
Co-authored-by: srijanee <srijanee.titli@gmail.com>
Co-authored-by: Srijani Sen <srijanisen@microsoft.com>
Co-authored-by: Sonal Singh <sonalsingh+github@microsoft.com>
Co-authored-by: Sonal Singh (from Dev Box) <sonalsingh@microsoft.com>
Co-authored-by: nandakishores <32315808+nandakishores@users.noreply.github.com>
Co-authored-by: nsiddabasapp <nsiddabasapp@microsoft.com>
Co-authored-by: Eugenio Peña García <70240915+EugenioPena@users.noreply.github.com>
Co-authored-by: Sai Sujith Reddy Mankala <samankal@microsoft.com>
Co-authored-by: henumpa <99614325+henumpa@users.noreply.github.com>
Co-authored-by: Chenjie Shi <tadelesh.shi@live.cn>
Co-authored-by: irramtir <irramtir+github@microsoft.com>
Co-authored-by: Ira Ramtirth <irramtir@microsoft.com>
Co-authored-by: Yaniv Sagron <yanivsag@gmail.com>
Co-authored-by: Rajkumar Chepala <rchepala+github@microsoft.com>
Co-authored-by: Rajkumar Chepala <rchepala@microsoft.com>
Co-authored-by: shubhika1795 <32219662+shubhika1795@users.noreply.github.com>
Co-authored-by: Shubhika Jain <shujai@microsoft.com>
Co-authored-by: judy <1002946066@qq.com>
Co-authored-by: Venu Sivanadham <56538710+venu-sivanadham@users.noreply.github.com>
Co-authored-by: chrisbrugal <138532458+chrisbrugal@users.noreply.github.com>
Co-authored-by: jbouzarouata1 <152891406+jbouzarouata1@users.noreply.github.com>
Co-authored-by: Fan Yang (AZURE) <yanfa@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants