Skip to content

[AutoPR @azure-arm-network]-generated-from-SDK Generation - JS-6065631#37842

Draft
azure-sdk wants to merge 7 commits into
mainfrom
sdkauto/@azure-arm-network-6065631
Draft

[AutoPR @azure-arm-network]-generated-from-SDK Generation - JS-6065631#37842
azure-sdk wants to merge 7 commits into
mainfrom
sdkauto/@azure-arm-network-6065631

Conversation

@azure-sdk
Copy link
Copy Markdown
Collaborator

@azure-sdk azure-sdk commented Mar 26, 2026

Configurations: 'specification/network/resource-manager/Microsoft.Network/Network/tspconfig.yaml', API Version: 2025-05-01, SDK Release Type: beta, and CommitSHA: 'a19ce547612341bf0bcd13d73b1cf58b5a9ea7d0' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6065631 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.

…work/Network/tspconfig.yaml', API Version: 2025-05-01, SDK Release Type: stable, and CommitSHA: 'a19ce547612341bf0bcd13d73b1cf58b5a9ea7d0' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6065631 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
@github-actions github-actions Bot added the Mgmt This issue is related to a management-plane library. label Mar 26, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 26, 2026

API Change Check

APIView identified API level changes in this PR and created the following API reviews

@azure/arm-network

@JialinHuang803
Copy link
Copy Markdown
Member

JialinHuang803 commented Mar 26, 2026

Breaking Change Analysis: @azure/arm-network v37.0.0-beta.1

Old SDK (main) New SDK (PR)
Generator Swagger / AutoRest TypeSpec / emitter
API Version 2025-05-01 2025-05-01
Package Version 36.0.0 37.0.0-beta.1

Type 1: API Version Upgrade -- 0 items

No Type 1 breaking changes. API version is the same (2025-05-01).


Type 2: TypeSpec / Emitter Migration -- 83 items

# Breaking Change Count Detail Accepted ✅ / ❌
1 Discriminator type changes (extensible enums) 4 Inline literal unions replaced by named union types from TypeSpec. See Root Cause Table below. (Pattern 3)
2 Union type alias changes 4 Caused by discriminator changes in #1. Ordering/type of discriminator property changed. (Pattern 4)
3 Operation signature changes (discriminator-caused) 5 Operations returning/accepting models with changed discriminator types. See Root Cause Table. (Pattern 1)
4 Operation signature changes (void return) 14 Old SDK returned header-only wrapper response types (e.g., AzureFirewallsPacketCaptureResponse = AzureFirewallsPacketCaptureHeaders). New SDK returns void. (Pattern 1)
5 Operation signature changes (string return -- unwrapped) 15 Old SDK wrapped LRO result in { body: string } response types. New SDK unwraps to direct string. (Pattern 1)
6 Removed List/Collection interfaces 10 List wrapper types internalized as _XxxList (unexported). Operations return PagedAsyncIterableIterator<T> directly. (Pattern 2)
7 Removed base resource interface (TrackedResource) 1 TypeSpec uses standard ARM types from @azure-tools/typespec-azure-resource-manager. (Pattern 5)
8 value now required on list results 10 TypeSpec defines value as required in list result types (using the Page model from typesspec-azure-core). Service always returns value, so no practical impact.
9 Models/types not exported by emitter 16 Includes 4 interfaces, 6 type aliases, 6 enums. These models are not reachable by operations, so emitter does not export them (tree-shaking or internal-only). (Pattern 8)
10 OptionalParams interfaces removed 4 Old SDK had empty OptionalParams interfaces for paginated operations. Emitter folds or removes them. (Pattern 9)

Unified Root Cause Table (Discriminator -> Union Alias -> Operation Signatures)

