Skip to content

MDC: Adding 2025-10-01-preview version to Microsoft.Security/Pricings API#40501

Merged
eliagrady merged 100 commits intoAzure:mainfrom
surashed:main
Mar 11, 2026
Merged

MDC: Adding 2025-10-01-preview version to Microsoft.Security/Pricings API#40501
eliagrady merged 100 commits intoAzure:mainfrom
surashed:main

Conversation

@surashed
Copy link
Copy Markdown
Contributor

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.

@mentat9 mentat9 added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required and removed ARMChangesRequested labels Mar 5, 2026
@psah434
Copy link
Copy Markdown
Member

psah434 commented Mar 5, 2026

required check lintidiff is failing. please fix.

@psah434 psah434 added ARMChangesRequested and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Mar 5, 2026
@surashed surashed requested a review from psah434 March 6, 2026 08:28
@eliagrady eliagrady added Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates and removed ARMChangesRequested labels Mar 8, 2026
@github-actions github-actions bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Mar 8, 2026
@eliagrady eliagrady enabled auto-merge (squash) March 8, 2026 13:09
@github-actions github-actions bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Mar 10, 2026
auto-merge was automatically disabled March 11, 2026 09:39

Head branch was pushed to by a user without write access

@razvanbadea-msft razvanbadea-msft added Approved-Suppression ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review labels Mar 11, 2026
@razvanbadea-msft
Copy link
Copy Markdown
Member

Added Approved-Suppression for now to unblock the pr as as i saw mentioned the comments for them will be addressed in another PR.

@eliagrady eliagrady removed request for mentat9 and psah434 March 11, 2026 15:15
Copy link
Copy Markdown
Contributor

@eliagrady eliagrady left a comment

Choose a reason for hiding this comment

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

approved

