Typical reason is that the tspconfig.yaml in PR configures a new Java SDK. Hence we cannot compare it with existing SDK (neither apiview nor changelog).

We had to create the apiview revision that 1. before the migration; 2. after the migration, and compare them.

1. create a folder in SDK repo, e.g. sdk/alertsmanagement/azure-resourcemanager-alertprocessingrules
2. in this folder, run autorest, target azure-rest-api-specs main branch

Verify whether the change is from service.

Here, before https://github.com/Azure/azure-rest-api-specs/blob/main/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2024-04-01/mfe.json#L6341

• Project is Maven.
• Java code is on JDK 8 or above.

It is recommended to use azure-sdk-bom (version higher than 1.3.0).

The intention is to investigate whether including the TypeSpec authoring chatbot MCP in the Azure/azure-rest-api-specs repository can help GitHub Copilot better handle user issues and PR reviews.

One champion scenario I'd imagine would be:

Issue by user with description like below:

1. Add preview api-version 2025-09-01 to RP <resource-provider>
2. Add resource <resource> with path <route>, including standard CRUD operations on this resource

Follow up on https://gist.github.com/weidongxu-microsoft/fa420c35cf0611a62a8d155771dd3425

With @armRenameListByOperation solved, we can put multiple List operation into same Interface.

TypeSpec dev advises against this approach.

TCGC, by default, groups operations via TypeSpec Interfaces.

If @operationGroup is specified in client.tsp, it would group operations from Interfaces with @operationGroup in client.tsp instead.

Swagger in Management usually groups many different resources in a single resource group, via "operationId".

Related issue:

• Azure/cadl-ranch#487
• microsoft/typespec#2477

PR

• Azure/azure-rest-api-specs#26359 (only a draft)

DevBox resource model is

Generate client method signature which follow the serivce operation signature.

Different language may have different interpretation of the signature, based on best practise of that language.

Model ClientOptions

@resource("resource-collection")

Information and runtime behavior of the new design can be found at cadl-ranch PR

Major difference in PUT.

1. Response of the PUT is the Resource object, not the OperationStatus object.
2. The last GET on Resource URL preferred to be omitted. The Resource object from the PUT is already the final result.

Major difference in POST.