Root Cause (Discriminator Change) Union Alias Affected Operation Signatures Affected
FirewallPolicyRule.ruleType: "ApplicationRule" | "NatRule" | "NetworkRule" -> FirewallPolicyRuleType FirewallPolicyRuleUnion FirewallPolicyRuleCollectionGroupDrafts.createOrUpdate, .get; FirewallPolicyRuleCollectionGroups.beginCreateOrUpdate, .beginCreateOrUpdateAndWait, .get
FirewallPolicyRuleCollection.ruleCollectionType: "FirewallPolicyNatRuleCollection" | "FirewallPolicyFilterRuleCollection" -> FirewallPolicyRuleCollectionType FirewallPolicyRuleCollectionUnion (same 5 operations as above -- models are nested)
ActiveBaseSecurityAdminRule.kind: "Custom" | "Default" -> EffectiveAdminRuleKind ActiveBaseSecurityAdminRuleUnion (none directly)
EffectiveBaseSecurityAdminRule.kind: "Custom" | "Default" -> EffectiveAdminRuleKind EffectiveBaseSecurityAdminRuleUnion (none directly)

TypeSpec source: models.tsp lines 1813 (FirewallPolicyRuleCollectionType), 2287 (EffectiveAdminRuleKind), 5664 (FirewallPolicyRuleType)


Detailed Breakdown

Row 1: Discriminator Type Changes (4 items, Pattern 3)
  • ActiveBaseSecurityAdminRule.kind: "Custom" | "Default" -> EffectiveAdminRuleKind
  • EffectiveBaseSecurityAdminRule.kind: "Custom" | "Default" -> EffectiveAdminRuleKind
  • FirewallPolicyRule.ruleType: "ApplicationRule" | "NatRule" | "NetworkRule" -> FirewallPolicyRuleType
  • FirewallPolicyRuleCollection.ruleCollectionType: "FirewallPolicyNatRuleCollection" | "FirewallPolicyFilterRuleCollection" -> FirewallPolicyRuleCollectionType
Row 2: Union Type Alias Changes (4 items, Pattern 4)
  • ActiveBaseSecurityAdminRuleUnion changed (caused by kind discriminator change)
  • EffectiveBaseSecurityAdminRuleUnion changed (caused by kind discriminator change)
  • FirewallPolicyRuleCollectionUnion changed (caused by ruleCollectionType discriminator change)
  • FirewallPolicyRuleUnion changed (caused by ruleType discriminator change)
Row 3: Operation Signature Changes -- Discriminator-caused (5 items, Pattern 1)
  • FirewallPolicyRuleCollectionGroupDrafts.createOrUpdate
  • FirewallPolicyRuleCollectionGroupDrafts.get
  • FirewallPolicyRuleCollectionGroups.beginCreateOrUpdate
  • FirewallPolicyRuleCollectionGroups.beginCreateOrUpdateAndWait
  • FirewallPolicyRuleCollectionGroups.get
Row 4: Operation Signature Changes -- Void Return (14 items, Pattern 1)

Old SDK returned header-only wrapper response types (e.g., AzureFirewallsPacketCaptureResponse = AzureFirewallsPacketCaptureHeaders). New SDK returns void because TypeSpec LRO templates model these as void-returning operations.

  • AzureFirewalls.beginPacketCaptureAndWait (AzureFirewallsPacketCaptureResponse -> void)
  • FirewallPolicyDeployments.beginDeployAndWait (FirewallPolicyDeploymentsDeployResponse -> void)
  • IpamPools.beginDeleteAndWait
  • ReachabilityAnalysisRuns.beginDeleteAndWait
  • ServiceGateways.beginDeleteAndWait
  • ServiceGateways.beginUpdateAddressLocationsAndWait (ServiceGatewaysUpdateAddressLocationsResponse -> void)
  • ServiceGateways.beginUpdateServicesAndWait (ServiceGatewaysUpdateServicesResponse -> void)
  • StaticCidrs.beginDeleteAndWait
  • VerifierWorkspaces.beginDeleteAndWait
  • VirtualNetworkAppliances.beginDeleteAndWait
  • VirtualNetworkGateways.beginInvokeAbortMigrationAndWait (VNG InvokeAbortMigrationResponse -> void)
  • VirtualNetworkGateways.beginInvokeCommitMigrationAndWait (VNG InvokeCommitMigrationResponse -> void)
  • VirtualNetworkGateways.beginInvokeExecuteMigrationAndWait (VNG InvokeExecuteMigrationResponse -> void)
  • VirtualNetworkGateways.beginInvokePrepareMigrationAndWait (VNG InvokePrepareMigrationResponse -> void)