@eliagrady eliagrady added the PublishToCustomers Acknowledgement the changes will be published to Azure customers. label Mar 11, 2026
@eliagrady eliagrady enabled auto-merge (squash) March 11, 2026 15:17
@eliagrady eliagrady removed VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates labels Mar 11, 2026
@eliagrady eliagrady merged commit 8f762af into Azure:main Mar 11, 2026
61 of 64 checks passed
markcowl added a commit to markcowl/azure-rest-api-specs that referenced this pull request Apr 7, 2026
… API (Azure#40501)

* Add blockchain to latest profile

* Add additional types

* Add SubAssessment event source type and add more automations examples

* Change Location isReadOnlu to false

* Test

* Add new read/write location and add new type TrackedResourceLocation

* Minor

* minor

* prettier fixes

* Change variable name to TrackedResourceLocation

* Change type name TrackedResourceLocation to AzureTrackedResourceLocation

* Update automations example

* Add SecureScores & SecureScoreControls as new supported datatypes in Automations resource

* [ASC.Automations] add new data type RegulatoryComplianceAssessment

* Add Secure Scores and Regulatory Compliance snapshot data types

* Changes

* minor fix

* syntax fixes

* [Microsoft.Security/Automations] Add AssessmentsSnapshot & SubAssessmentSnapshot data types

* minor

* minor

* minor

* minor

* MDC: Adding 2024-07-01-preview version to SecurityConnectors API [Introducing new Docker-Hub Environment]

* MDC: Adding 2024-07-01-preview version to SecurityConnectors API [Introducing new Docker-Hub Environment]

* Add DefenderForContainersDockerHub offering

* minor fix

* Copy files from stable/2024-01-01

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to preview/2025-10-01-preview

Updated the API version from stable/2024-01-01 to preview/2025-10-01-preview.

* Added tag for 2025-10-01-preview in readme file

* Copy files from stable/2024-01-01

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to preview/2025-10-01-preview

Updated the API version from stable/2024-01-01 to preview/2025-10-01-preview.

* Added tag for 2025-10-01-preview in readme file

* .

* Copy files from stable/2024-01-01

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to preview/2025-10-01-preview

Updated the API version from stable/2024-01-01 to preview/2025-10-01-preview.

* Added tag for 2025-10-01-preview in readme file

* .

* .

* .

* .

* .

* Keren's updates - new properties

* Remove redundent inherited property

* Add examples for containers resource level

* Revert "Remove redundent inherited property"

This reverts commit d118085.

* .

* .

* .

* .

* .

* .

* .

* .

* .

* address issue Azure#1

* address issue Azure#2

* resolving conflict from folder migration

* add v1

* Delete unnesscary files

* change

* .

* .

* .

* Remove ScopeIdSubscriptionOnly from existing API versions' types.json

The ScopeIdSubscriptionOnly parameter was incorrectly added to all existing
API versions' common/v1/types.json files. This parameter is only used by the
new 2025-10-01-preview pricings.json BatchUpdate operation and should only
exist in the 2025-10-01-preview/common/v1/types.json file.

This fixes the VersioningReviewRequired and Swagger Avocado check failures
by not modifying existing API versions.

* Fix CI failures: PUT->POST for BatchUpdate, remove error responses/examples, fix Avocado/LintDiff

* Fix LintDiff, Avocado, and prettier issues

- Add x-ms-pageable to Pricings_List operation (fixes XmsPageableForListCalls)
- Fix suppression paths: backslash to forward slash for Linux CI compatibility
- Add suppressions for new LintDiff violations: PathForResourceAction,
  AvoidAdditionalProperties, RequiredReadOnlySystemData, PutInOperationName,
  ParameterNotDefinedInGlobalParameters, EnumInsteadOfBoolean
- Add Avocado suppressions: MULTIPLE_API_VERSION, NOT_LATEST_API_VERSION_IN_DEFAULT_TAG,
  MISSING_APIS_IN_DEFAULT_TAG
- Update composite-v3 tag to include preview/2025-10-01-preview/pricings.json
- Fix truncated suppression reason text
- Apply prettier formatting to x-ms-identifiers arrays

* Fix CI: restore stable pricings and securityConnectors in default composite tag

- Keep stable/2024-01-01/pricings.json in package-composite-v3 default tag
  (was incorrectly replaced with preview/2025-10-01-preview/pricings.json)
- Restore preview/2024-08-01-preview/securityConnectors.json in default tag
  (was incorrectly changed to non-existent stable/2024-01-01/securityConnectors.json)
- Remove unnecessary MULTIPLE_API_VERSION suppression

These changes fix Swagger Avocado, BreakingChange, and LintDiff CI failures.

* Restore MULTIPLE_API_VERSION suppression for Avocado check

The default composite tag (package-composite-v3) intentionally includes
multiple API versions across Security Center features. This suppression
was mistakenly removed in the previous fix.

* Rename pricings/batch to pricings/batchUpdate for PathForResourceAction compliance

* .

* .

* Rename batch URL from batchUpdate to batch and update PathForResourceAction suppression

* Add where: clauses to 2025-10-01-preview suppressions in readme.md

* Fix ARM path validation: use /pricings/default/batch for even-segment compliance

---------

Co-authored-by: Mark Cowlishaw <markcowl@microsoft.com>
Co-authored-by: Your Name <you@example.com>
Co-authored-by: chshum <chshum@microsoft.com>
Co-authored-by: Keren Damari <kedamari@microsoft.com>
Co-authored-by: ygorshomov <ygorshomov@microsoft.com>
Co-authored-by: zedy <zedy@wicresoft.com>
Co-authored-by: Elia Grady <eliagrady@users.noreply.github.com>
Co-authored-by: Razvan Badea <156206747+razvanbadea-msft@users.noreply.github.com>
markcowl added a commit to markcowl/azure-rest-api-specs that referenced this pull request Apr 9, 2026
… API (Azure#40501)

* Add blockchain to latest profile

* Add additional types

* Add SubAssessment event source type and add more automations examples

* Change Location isReadOnlu to false

* Test

* Add new read/write location and add new type TrackedResourceLocation

* Minor

* minor

* prettier fixes

* Change variable name to TrackedResourceLocation

* Change type name TrackedResourceLocation to AzureTrackedResourceLocation

* Update automations example

* Add SecureScores & SecureScoreControls as new supported datatypes in Automations resource

* [ASC.Automations] add new data type RegulatoryComplianceAssessment

* Add Secure Scores and Regulatory Compliance snapshot data types

* Changes

* minor fix

* syntax fixes

* [Microsoft.Security/Automations] Add AssessmentsSnapshot & SubAssessmentSnapshot data types

* minor

* minor

* minor

* minor

* MDC: Adding 2024-07-01-preview version to SecurityConnectors API [Introducing new Docker-Hub Environment]

* MDC: Adding 2024-07-01-preview version to SecurityConnectors API [Introducing new Docker-Hub Environment]

* Add DefenderForContainersDockerHub offering

* minor fix

* Copy files from stable/2024-01-01

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to preview/2025-10-01-preview

Updated the API version from stable/2024-01-01 to preview/2025-10-01-preview.

* Added tag for 2025-10-01-preview in readme file

* Copy files from stable/2024-01-01

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to preview/2025-10-01-preview

Updated the API version from stable/2024-01-01 to preview/2025-10-01-preview.

* Added tag for 2025-10-01-preview in readme file

* .

* Copy files from stable/2024-01-01

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to preview/2025-10-01-preview

Updated the API version from stable/2024-01-01 to preview/2025-10-01-preview.

* Added tag for 2025-10-01-preview in readme file

* .

* .

* .

* .

* .

* Keren's updates - new properties

* Remove redundent inherited property

* Add examples for containers resource level

* Revert "Remove redundent inherited property"

This reverts commit d118085.

* .

* .

* .

* .

* .

* .

* .

* .

* .

* address issue Azure#1

* address issue Azure#2

* resolving conflict from folder migration

* add v1

* Delete unnesscary files

* change

* .

* .

* .

* Remove ScopeIdSubscriptionOnly from existing API versions' types.json

The ScopeIdSubscriptionOnly parameter was incorrectly added to all existing
API versions' common/v1/types.json files. This parameter is only used by the
new 2025-10-01-preview pricings.json BatchUpdate operation and should only
exist in the 2025-10-01-preview/common/v1/types.json file.

This fixes the VersioningReviewRequired and Swagger Avocado check failures
by not modifying existing API versions.

* Fix CI failures: PUT->POST for BatchUpdate, remove error responses/examples, fix Avocado/LintDiff

* Fix LintDiff, Avocado, and prettier issues

- Add x-ms-pageable to Pricings_List operation (fixes XmsPageableForListCalls)
- Fix suppression paths: backslash to forward slash for Linux CI compatibility
- Add suppressions for new LintDiff violations: PathForResourceAction,
  AvoidAdditionalProperties, RequiredReadOnlySystemData, PutInOperationName,
  ParameterNotDefinedInGlobalParameters, EnumInsteadOfBoolean
- Add Avocado suppressions: MULTIPLE_API_VERSION, NOT_LATEST_API_VERSION_IN_DEFAULT_TAG,
  MISSING_APIS_IN_DEFAULT_TAG
- Update composite-v3 tag to include preview/2025-10-01-preview/pricings.json
- Fix truncated suppression reason text
- Apply prettier formatting to x-ms-identifiers arrays

* Fix CI: restore stable pricings and securityConnectors in default composite tag

- Keep stable/2024-01-01/pricings.json in package-composite-v3 default tag
  (was incorrectly replaced with preview/2025-10-01-preview/pricings.json)
- Restore preview/2024-08-01-preview/securityConnectors.json in default tag
  (was incorrectly changed to non-existent stable/2024-01-01/securityConnectors.json)
- Remove unnecessary MULTIPLE_API_VERSION suppression

These changes fix Swagger Avocado, BreakingChange, and LintDiff CI failures.

* Restore MULTIPLE_API_VERSION suppression for Avocado check

The default composite tag (package-composite-v3) intentionally includes
multiple API versions across Security Center features. This suppression
was mistakenly removed in the previous fix.

* Rename pricings/batch to pricings/batchUpdate for PathForResourceAction compliance

* .

* .

* Rename batch URL from batchUpdate to batch and update PathForResourceAction suppression

* Add where: clauses to 2025-10-01-preview suppressions in readme.md

* Fix ARM path validation: use /pricings/default/batch for even-segment compliance

---------

Co-authored-by: Mark Cowlishaw <markcowl@microsoft.com>
Co-authored-by: Your Name <you@example.com>
Co-authored-by: chshum <chshum@microsoft.com>
Co-authored-by: Keren Damari <kedamari@microsoft.com>
Co-authored-by: ygorshomov <ygorshomov@microsoft.com>
Co-authored-by: zedy <zedy@wicresoft.com>
Co-authored-by: Elia Grady <eliagrady@users.noreply.github.com>
Co-authored-by: Razvan Badea <156206747+razvanbadea-msft@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-Avocado Approved-Suppression ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager SuppressionReviewRequired Versioning-Approved-BugFix https://github.com/Azure/azure-sdk-tools/issues/6374

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants