Azure .NET Mgmt SDK PR Review

Review Azure SDK for .NET management library pull requests against the official API review guidelines.

Instructions

When asked to review an Azure SDK .NET management-plane library PR (packages Azure.ResourceManager and Azure.ResourceManager.*):

1. Fetch PR details and diff using GitHub MCP tools
2. Examine API surface files (api/*.cs) for public API
3. Check Generated models and resources in src/Generated/
4. Review TypeSpec customizations (e.g., client.tsp, tspconfig.yaml)
5. Add review comments directly to the PR using GitHub MCP tools

Review Checklist

Naming – Avoid These Suffixes

Resource Naming

• Remove “Resource” suffix if remaining noun is still descriptive (e.g., VirtualMachine not VirtualMachineResource)
• Keep “Resource” if removing makes it non-descriptive (e.g., GenericResource stays)
• For models: append “Data” suffix if inherits ResourceData/TrackedResourceData, otherwise “Info”

Operation Body Parameters

• PATCH operation body: Must be named [Model]Patch
• PUT/POST operation body: Must be named [Model]Content or [Model]Data

Property Naming

• Boolean properties: Must start with verb prefix: Is, Can, Has
• DateTimeOffset properties: Should end with On (e.g., CreatedOn, StartOn, EndOn)
• Interval/Duration (integer): Include units in name (e.g., MonitoringIntervalInSeconds)
• TTL properties: Rename to TimeToLiveIn<Unit>

Acronyms

• Use PascalCase (capitalize first letter only): Aes, Tcp, Http
• 2-letter acronyms: uppercase if standalone (IO), except Id, Vm
• Expand acronyms if not clearly explained in first page of search results with context

Enums

• Use singular type name (not plural) unless bit flags
• Numeric version enums should use underscore: Tls1_0, Ver5_6

Type Formatting

The following table applies to the generated C# API surface (public types/properties in api/*.cs).

For TypeSpec, UUID-valued properties should use the uuid scalar and map to Guid in the generated .NET SDK.

Duration/Interval Format

• ISO 8601 duration (P1DT2H59M59S): use duration scalar in TypeSpec
• ISO 8601 constant (2.2:59:59.5000000): use @encode(DurationConstant) in TypeSpec

CheckNameAvailability Operation

• Method: Check[Resource/RP name]NameAvailability
• Parameter/Response model: [Resource/RP name]NameAvailabilityXXX
• Unavailable reason enum: [Resource/RP name]NameUnavailableReason

Versioning

• Management SDK packages follow a unified versioning strategy. No individual package is allowed to bump its major version unless a major version bump decision has been explicitly made by the .NET architects for all mgmt packages.
• If a PR bumps the major version (e.g., from 1.x to 2.0.0) due to breaking changes, flag this as a Must Fix: “You must not bump the major version without the .NET architects’ explicit requirement. Even with breaking changes, mgmt packages must stay on the current major version unless a coordinated major bump is in progress.”
• When the new API version introduces breaking changes (e.g., removed properties, renamed types), the SDK must mitigate them at the API surface level so there are no breaking changes to customers. Use customization code via partial classes and generator features (e.g., rename-mapping, custom properties, shim methods) to preserve backward compatibility. The goal is to avoid breaking changes entirely so a major version bump is not needed.

Other API Rules

• PUT/PATCH optional body parameters should be changed to required
• Discriminator models should make base model abstract
• Remove all ListOperations methods (SDK exposes operations via public APIs)

Output Format

1. Summarize what passes review
2. For each issue found, add a review comment directly to the PR on the relevant file and line using GitHub MCP tools
3. Provide a final summary of all comments added