Row 5: Operation Signature Changes -- String Return / Unwrapped (15 items, Pattern 1)

Old SDK wrapped LRO result in response types like { body: string } (e.g., VirtualNetworkGatewaysStartPacketCaptureResponse = { body: string }). New SDK unwraps to return string directly.

  • VirtualNetworkGatewayConnections.beginGetIkeSasAndWait (VNG ConnectionsGetIkeSasResponse -> string)
  • VirtualNetworkGatewayConnections.beginStartPacketCaptureAndWait (VNG ConnectionsStartPacketCaptureResponse -> string)
  • VirtualNetworkGatewayConnections.beginStopPacketCaptureAndWait (VNG ConnectionsStopPacketCaptureResponse -> string)
  • VirtualNetworkGateways.beginGeneratevpnclientpackageAndWait (VNG GeneratevpnclientpackageResponse -> string)
  • VirtualNetworkGateways.beginGenerateVpnProfileAndWait (VNG GenerateVpnProfileResponse -> string)
  • VirtualNetworkGateways.beginGetVpnProfilePackageUrlAndWait (VNG GetVpnProfilePackageUrlResponse -> string)
  • VirtualNetworkGateways.beginStartExpressRouteSiteFailoverSimulationAndWait (VNG StartExpressRouteFailoverResponse -> string)
  • VirtualNetworkGateways.beginStartPacketCaptureAndWait (VNG StartPacketCaptureResponse -> string)
  • VirtualNetworkGateways.beginStopExpressRouteSiteFailoverSimulationAndWait (VNG StopExpressRouteFailoverResponse -> string)
  • VirtualNetworkGateways.beginStopPacketCaptureAndWait (VNG StopPacketCaptureResponse -> string)
  • VpnConnections.beginStartPacketCaptureAndWait (VpnConnectionsStartPacketCaptureResponse -> string)
  • VpnConnections.beginStopPacketCaptureAndWait (VpnConnectionsStopPacketCaptureResponse -> string)
  • VpnGateways.beginStartPacketCaptureAndWait (VpnGatewaysStartPacketCaptureResponse -> string)
  • VpnGateways.beginStopPacketCaptureAndWait (VpnGatewaysStopPacketCaptureResponse -> string)
  • VpnLinkConnections.beginGetIkeSasAndWait (VpnLinkConnectionsGetIkeSasResponse -> string)
Row 6: Removed List/Collection Interfaces (10 items, Pattern 2)
  • ApplicationGatewayAvailableSslPredefinedPolicies
  • ApplicationGatewayWafDynamicManifestResultList
  • ConnectionSharedKeyResultList
  • ExpressRouteCrossConnectionPeeringList
  • IpamPoolList
  • ListVirtualHubBgpConnectionResults
  • ListVirtualHubIpConfigurationResults
  • NetworkVirtualApplianceConnectionList
  • PoolAssociationList
  • StaticCidrList
Row 7: Base Resource Interface Removed (1 item, Pattern 5)
  • TrackedResource (old: extends SecurityPerimeterResource with tags and location; new: uses standard ARM TrackedResource from @azure-tools/typespec-azure-resource-manager)
Row 8: value Now Required (10 items)
  • EffectiveNetworkSecurityGroupListResult.value
  • EffectiveRouteListResult.value
  • ExpressRouteCircuitsArpTableListResult.value
  • ExpressRouteCircuitsRoutesTableListResult.value
  • ExpressRouteCircuitsRoutesTableSummaryListResult.value
  • ExpressRouteCrossConnectionsRoutesTableSummaryListResult.value
  • ExpressRouteProviderPortListResult.value
  • RadiusAuthServerListResult.value
  • ResourceNavigationLinksListResult.value
  • ServiceAssociationLinksListResult.value
Row 9: Models/Types Not Exported by Emitter (16 items, Pattern 8)

