[AutoPR azure-resourcemanager-network]-generated-from-SDK Generation - Java-6702249

[azure-sdk-automation]

Configurations: 'specification/network/resource-manager/Microsoft.Network/Network/tspconfig.yaml', API Version: 2025-09-01, SDK Release Type: stable, and CommitSHA: 'bd92126f09e7e3caa74f10fa1c944d1e451813ac' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6702249 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. Release plan link: https://azsdk-releaseplan-dashboard-hveph5aqhhcfhtgu.westus-01.azurewebsites.net/?releaseplan=36026 Submitted by: v-slokar@microsoft.com

[Copilot]

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
35 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[github-actions]

Automated management AutoPR review

• Head SHA: f799eab
• Package: azure-resourcemanager-network 2.60.0
• Release type: stable
• API version: 2025-09-01, 2018-10-01
• CHANGELOG: 2.60.0 (2026-08-14)
• Java changes reviewed: 18 added and 78 modified non-generated Java files in sdk/network/azure-resourcemanager-network
• Breaking changes: none
• Decision: no high-confidence concerns

Informational

• MGMT-API-VERSION New — sdk/network/azure-resourcemanager-network/CHANGELOG.md, release 2.60.0 (2026-08-14), records effective API versions 2025-09-01 and 2018-10-01.

Automated management AutoPR review by Management AutoPR Review: https://github.com/Azure/azure-sdk-for-java/actions/runs/31770524298. Advisory only.

[Weidong Xu (weidongxu-microsoft)]

The generated stable release changes the public contract of the existing ServiceGatewaysClient operations updateAddressLocations and updateServices compared with released version 2.59.1:

• The beginUpdateAddressLocations* and beginUpdateServices* LRO methods are removed.
• Existing methods change from void / Mono<Void> / Response<Flux<ByteBuffer>> to ServiceGatewayActionOkResponseBodyInner response types.
• The CHANGELOG does not document these breaking changes.

This looks like an LRO/response-model change originating from the specification. Could you please confirm whether the operations are intended to change from long-running to synchronous and address compatibility for this stable release?

The duplicate AutoPR has equivalent generated code; the only difference is ordering of three CHANGELOG bullet pairs.

[Weidong Xu (weidongxu-microsoft)]

Why this change? The API was LRO, but now change to simple operation?

[Weidong Xu (weidongxu-microsoft)]

#50141 (comment)

[Weidong Xu (weidongxu-microsoft)]

The LRO-to-synchronous change is intentional and originates from Azure/azure-rest-api-specs#44745.

That PR confirms UpdateSgwLocationAddress and UpdateSgwServices return immediately rather than behaving as LROs. The versioned TypeSpec preserves the LRO shape for older API versions and introduces synchronous operations for 2025-09-01:

https://github.com/Azure/azure-rest-api-specs/blob/bd92126f09e7e3caa74f10fa1c944d1e451813ac/specification/network/resource-manager/Microsoft.Network/Network/Network/ServiceGateway.tsp#L128-L196

Given that service/spec context, the generated API change is accepted.