-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Release machinelearningservices microsoft.machine learning services 2025 12 01 #38783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Release machinelearningservices microsoft.machine learning services 2025 12 01 #38783
Conversation
Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec.
Updated the API version from stable/2025-09-01 to stable/2025-12-01.
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
|
@fmabroukmsft please address the Avocado errors or justify why these can't be addressed (and suppress in that case with the said justification). |
I noticed some of the enum values are removed in lastest version from last preview version, how is back compat maintained for these properties for the customers? Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2025-12-01/machineLearningServices.json:3009 in 9670ec6. [](commit_id = 9670ec6, deletion_comment = False) |
I think it's related to resizing In reply to: 3530352905 Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2025-12-01/machineLearningServices.json:3009 in 9670ec6. [](commit_id = 9670ec6, deletion_comment = False) |
why is it enum if just one value? also how is back compat handled with previous version if AAD and and KeyAndAAD is passed in the payload? Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2025-12-01/mfe.json:22703 in 9670ec6. [](commit_id = 9670ec6, deletion_comment = False) |
| "description": "Details for managed resource group assigned identities.", | ||
| "type": "object", | ||
| "properties": { | ||
| "principalId": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
returning 202 is not recommended pattern anymore. please use 201 or 200 with provisioning state indicating the creation status. please follow this RPC guideline to make the change - https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/async-api-reference.md#asynchronous-operations Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2025-12-01/workspaceRP.json:171 in 9670ec6. [](commit_id = 9670ec6, deletion_comment = False) |
please make the change for other APIs in this PR. In reply to: 3530405439 Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2025-12-01/workspaceRP.json:171 in 9670ec6. [](commit_id = 9670ec6, deletion_comment = False) |
please also add applies for all cases in this file Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2025-12-01/workspaceRP.json:478 in 9670ec6. [](commit_id = 9670ec6, deletion_comment = False) |
this is not recommended for public documentation unless this is a special string constant for this property (which doesn't seem to be the case), please remove '_' Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2025-12-01/workspaceRP.json:1912 in 9670ec6. [](commit_id = 9670ec6, deletion_comment = False) |
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection 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!
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:
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.
Additional information
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 ApiViewcomment 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
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.