Removed Interfaces (4):

  • ConnectionStateSnapshot (defined in TypeSpec models.tsp:25336 but not reachable from exported operations)
  • PatchRouteFilter (back-compatible.tsp:281 has @@legacy.flattenProperty; orphaned -- not used by any operation)
  • PatchRouteFilterRule (back-compatible.tsp:278 has @@legacy.flattenProperty; orphaned -- not used by any operation)
  • VpnSiteId (defined in TypeSpec models.tsp:25481 but not exported)

Removed Type Aliases (6):

  • ConnectionMonitorSourceStatus (TypeSpec models.tsp:5841)
  • ConnectionState (TypeSpec models.tsp:5797)
  • EvaluationState (TypeSpec models.tsp:5819)
  • NetworkOperationStatus (TypeSpec models.tsp:5753)
  • HubVirtualNetworkConnectionStatus (TypeSpec models.tsp:5890)
  • TunnelConnectionStatus (TypeSpec models.tsp:5863)

Removed Enums (6):

  • KnownConnectionMonitorSourceStatus
  • KnownConnectionState
  • KnownEvaluationState
  • KnownNetworkOperationStatus
  • KnownHubVirtualNetworkConnectionStatus
  • KnownTunnelConnectionStatus

Note: These unions ARE defined in TypeSpec but the emitter may not export them because they are only referenced by models not reachable from operations (e.g., ConnectionStateSnapshot uses ConnectionState and EvaluationState).

Row 10: OptionalParams Interfaces Removed (4 items, Pattern 9)
  • ApplicationGatewayWafDynamicManifestsGetOptionalParams
  • ServiceGatewaysGetAddressLocationsOptionalParams
  • ServiceGatewaysGetServicesOptionalParams
  • VpnLinkConnectionsGetAllSharedKeysOptionalParams

All were empty interfaces extending coreClient.OperationOptions with no additional properties. Emitter may inline or rename them.


Total: 0 (Type 1) + 83 (Type 2) = 83 breaking changes

All breaking changes are caused by the TypeSpec/emitter migration. No API version upgrade impact since both old and new SDK target API version 2025-05-01.

…work/Network/tspconfig.yaml', API Version: 2025-05-01, SDK Release Type: stable, and CommitSHA: '1bae4f04fa0234d80f65b580ac33f139fd7c07f3' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6066053 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Found 2 issues in this PR (@azure/arm-network 37.0.0, stable):

  1. Tool issue (1): package.json contains "apiRefLink" pointing to the preview docs URL (?view=azure-node-preview) despite this being a stable release. This is likely a generation-tool bug and should be fixed and reported upstream.
  2. Design concern (1): The previous stable version 36.0.0 was released only ~6 weeks ago (2026-02-11). Frequent major-version bumps within a 6-month window are not recommended — please confirm with the team whether the timing is justified.

No API naming (_N suffix, AutoGenerated, _ prefix), type safety (unknown in public models), or export (ae-forgotten-export) issues were found. Version numbers are consistent across package.json, CHANGELOG.md, and src/api/networkManagementContext.ts (37.0.0). No alpha versions detected.

📊 Structured Report
{"agent":"mgmt-reviewer","pr":37842,"summary":"issues_found","findings":[{"file":"sdk/network/arm-network/package.json","line":193,"issueType":"tool","category":"apiRefLink preview URL for stable release","description":"apiRefLink uses ?view=azure-node-preview but package version is 37.0.0 (stable). Should use ?view=azure-node-latest."},{"file":"sdk/network/arm-network/CHANGELOG.md","line":3,"issueType":"design","category":"frequent major releases","description":"36.0.0 was released 2026-02-11 (~6 weeks ago). Two major releases within 6 months is flagged for discussion."}]}

Benchmarked by Management SDK PR Review

"azure"
],
"disableDocsMs": true,
"apiRefLink": "https://learn.microsoft.com/javascript/api/@azure/arm-network?view=azure-node-preview"
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.

