Skip to content

Add 2025-11-01-preview version to Microsoft.Subscription#37722

Merged
ComradeCow merged 4 commits intomainfrom
comradecow/subscription-add-2025-11-01
Dec 8, 2025
Merged

Add 2025-11-01-preview version to Microsoft.Subscription#37722
ComradeCow merged 4 commits intomainfrom
comradecow/subscription-add-2025-11-01

Conversation

@ComradeCow
Copy link
Member

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.

spec_pr_review_workflow_diagram

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

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
Copy link

github-actions bot commented Sep 24, 2025

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

Comment generated by summarize-checks workflow run.

@ComradeCow
Copy link
Member Author

Waiting to merge this until #37575 is merged.

@github-actions github-actions bot added brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. ARMReview new-api-version resource-manager WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Sep 24, 2025
@github-actions
Copy link

github-actions bot commented Sep 24, 2025

API Change Check

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

Language API Review for Package
Swagger Microsoft.Subscription
Go sdk/resourcemanager/subscription/armsubscription
C# Azure.ResourceManager.Subscription
JavaScript @azure/arm-subscriptions

@github-actions github-actions bot added the BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required label Sep 24, 2025
@ComradeCow ComradeCow added the PublishToCustomers Acknowledgement the changes will be published to Azure customers. label Sep 24, 2025
@github-actions github-actions bot added NotReadyForARMReview BreakingChange-JavaScript-Sdk and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Sep 24, 2025
@ComradeCow ComradeCow force-pushed the comradecow/subscription-add-2025-11-01 branch 2 times, most recently from 867dc16 to d6ac262 Compare September 24, 2025 16:11
@mikekistler
Copy link
Member

Breaking changes previously reviewed and approved in #29912.

@mikekistler mikekistler added the BreakingChange-Approved-Previously Changes were reviewed and approved in a previous PR label Sep 25, 2025
@github-actions github-actions bot added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required and removed NotReadyForARMReview labels Sep 25, 2025
"description": "Subscription Changed Target Directory response properties."
},
"systemData": {
"$ref": "../../../../../common-types/resource-management/v5/types.json#/definitions/systemData",
Copy link
Contributor

@sandipsh sandipsh Sep 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

v5

v6 is latest #Resolved

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated all the shared type references to v6.

"format": "date-time",
"x-nullable": true
},
"sourceOwnerEmail": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sourceOwnerEmail

could this use a pattern as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a pattern for email? I couldn't find examples in the repository.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

me neither, low pri/ nice to have.

"description": "The id of the subscription being transferred.",
"readOnly": true,
"type": "string",
"pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"

not sure if there is something common for this.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not either, and I'd love to hear if there is. Doing a search through the repo there's a 1001 different ways guids get specified. I originally had "format": "uuid" but was told not to use that because of how it gets interpreted for some SDKs to use a guid type rather than string? Not sure what the best pattern is.

"enum": [
"Initialized",
"InProgress",
"Completed"
Copy link
Contributor

@sandipsh sandipsh Sep 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pretty self explanatory, but might be helpful to add description to add more context/info for doc purpose. #Resolved

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the values in x-ms-enum.

@sandipsh
Copy link
Contributor

please take a look at the avocado failure as well.

@sandipsh sandipsh added ARMChangesRequested and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Sep 26, 2025
@ComradeCow ComradeCow force-pushed the comradecow/subscription-add-2025-11-01 branch from d6ac262 to a0ee0b6 Compare September 26, 2025 14:28
@ComradeCow
Copy link
Member Author

The Avocado current errors should be resolved with #37575 as that resolves the MULTIPLE_API_ERROR code. There will be errors remaining for the deprecated apis that we will need the Approved-Avocado tag.

@github-actions github-actions bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Sep 26, 2025
@sandipsh
Copy link
Contributor

@ComradeCow are you handling the avocado error? I still see it.

@sandipsh sandipsh added ARMChangesRequested and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Sep 26, 2025
Scott Kool added 4 commits September 29, 2025 21:03
Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.
Updated the API version from preview/2024-08-01-preview to preview/2025-11-01-preview.
@ComradeCow ComradeCow force-pushed the comradecow/subscription-add-2025-11-01 branch from a0ee0b6 to 9a21c61 Compare September 30, 2025 02:06
@github-actions github-actions bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Sep 30, 2025
@ComradeCow
Copy link
Member Author

#37575 has now been merged which cleans up the Avocado errors.

@ravimeda ravimeda added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Sep 30, 2025
@ComradeCow
Copy link
Member Author

(poking to keep this pr from going stale)

@microsoft-github-policy-service microsoft-github-policy-service bot added no-recent-activity There has been no recent activity on this issue. and removed no-recent-activity There has been no recent activity on this issue. labels Oct 27, 2025
@ComradeCow
Copy link
Member Author

(poking to keep this pr from going stale)

@microsoft-github-policy-service microsoft-github-policy-service bot added no-recent-activity There has been no recent activity on this issue. and removed no-recent-activity There has been no recent activity on this issue. labels Nov 17, 2025
@ComradeCow
Copy link
Member Author

(poking to keep this pr from going stale)

@microsoft-github-policy-service microsoft-github-policy-service bot added no-recent-activity There has been no recent activity on this issue. and removed no-recent-activity There has been no recent activity on this issue. labels Dec 8, 2025
@ComradeCow ComradeCow merged commit 2fc7fcc into main Dec 8, 2025
120 of 122 checks passed
@ComradeCow ComradeCow deleted the comradecow/subscription-add-2025-11-01 branch December 8, 2025 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review BreakingChange-Approved-Previously Changes were reviewed and approved in a previous PR BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. new-api-version PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants