New Resource Provider - Microsoft.AIInfraOptimization

[sakshamgargMS]

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

• New resource provider.
• New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
• Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
• Update existing version to fix OpenAPI spec quality issues in S360.
• Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
• Other, please clarify:
  • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

• I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• I have reviewed following Resource Provider guidelines, including
  ARM resource provider contract and
  REST guidelines (estimated time: 4 hours).
  I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
• A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

Additional information

This PR publishes the spec merged in the private repo via Azure/azure-rest-api-specs-pr#29872 (merge commit e28667b52ed73ea6d86715cdcc1a61480da34189 on RPSaaSMaster). All files under specification/aiinfraoptimization/ are byte-identical to that merge commit. The only difference is the CODEOWNERS entry, which additionally lists sakshamgargMS.

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

• First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.
• For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.

[github-actions]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
  This PR is not ready for ARM review (label: NotReadyForARMReview). This PR will not be reviewed by ARM until relevant problems are fixed. Consult the rest of this Next Steps to Merge comment for details.
  Once the blocking problems are addressed, add to the PR a comment with contents /azp run. Automation will re-evaluate this PR and if everything looks good, it will add WaitForARMFeedback label which will put this PR on the ARM review queue.
  For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  
• ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
  This PR has ARMModelingReviewRequired label. This means it is introducing a new Resource Provider namespace or a new resource type. New RPs and new resource types require a discussion with the ARM Modeling Review team before merging.
  
  If you haven't discussed yet:
  Please join the ARM API Modeling Review Office Hours - a drop-in, first-come, first-served session (no booking required):
  
  • When: Every Tuesday and Thursday, 9:30-10:30 AM PST
  • How to join: Join via Teams
  • Come prepared with your questions and a design document (Word/PowerPoint is fine; TypeSpec/Swagger not required).
  • For more details refer: API Review Workflow | ARM Wiki
  If ARMModelingSignedOff label was removed by automation:
  This happens when the lease file is not found. Please check with the PM you discussed your design with to confirm if the lease file PR has been merged. In the public repo, lease files reflect immediately after merge. In the private repo (azure-rest-api-specs-pr), lease files typically sync within a few hours, but it can take up to 1-2 business days depending on sync pipeline timing and queue load. Please wait for the sync to complete.
  For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  

Comment generated by summarize-checks workflow run.

[github-actions]

Contributor readiness: required access

Warning

Access issues can block approvals, Azure DevOps pipelines, or labeling.

User / area	Access issue	PR impact
🟡 sakshamgarg@microsoft.com	Author/committer account unavailable; add or verify this email on a GitHub account. Affects 2 commits: 7031d08, 1cebe29.	Not determined.

Internal contributors: set up / renew access. Recheck: /azsdk check-access.

Contributors with verified access (2)

Public Azure membership and repository write access verified.

User	Roles
sakshamgargMS	PR author, commit author, committer
venu-sivanadham	commit author, approved reviewer

Non-blocking check; fix access issues to unblock affected actions.

Last updated: 2026-10-19T13:01:57.682Z

[github-actions]

Package Name Review Required

Plane: Management Plane

Language	Package Name	Namespace	Format	Status	Approvers
dotnet	Azure.ResourceManager.AIInfraOptimization	Azure.ResourceManager.AIInfraOptimization	✅	✅ Approved by Arthur Ma (@ArthurMa1978)	Arthur Ma (@ArthurMa1978), m-nash, JoshLove-msft
java	com.azure.resourcemanager:azure-resourcemanager-aiinfraoptimization	com.azure.resourcemanager.aiinfraoptimization	✅	✅ Approved by Arthur Ma (@ArthurMa1978)	Arthur Ma (@ArthurMa1978), m-nash, JoshLove-msft
python	azure-mgmt-aiinfraoptimization	azure.mgmt.aiinfraoptimization	✅	✅ Approved by Arthur Ma (@ArthurMa1978)	Arthur Ma (@ArthurMa1978), m-nash, JoshLove-msft
typescript	@azure/arm-aiinfraoptimization	@azure/arm-aiinfraoptimization	✅	✅ Approved by Arthur Ma (@ArthurMa1978)	Arthur Ma (@ArthurMa1978), m-nash, JoshLove-msft
go	sdk/resourcemanager/aiinfraoptimization/armaiinfraoptimization	sdk/resourcemanager/aiinfraoptimization/armaiinfraoptimization	✅	✅ Approved by Arthur Ma (@ArthurMa1978)	Arthur Ma (@ArthurMa1978), m-nash, JoshLove-msft

How to approve:

• Per language: apply package-name-<language>-approved label
• All at once: apply package-name-approved-all label (shortcut for mgmt plane)

Merge is blocked until all languages are approved.

Approver list: .github/protected-labels.yml
Process: .github/workflows/src/package-name-approval/PACKAGE-NAME-REVIEW-PROCESS.md
Package names extracted via tsp compile with typespec-metadata emitter

[github-actions]

API Change Check

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

Language	API Review for Package
Swagger	Microsoft.AIInfraOptimization-AIInfraOptimization
Go	sdk/resourcemanager/aiinfraoptimization/armaiinfraoptimization
JavaScript	@azure/arm-aiinfraoptimization
Java	com.azure.resourcemanager:azure-resourcemanager-aiinfraoptimization
Python	azure-mgmt-aiinfraoptimization

---

Comment generated by After APIView workflow run.

[github-actions]

ARM API Review Summary\n\nResult: Changes requested\n\nScope and revision: Full review of PR #47287 at pinned head 1cebe29062cab838573b850bc8078ec7d1c7829b, base 6f0a58c875a0fae861544e9082e02046360fd115. The changed TypeSpec provider and generated OpenAPI artifacts were reviewed.\n\nBlocking findings: 2\n\n1. routes.tsp:14 — new suppression of arm-resource-interface-requires-decorator for the provider-level action interface.\n2. main.tsp:17 — new suppression of casing-style for the canonical Microsoft.AIInfraOptimization RP namespace.\n\nBoth suppressions have technically specific justifications, but neither had the required Approved-TypeSpecSuppression approval context when reviewed. Inline comments contain the rule citations, classification, approval context, and remediation.\n\nValidation: The independent ARM API Review Critic verified both findings and found no additional blocking API, security, LRO, paging, examples, operations-list, or generated-OpenAPI contract issues. Generated OpenAPI includes the required TypeSpec marker, OAuth2 security, standard errors, examples, and pageable operations metadata.\n\nRequired next step: Apply Approved-TypeSpecSuppression after confirming approval for each suppression, or remove/remodel the suppressions to satisfy the underlying lint rules.

🔍 ARM API review by ARM API Review: Automated Workflow

[github-actions]

ARM API review completed for pinned head 1cebe29062cab838573b850bc8078ec7d1c7829b (full scope). The independent ARM API Review Critic verified the two inline blocking findings: both are new, technically justified TypeSpec suppressions that lack the required Approved-TypeSpecSuppression approval context. No additional blocking API, security, LRO, paging, examples, or operations-contract issues were identified. Please obtain the required approval or remove/remodel the suppressions.

🔍 ARM API review by ARM API Review: Automated Workflow

[Venu Sivanadham (venu-sivanadham)]

The provider level action is already gone through ARM modeling office hours, and same changes are already present in RPSaaSMaster branch of pr repo. Hence approved the suppressions.

[sakshamgargMS]

/azsdk check-access

[sakshamgargMS]

Arthur Ma (@ArthurMa1978) m-nash JoshLove-msft could you please review the management-plane package names for the new Microsoft.AIInfraOptimization RP (see the Package Name Review Required table above)?

Language	Package
.NET	Azure.ResourceManager.AIInfraOptimization
Java	com.azure.resourcemanager:azure-resourcemanager-aiinfraoptimization
Python	azure-mgmt-aiinfraoptimization
TypeScript	@azure/arm-aiinfraoptimization
Go	sdk/resourcemanager/aiinfraoptimization/armaiinfraoptimization

All follow the standard ARM naming pattern. ARM sign-off and TypeSpec suppression approval are complete; package-name approval (package-name-approved-all) is the remaining blocker for merge and for SDK Validation - Python. Thank you!

[github-actions]

✅ Package Name Approved

All required package name approvals received. This PR is clear to merge from a package name perspective.

[sakshamgargMS]

All package-name approvals are now present. Python package name azure-mgmt-aiinfraoptimization has been reserved through the official pipeline (https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6972222), Python SDK validation passed on retry, and the refreshed SDK Validation Status and Next Steps to Merge report success.

Venu Sivanadham (@venu-sivanadham) could you please provide the approving PR review required for merge? ARM sign-off and TypeSpec suppression approvals are already recorded. GitHub still reports CHANGES_REQUESTED from the earlier automated review about those suppressions; could a maintainer also resolve that stale review through the normal review process? We have not bypassed any review gates.

The two findings requested approval for TypeSpec suppressions. Venu confirmed the ARM modeling review and approved the suppressions on 2026-10-16; typespec-suppressions-approved is present and validation passes. Venu formally approved this PR on 2026-10-19. Dismissing the superseded automated review; no API or code findings remain from that review.