🔴 Tool Issuepackage.json:193
`"apiRefLink": "(learn.microsoft.com/redacted)

This package is being released as a stable version (37.0.0), but the apiRefLink in //sampleConfiguration points to the preview docs URL (?view=azure-node-preview). This suggests a tooling bug in the generation pipeline that generates package.json.

Fix: Change the apiRefLink value to the stable docs URL:

"apiRefLink": "(learn.microsoft.com/redacted)

Please also report this issue in the generation tool repository.

Copy link
Copy Markdown
Member

@MaryGao MaryGao Mar 26, 2026

Choose a reason for hiding this comment

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

@skywing918 and @kazrael2119 Could you confirm if this is a codegen bug?

Copy link
Copy Markdown
Member

@kazrael2119 kazrael2119 Mar 30, 2026

Choose a reason for hiding this comment

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

I think we should support this update in changelog-tool as before we run changelog-tool, the package version should always use 1.0.0-beta.1(this is the default value from codegen). We should dynamicly update this link after changelog-tool completes the version calculation

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Comment thread sdk/network/arm-network/CHANGELOG.md Outdated
@@ -1,5 +1,591 @@
# Release History

## 37.0.0 (2026-03-26)
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.

🔴 Design ConcernCHANGELOG.md:3
## 37.0.0 (2026-03-26)

The previous stable version 36.0.0 was released on 2026-02-11, which is only ~6 weeks ago. This is well within the 6-month window where frequent major-version breakages are flagged. Two consecutive major releases in such a short window can disrupt customers who are still adopting the previous version.

Fix: Please discuss with the service/spec team whether these breaking changes are urgent enough to justify a new major release at this cadence, or whether they could be batched with the next planned release.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@JialinHuang803 Have we got the PM's approval for this breaking release? Generally it's not recommanded to release two breakings wihtin 6 months.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We don't plan to release this package now. This PR is generated for breaking change analysis.

…work/Network/tspconfig.yaml', API Version: 2025-05-01, SDK Release Type: stable, and CommitSHA: '02f52b1c1332822011ea514b1aba498bf27d7f7b' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6071639 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
azure-sdk and others added 4 commits March 31, 2026 04:22
…work/Network/tspconfig.yaml', API Version: 2025-05-01, SDK Release Type: beta, and CommitSHA: 'aa591176e14ed29f96ebf1e3899e4356df7f13dd' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6084390 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
…work/Network/tspconfig.yaml', API Version: 2025-05-01, SDK Release Type: beta, and CommitSHA: 'b684aff3319ffa5784a8b8d19d6af5adf168a4bb' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6085746 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
…network-6065631

# Conflicts:
#	pnpm-lock.yaml
…work/Network/tspconfig.yaml', API Version: 2025-05-01, SDK Release Type: beta, and CommitSHA: 'a83147fe12aece4ded0bd96be212e5242e087cb9' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6086390 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
@JialinHuang803
Copy link
Copy Markdown
Member

JialinHuang803 commented Mar 31, 2026

Features Added Analysis: @azure/arm-network v37.0.0-beta.1

All 495 features are TypeSpec/emitter migration artifacts. None represent genuinely new API capabilities -- the API version is the same (2025-05-01).

# Category Count Root Cause
1 New-style LRO operations (no begin prefix) 285 TypeSpec emitter generates new primary LRO methods using PollerLike (e.g., delete(), createOrUpdate()). Old begin*/begin*AndWait methods are kept as @deprecated.
2 PropertiesFormat/Properties interfaces 184 Old SDK flattened properties sub-bags into parent models. New emitter exports the inner XxxPropertiesFormat interfaces as standalone types. They are exported but not referenced by any operation or model.
3 Base resource model types 10 New ARM resource base types from the TypeSpec emitter (TrackedResourceWithEtag, ProxyResourceWithReadOnlyID, WritableResource, etc.). Replace old TrackedResource/SubResource.
4 Renamed OptionalParams interfaces 4 Old operations were Get-style (e.g., ServiceGatewaysGetAddressLocations), new are List-style (e.g., ServiceGatewaysListAddressLocations). The old interfaces appear as "Removed" in breaking changes.
5 Paging/Polling utility types 4 PagedAsyncIterableIterator, PageSettings, SimplePollerLike, RestorePollerOptions -- re-exported from core packages as named interfaces.
6 Renamed type aliases + enums 4 CreatedByType -> NetworkManagementClientCreatedByType (prefix added to avoid collision). New AzureSupportedClouds type.
7 Other interfaces 4 DefaultRuleSetPropertyFormat (used by a model), plus 3 exported but unreferenced: ApplicationGatewayWafDynamicManifestPropertiesResult, IpamPoolPrefixAllocationPool, ResourceNavigationLinkFormat.

Row 1: New-style LRO Operations (285 items)

TypeSpec emitter generates new primary LRO methods without the begin prefix, using PollerLike instead of SimplePollerLike. The old begin*/begin*AndWait methods are retained as @deprecated for backward compatibility.

Example:

  • OLD: beginDelete() -> SimplePollerLike, beginDeleteAndWait() -> Promise<void>
  • NEW: delete() -> PollerLike (new primary method)

Top method names: delete (99), createOrUpdate (77), updateTags (7), startPacketCapture (4), stopPacketCapture (4), plus 83 other unique LRO method names across 114 operation groups.

Row 2: PropertiesFormat/Properties Interfaces (184 items)

Old SDK flattened properties sub-bags into parent models (via @@Legacy.flattenProperty in back-compatible.tsp). The new emitter still flattens properties into parent models, but also exports the inner XxxPropertiesFormat/XxxProperties interfaces as standalone types.

These 184 interfaces are exported but not referenced by any operation signature or other model in the API surface -- they are unreachable from the type graph.

Examples: AdminPropertiesFormat, ApplicationGatewayPropertiesFormat, SubnetPropertiesFormat, VirtualNetworkGatewayPropertiesFormat, etc.

Row 3: Base Resource Model Types (10 items)
  • ProxyResourceWithReadOnlyID
  • ProxyResourceWithSettableId
  • ReadOnlySubResourceModel
  • SecurityPerimeterTrackedResource
  • SubResourceModel
  • TrackedResourceWithEtag
  • TrackedResourceWithOptionalLocation
  • TrackedResourceWithSettableIdOptionalLocation
  • TrackedResourceWithSettableName
  • WritableResource
Row 4: Renamed OptionalParams Interfaces (4 items)

Paired with the 4 "Removed Interface" entries in breaking changes (Row 10). The operations were renamed from Get-style to List-style:

  • ApplicationGatewayWafDynamicManifestsGetOptionalParams -> ApplicationGatewayWafDynamicManifestsListOptionalParams
  • ServiceGatewaysGetAddressLocationsOptionalParams -> ServiceGatewaysListAddressLocationsOptionalParams
  • ServiceGatewaysGetServicesOptionalParams -> ServiceGatewaysListServicesOptionalParams
  • VpnLinkConnectionsGetAllSharedKeysOptionalParams -> VpnLinkConnectionsListAllSharedKeysOptionalParams
Row 5: Paging/Polling Utility Types (4 items)
  • PagedAsyncIterableIterator
  • PageSettings
  • SimplePollerLike
  • RestorePollerOptions

Re-exported from core packages as named interfaces in the package API surface.

Row 6: Renamed Type Aliases + Enums (4 items)
  • CreatedByType -> NetworkManagementClientCreatedByType (prefix added to avoid naming collision)
  • KnownCreatedByType -> NetworkManagementClientKnownCreatedByType
  • AzureSupportedClouds (new, type alias for ${AzureClouds})
  • AzureClouds (new enum)
Row 7: Other Interfaces (4 items)
  • DefaultRuleSetPropertyFormat -- referenced by defaultRuleSet?: DefaultRuleSetPropertyFormat in a model
  • ApplicationGatewayWafDynamicManifestPropertiesResult -- exported but unreferenced
  • IpamPoolPrefixAllocationPool -- exported but unreferenced
  • ResourceNavigationLinkFormat -- exported but unreferenced

Total: 495 features added (all TypeSpec/emitter migration artifacts)

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 5, 2026

Hi @azure-sdk. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

@github-actions github-actions Bot added the no-recent-activity There has been no recent activity on this issue. label Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Mgmt This issue is related to a management-plane library. mgmt-review-needed no-recent-activity There has been no recent activity on this issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants