[Mgmt] Azure.ResourceManager.Compute: Migrate to TypeSpec

[ArcturusZhang]

fixes #55101

Summary

Migrates Azure.ResourceManager.Compute from AutoRest/Swagger generation to TypeSpec-based management-plane generation.

Dependencies

Spec PR

• Add C# client customizations for Compute TypeSpec migration azure-rest-api-specs#41351 — C# client customizations for Compute.
• The SDK currently pins tsp-location.yaml to ArcturusZhang/azure-rest-api-specs commit f15d189e353770158306aab055cc9ef16553fd03 under specification/compute/resource-manager/Microsoft.Compute/Compute.

Generator fix PRs separated from this branch

• [Mgmt Generator] Use per-client API version instead of global DefaultApiVersion #57021 — DefaultApiVersion per-client fix
• [Mgmt Generator] Fix OData parameter name issues #57049 — Duplicate key + OData dollar parameter name fixes
• [Mgmt Emitter] Fix empty client apiVersions for multi-service clients #57160 — Fix empty client apiVersions for multi-service clients
• [Mgmt Generator] Unify scope info as ArmScopeInfo, add scope parameter for extension non-resource methods #58291 — Unify scope info as ArmScopeInfo, add scope parameter for extension non-resource methods
• [Mgmt Generator] Flatten required value-type from optional parent as Nullable<T> #58290 — Flatten required value-type from optional parent as Nullable
• [Mgmt Generator] Use CrossLanguageDefinitionId for ArrayResponse CollectionResult class names #58793 — Use CrossLanguageDefinitionId for ArrayResponse CollectionResult class names
• [mgmt-generator] Add disable-safe-flatten clientOption opt-out (fixes #58066) #58944 — Add disable-safe-flatten clientOption opt-out (fixes [Mgmt Generator] Add option to disable safe-flatten per property/type #58066, a Compute-driven flattening regression)
• Mgmt generator: emit a GetAll overload per List operation for tuple resources #58749 — Mgmt generator: emit a GetAll overload per List operation for tuple resources

Related issues

• [Mgmt Generator] DefaultApiVersion crashes on multi-service client (Compute migration blocked) #57006 — DefaultApiVersion bug for multi-service clients
• [Mgmt Generator] Add option to disable safe-flatten per property/type #58066 — safe-flatten opt-out request
• Compute migration: AvailabilitySet PlacementGroupId playback mismatch for PPG removal #59920 — Track AvailabilitySetOperationsTests.PlacementGroupId playback/serialization mismatch

Changes

• Replaced AutoRest generation with TypeSpec-based generation and updated metadata.json / tsp-location.yaml.
• Refreshed generated code, public API baselines, samples/snippets, and test recordings needed for the migration branch.
• Added SDK customizations to preserve shipped Compute API shape where TypeSpec generation differs, including:
  • CloudService unsupported-operation compatibility surface.
  • Gallery/community/shared gallery namespace and resource-shape compatibility.
  • Resource-reference compatibility shims for SubResource / WritableSubResource-based APIs.
  • Conditional request compatibility shims for legacy ifMatch / ifNoneMatch string parameters while exposing new MatchConditions overloads.
  • Model/property naming compatibility such as gallery IsRestoreEnabled, shared gallery Identifier, and VMSS extension name helper suppression.
• Cleaned up redundant migration code after regeneration proved it unnecessary:
  • Removed ArmComputeModelFactory custom partial; generated factory now covers the needed overloads.
  • Removed SubResourceCompatibilityExtensions by inlining remaining read-only conversions.
  • Converted unsafe mutable list compatibility properties to obsolete/hidden redirecting shims.

Recent cleanup and CI fixes

• Restored GalleryImageVersionPatch consistency: generated IsRestoreEnabled stays public, while old Restore is an obsolete/hidden compatibility shim redirecting to it.
• Simplified legacy conditional request shims by making ifMatch required and ifNoneMatch optional, avoiding ambiguous common calls without extra no-token overloads.
• Kept CodeGenSerialization hooks for VM identity serialization, but removed the explicit wire-name argument after local regeneration/build confirmed the pinned generator handles hook-only attributes.
• Updated generated samples to avoid obsolete compatibility properties that fail CI under warnings-as-errors.
• Updated tsp-location.yaml to a newer spec customization commit and regenerated.

Validation

Local validation completed on the latest branch head d26121636c5:

• dotnet build /t:GenerateCode for Azure.ResourceManager.Compute using the local Compute TypeSpec spec directory.
• eng/scripts/Export-API.ps1 compute.
• dotnet build sdk/compute/Azure.ResourceManager.Compute/tests/Azure.ResourceManager.Compute.Tests.csproj --no-restore.

Current status

• Latest SDK branch head: d26121636c5.
• SDK CI has been retriggered on the latest head.
• The linked spec PR is still being validated separately; its latest follow-up only adjusts Avocado suppression formatting.

Known follow-ups

• CreateResourceIdentifier static factories on GalleryInVmAccessControlProfile[Version]Resource still use uppercase inVMAccessControlProfileName / inVMAccessControlProfileVersionName parameter names. Renaming the spec property would also surface an unacceptable public Name property on the corresponding data model, so this likely needs a generator-level fix.
• Some playback recordings were updated for generated request payload changes, but additional live/recorded test review may still be needed if CI exposes new recording mismatches.

[github-actions]

Management SDK Review Summary

• Scope: Azure.ResourceManager.Compute (TypeSpec migration)
• Versioning: ✅ Pass — Version: 1.15.0-beta.2, ApiCompatVersion: 1.14.0; no major-version bump
• API surface: ✅ Pass — scanner: no violations; contextual naming: evaluated 21 new public types, flagged 10 (same as prior reviews; pending spec PR)
• ApiCompat / breaking changes: ⏳ Pending — CI build/analyze matrix still in progress
• Migration-specific checks (Phases 4–5): ✅ Pass on all 4 new commits

---

Latest commits assessment (since last review d26121636c5c)

9afbf34e6c — "Rename Compute recovery policy booleans" ✅

Regenerated OperationRecoverySettings.cs, RestartRecoveryPolicy.cs, StartRecoveryPolicy.cs, ReimageRecoveryPolicy.cs, ArmComputeModelFactory.cs, samples, and API baseline. Boolean properties now correctly use Is prefix via @@clientName`` applied in the updated spec commit (5f86e8b8afb3bb45164073bf1eb776a0e890f2de). This is generated output, not a hand-edit (rule 4.10 ✅).

Resolves the [BOOL001] blocking finding from prior reviews.

a0eb5a6dde — "Restore Compute identity serialization names" ✅

Adds "identity" wire-name argument back to [CodeGenSerialization] in both VirtualMachineData.cs and VirtualMachinePatch.cs — reverting the simplification from d26121636c5c that omitted it. Justification comment is present (rule 4.1 ✅). The wire-name is needed because VM identity uses the non-v3 wire value. Clean customization fix.

0994271aa6 — "Fix Compute generated file casing" ✅

Renames 12 files under src/Generated/ to correct casing (VirtualMachineScaleSetVm*, GalleryInVm*, ResilientVM*, VMScaleSet*). Pure generator output; no content changes. Clean (rule 4.10 ✅).

fcb76608ec — "Fix Compute LRO rehydration serialization" ✅

Adds [JsonIgnore] to 4 [Obsolete] + [EditorBrowsable(Never)] compat shim properties in VirtualMachineScaleSetIPConfiguration.cs:

• ApplicationGatewayBackendAddressPools
• ApplicationSecurityGroups
• LoadBalancerBackendAddressPools
• LoadBalancerInboundNatPools

These are NotSupportedException-throwing shims; [JsonIgnore] correctly excludes them from the serializer during LRO rehydration. Rule 4.9 ✅ (shim correctly throws because old behavior cannot be safely implemented with the new ComputeWriteableSubResourceData type); rule 4.4 ✅ (never-browse properties still have a functional replacement).

---

Prior blocking issues — now resolved

Finding	Status
[BOOL001] OperationRecoverySettings.RestartRecoveryPolicyEnabled, StartRecoveryPolicyEnabled, ReimageRecoveryPolicyEnabled	✅ RESOLVED — properties renamed with Is prefix via spec PR + regeneration
[4.10] ComputeUsageUnit.cs doc comment in // <auto-generated/> file	✅ RESOLVED — thread resolved (TypeSpec @doc + GenerateCode confirmed)

---

Non-inline findings — still pending (non-blocking)

[Contextual Naming] 10 types still need RP/service context

All fixes via @@clientName(..., "csharp") in client.tsp in spec PR Azure/azure-rest-api-specs#41351.

Type	Verdict	Recommended rename
VmScaleSetLifecycleHookEventProperties	Flag — abbreviated Vm prefix	VirtualMachineScaleSetLifecycleHookEventProperties
VmScaleSetLifecycleHookEventState	Flag — abbreviated Vm prefix	VirtualMachineScaleSetLifecycleHookEventState
VmScaleSetLifecycleHookEventType	Flag — abbreviated Vm prefix	VirtualMachineScaleSetLifecycleHookEventType
LifecycleHook	Flag — no RP context	VirtualMachineScaleSetLifecycleHook
LifecycleHookAction	Flag — no RP context	VirtualMachineScaleSetLifecycleHookAction
LifecycleHookActionState	Flag — no RP context	VirtualMachineScaleSetLifecycleHookActionState
OperationRecoverySettings	Flag — too generic	VirtualMachineScaleSetOperationRecoverySettings or ComputeOperationRecoverySettings
StorageAlignmentStatus	Flag — Storage prefix ambiguous with Azure Storage service	ComputeStorageAlignmentStatus
StorageFaultDomainAlignmentType	Flag — Storage prefix ambiguous	ComputeStorageFaultDomainAlignmentType
ZonePlacementPolicyType	Flag — no RP context	ComputeZonePlacementPolicyType

These must be addressed before the PR merges or before the package is promoted to stable.

[Non-blocking suggestion] VirtualMachineScaleSetVmResource.cs.cs double extension

The file src/Customize/VirtualMachineScaleSetVmResource.cs.cs still has a double .cs extension. Rename to VirtualMachineScaleSetVmResource.cs.

---

CI Status

Several net - pullrequest checks are currently in progress on this head commit. ApiCompat results are pending. No CI failures are visible on the current head.

---

Summary

No new blocking findings on this head commit. Both previously-blocking issues are now resolved:

1. ✅ [BOOL001] three OperationRecoverySettings boolean properties — fixed via spec + regeneration
2. ✅ [4.10] ComputeUsageUnit.cs doc comment — resolved

The 10 contextual naming types and the double-extension filename are non-blocking but should be addressed before merge/stable.

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27669923647

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27669923647

Dismissed because Azure .NET Management SDK PR Review found no blocking issues on newer commit fcb7660.

[github-actions]

Management SDK Review Summary

• Scope: Azure.ResourceManager.Compute (TypeSpec migration)
• Versioning: ✅ Pass — Version: 1.15.0-beta.2, ApiCompatVersion: 1.14.0; no major-version bump
• API surface: ✅ Pass — scanner: no violations; contextual naming: evaluated 8 new public types, flagged 6 (unchanged from prior reviews; pending spec PR)
• ApiCompat / breaking changes: ⏳ Pending — CI build/analyze matrix still in progress on this head commit
• Migration-specific checks (Phases 4–5): ⚠️ 1 non-blocking concern on latest commit

---

Latest commit assessment (b2cf539b7 — "Fix Compute obsolete compatibility properties")

Scope of changes

8 customization files changed: AvailabilitySetData.cs, CapacityReservationGroupData.cs, AvailabilitySetPatch.cs, CapacityReservationGroupPatch.cs, VirtualMachineNetworkInterfaceIPConfiguration.cs, VirtualMachineScaleSetIPConfiguration.cs, VirtualMachineScaleSetUpdateIPConfiguration.cs, RestorePointData.cs.

All changes follow the same pattern:

• Changed backward-compat shims from => throw new NotSupportedException(...) to { get; set; } auto-properties.
• Updated [Obsolete] messages from "cannot be used for mutation" to "no longer works."
• Removed [JsonIgnore] from the 4 compat properties in VirtualMachineScaleSetIPConfiguration (previously added in fcb76608ec for LRO rehydration safety).

Phase 4 assessment

[4.9] Non-blocking concern (see inline comment): The { get; set; } auto-properties are silently non-functional. GET always returns null; SET is silently discarded. This is a regression from the NotSupportedException approach (which was explicitly approved in a prior review as correct). Rule 4.9 prefers delegation with type conversion; NotSupportedException is the fallback when delegation is infeasible — not silent discard.

Please document the specific CI failure that motivated this change (rule 4.1), and either implement delegation or restore NotSupportedException with justification.

[JsonIgnore] removal (acceptable): Removing [JsonIgnore] from the 4 compat properties in VirtualMachineScaleSetIPConfiguration is safe. The class implements IJsonModel<T> with custom serialization that explicitly ignores these compat properties. The previous [JsonIgnore] was a defensive measure that is not needed now that these properties no longer throw.

---

Prior non-blocking findings — still pending

Scanner: no new violations ✅

All 182 violations are present in the 1.14.0 baseline — no new issues introduced by this PR.

New types from latest commit: OK ✅

Type	Verdict
VirtualMachineScaleSetLifecycleHookEventPatch	OK — full RP context, correct Patch suffix for update body
VirtualMachineScaleSetLifecycleHookEventTarget	OK — full RP context, domain concept

[Contextual Naming] 6 types still need RP/service context (non-blocking)

Previously flagged, fixes via @@clientName(..., "csharp") in client.tsp in spec PR Azure/azure-rest-api-specs#41351:

Type	Verdict	Recommended rename
VmScaleSetLifecycleHookEventProperties	Flag — abbreviated Vm prefix	VirtualMachineScaleSetLifecycleHookEventProperties
VmScaleSetLifecycleHookEventState	Flag — abbreviated Vm prefix	VirtualMachineScaleSetLifecycleHookEventState
VmScaleSetLifecycleHookEventType	Flag — abbreviated Vm prefix	VirtualMachineScaleSetLifecycleHookEventType
StorageAlignmentStatus	Flag — Storage prefix ambiguous with Azure Storage service	ComputeStorageAlignmentStatus
StorageFaultDomainAlignmentType	Flag — Storage prefix ambiguous	ComputeStorageFaultDomainAlignmentType
ZonePlacementPolicyType	Flag — no RP context	ComputeZonePlacementPolicyType

These must be addressed before merge or before promoting to stable.

[Non-blocking suggestion] Double .cs extension

src/Customize/VirtualMachineScaleSetVmResource.cs.cs still has a double extension. Rename to VirtualMachineScaleSetVmResource.cs.

---

CI Status

Several net - pullrequest checks are currently in progress on this head commit. No failures visible. ApiCompat results pending.

---

Summary

No new blocking findings on this head commit. One new non-blocking Phase 4 concern: the compat { get; set; } properties are silently non-functional (inline comment posted). Contextual naming types and double extension remain pending from prior reviews.

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27671119129

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27671119129

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27671119129

Dismissed because Azure .NET Management SDK PR Review found no blocking issues on newer commit b2cf539.

[github-actions]

Management SDK Review Summary

• Scope: Azure.ResourceManager.Compute (TypeSpec migration)
• Versioning: ✅ Pass — Version: 1.15.0-beta.2, ApiCompatVersion: 1.14.0; no major-version bump
• API surface: ✅ Pass — scanner: no violations; contextual naming: evaluated 0 new public types on this commit (6 flagged from earlier commits, still pending)
• ApiCompat / breaking changes: ⏳ Pending — CI build/analyze matrix still in progress on head commit
• Migration-specific checks (Phases 4–5): ⚠️ 1 non-blocking concern (unresolved, unchanged from prior review)

---

The 2 commits since the prior management SDK review (b2cf539b7) changed only sdk/compute/Azure.ResourceManager.Compute/assets.json — test recording pointer updates for gallery recording casing. No source, API surface, or customization code changed. No new findings.

Pending non-blocking items (unchanged from prior reviews)

1. [4.9] Unresolved inline thread (#discussion_r3426235897): 8 backward-compat { get; set; } auto-properties across VirtualMachineScaleSetIPConfiguration.cs, AvailabilitySetData.cs, AvailabilitySetPatch.cs, CapacityReservationGroupData.cs, CapacityReservationGroupPatch.cs, VirtualMachineNetworkInterfaceIPConfiguration.cs, VirtualMachineScaleSetUpdateIPConfiguration.cs, and RestorePointData.cs are silently non-functional (GET returns null; SET discards the value). The author has acknowledged this (comment) and plans to add [EditorBrowsable(Never)] + [Obsolete] — note that decoration alone does not address the silent-discard concern. Please also document the CI failure motivation per rule 4.1 and either implement delegation to the replacement API or restore NotSupportedException with justification.

2. [Contextual Naming] 6 types still need RP/service context — fix via @@clientName(..., "csharp") in spec PR Azure/azure-rest-api-specs#41351:

   Type	Recommended rename
   VmScaleSetLifecycleHookEventProperties	VirtualMachineScaleSetLifecycleHookEventProperties
   VmScaleSetLifecycleHookEventState	VirtualMachineScaleSetLifecycleHookEventState
   VmScaleSetLifecycleHookEventType	VirtualMachineScaleSetLifecycleHookEventType
   StorageAlignmentStatus	ComputeStorageAlignmentStatus
   StorageFaultDomainAlignmentType	ComputeStorageFaultDomainAlignmentType
   ZonePlacementPolicyType	ComputeZonePlacementPolicyType

   These must be addressed before merge or before promoting to stable.

3. [Non-blocking suggestion] src/Customize/VirtualMachineScaleSetVmResource.cs.cs still has a double .cs extension — rename to VirtualMachineScaleSetVmResource.cs.

CI Status

Several net - pullrequest checks are currently in progress on head commit e4283e4b. No failures visible. ApiCompat results pending.

---

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27673528868

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27673528868

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27673528868

Dismissed because Azure .NET Management SDK PR Review found no blocking issues on newer commit e4283e4.

[github-actions]

Management SDK Review Summary

Same status as the previous management SDK review: no blocking management SDK findings. No new management SDK review findings on this head commit.

---

The latest commit (4c61c2d3 — "Hide obsolete capacity reservation patch properties") adds [System.ObsoleteAttribute("Use CapacityReservationResources instead.", false)] to CapacityReservationGroupPatch.CapacityReservations and [System.ObsoleteAttribute("Use AssociatedVirtualMachineResources instead.", false)] to CapacityReservationGroupPatch.VirtualMachinesAssociated. This is a good, non-breaking improvement — these are read-only delegating properties that are now properly annotated for deprecation.

The commit partially addresses the open [4.9] thread for CapacityReservationGroupPatch. The remaining 7 files in that thread (VirtualMachineScaleSetIPConfiguration.cs, AvailabilitySetData.cs, AvailabilitySetPatch.cs, CapacityReservationGroupData.cs, VirtualMachineNetworkInterfaceIPConfiguration.cs, VirtualMachineScaleSetUpdateIPConfiguration.cs, RestorePointData.cs) are not yet addressed.

All 6 pending contextual-naming items and the double .cs extension remain open from prior reviews (see prior review for the full list).

Deterministic checks

• Scanner (vs 1.14.0 baseline): ✅ No violations — all 182 pre-existing violations filtered by baseline
• Contextual naming: evaluated 0 new public types on this commit (21 total new; 6 flagged from earlier commits, still pending)
• Breaking changes: ⏳ Pending — CI matrix still in progress; adding [Obsolete(error:false)] is non-breaking

CI Status

Build Compliance ✅ passed; SDL checks ✅ passed. Build/analyze/test matrix jobs are in progress on head commit 4c61c2d3. ApiCompat results pending.

---

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27676795650

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27676795650

Dismissed because Azure .NET Management SDK PR Review found no blocking issues on newer commit 4c61c2d.

[github-actions]

Management SDK Review Summary

• Scope: Azure.ResourceManager.Compute (TypeSpec migration)
• Versioning: ✅ Pass — Version: 1.15.0-beta.2, ApiCompatVersion: 1.14.0; no major-version bump
• API surface: ✅ Pass — scanner: no violations (API file unchanged from prior review; all 182 pre-existing violations filtered by 1.14.0 baseline); contextual naming: evaluated 21 new public types (all evaluated in prior reviews; 6 still flagged — pending spec PR)
• ApiCompat / breaking changes: ⏳ Pending — Build Compliance ✅ passed; SDL checks ✅ passed; build/analyze/test matrix jobs still in progress on head 5c5758105db0
• Migration-specific checks (Phases 4–5): ✅ Pass — all 10 prior review threads resolved in this commit; no new customization concerns

Latest commit assessment (5c5758105db0 — "Address remaining Compute review comments")

This commit addressed all outstanding open review threads:

[4.9] + [4.1] Non-functional backward-compat stubs — addressed ✅

All 8 files from the open [4.9] thread now have proper // Compatibility placeholder only; this property is not wired to ... comments (rule 4.1). The properties are non-throwing auto-properties as required by rule 4.9:

• VirtualMachineScaleSetIPConfiguration.cs, VirtualMachineNetworkInterfaceIPConfiguration.cs, VirtualMachineScaleSetUpdateIPConfiguration.cs — IList<WritableSubResource> stubs
• AvailabilitySetData.cs, AvailabilitySetPatch.cs, CapacityReservationGroupData.cs, CapacityReservationGroupPatch.cs, RestorePointData.cs

[4.1] CapacityReservationGroupPatch — addressed ✅

CapacityReservations and VirtualMachinesAssociated now carry [Obsolete(..., false)] + [EditorBrowsable(Never)] with proper messages pointing to the replacements.

Casting patterns — addressed ✅

SharedGalleryImageVersionData.cs, SharedGalleryImageData.cs, CommunityGalleryData.cs, CommunityGalleryImageData.cs, CommunityGalleryImageVersionData.cs, DedicatedHostGroupPatch.cs now use as instead of direct casts.

XML docs in backward-compat shims — addressed ✅

VirtualMachineScaleSetVmResource.cs.cs: <summary> xml docs removed from [EditorBrowsable(Never)] compat methods.

KeyVaultSecretReference simplification ✅

tsp-location.yaml bumped to 6c74b744578e. The generator now emits PersistableModelCreateCore/PersistableModelWriteCore virtual methods in src/Generated/Models/KeyVaultSecretReference.Serialization.cs, so the previous override in src/Customize/Models/KeyVaultSecretReference.cs was no longer needed (26 lines removed). The CI "Verify Generated Code" check will validate the generated file.

---

Prior non-blocking findings — still pending

Contextual naming — 6 types flagged (pending spec PR)

Require fixes in client.tsp in Azure/azure-rest-api-specs#41351 via @@clientName(..., "csharp"). Must be addressed before promoting to stable.

Type	Verdict	Recommended rename
VmScaleSetLifecycleHookEventProperties	Flag — abbreviated Vm prefix	VirtualMachineScaleSetLifecycleHookEventProperties
VmScaleSetLifecycleHookEventState	Flag — abbreviated Vm prefix	VirtualMachineScaleSetLifecycleHookEventState
VmScaleSetLifecycleHookEventType	Flag — abbreviated Vm prefix	VirtualMachineScaleSetLifecycleHookEventType
StorageAlignmentStatus	Flag — Storage prefix ambiguous with Azure Storage service	ComputeStorageAlignmentStatus
StorageFaultDomainAlignmentType	Flag — Storage prefix ambiguous	ComputeStorageFaultDomainAlignmentType
ZonePlacementPolicyType	Flag — no RP context	ComputeZonePlacementPolicyType

Double .cs extension

src/Customize/VirtualMachineScaleSetVmResource.cs.cs still has a double extension. Rename to VirtualMachineScaleSetVmResource.cs.

---

CI Status

Build Compliance ✅ passed; SDL checks ✅ passed. Build/analyze/test matrix jobs are in progress on head 5c5758105db0. ApiCompat results pending.

No blocking management SDK review issues on this head commit. All prior open review threads are resolved.

---

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27679227382

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27679227382

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27679227382

Dismissed because Azure .NET Management SDK PR Review found no blocking issues on newer commit 5c57581.

[github-actions]

Management SDK Review Summary

Skipped full management SDK review because only low-risk files changed since the previous no-finding management review. No new management SDK review findings.

The only change since the prior management SDK review (commit 5c5758105db0) is sdk/computeschedule/Azure.ResourceManager.ComputeSchedule/tests/Scenario/ComputescheduleOperationsTests.cs — a test-only file in the tests/** low-risk category.

CI checks are still in progress on the current head eb692d998366a64485828d8bcc57f5b9102dc6e2.

---

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27743020050

Analyzed by Azure .NET Management SDK PR Review: https://github.com/Azure/azure-sdk-for-net/actions/runs/27743020050

Dismissed because Azure .NET Management SDK PR Review found no blocking issues on newer commit eb692d9.