Define contract for Batch RuleSet feature

[mangoo1]

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

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

✅ 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.

[github-actions]

API Change Check

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

Language	API Review for Package
TypeSpec	Microsoft.Cdn
Swagger	Microsoft.Cdn-Cdn
Go	sdk/resourcemanager/cdn/armcdn
Java	com.azure.resourcemanager:azure-resourcemanager-cdn
JavaScript	@azure/arm-cdn

[mangoo1]

@mangoo1 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Microsoft"

[mikeharder]

The remaining error from LintDiff looks valid to me:

You do repeat this in the path and body. Path:

azure-rest-api-specs/specification/cdn/resource-manager/Microsoft.Cdn/Cdn/stable/2025-12-01/openapi.json

Lines 6832 to 6841 in 053e5d8

	{
	"name": "profileName",
	"in": "path",
	"description": "Name of the Azure Front Door Standard or Azure Front Door Premium or CDN profile which is unique within the resource group.",
	"required": true,
	"type": "string",
	"minLength": 1,
	"maxLength": 260,
	"pattern": "^[a-zA-Z0-9]+(-*[a-zA-Z0-9])*$"
	},

Body:

azure-rest-api-specs/specification/cdn/resource-manager/Microsoft.Cdn/Cdn/stable/2025-12-01/openapi.json

Lines 16370 to 16378 in 053e5d8

	"RuleSetProperties": {
	"type": "object",
	"description": "The JSON object that contains the properties of the Rule Set to create.",
	"properties": {
	"profileName": {
	"type": "string",
	"description": "The name of the profile which holds the rule set.",
	"readOnly": true
	},

You can either change your spec (and maybe service?) to fix this, or add a suppression:

https://github.com/Azure/azure-rest-api-specs/wiki/Swagger-LintDiff#adding-scoped-suppressions

[mangoo1]

I tend to supress this as that was defined before my changes, would be breaking changes if I remove that.

The remaining error from LintDiff looks valid to me:

You do repeat this in the path and body. Path:

azure-rest-api-specs/specification/cdn/resource-manager/Microsoft.Cdn/Cdn/stable/2025-12-01/openapi.json

Lines 6832 to 6841 in 053e5d8

	{
	"name": "profileName",
	"in": "path",
	"description": "Name of the Azure Front Door Standard or Azure Front Door Premium or CDN profile which is unique within the resource group.",
	"required": true,
	"type": "string",
	"minLength": 1,
	"maxLength": 260,
	"pattern": "^[a-zA-Z0-9]+(-*[a-zA-Z0-9])*$"
	},

Body:

azure-rest-api-specs/specification/cdn/resource-manager/Microsoft.Cdn/Cdn/stable/2025-12-01/openapi.json

Lines 16370 to 16378 in 053e5d8

	"RuleSetProperties": {
	"type": "object",
	"description": "The JSON object that contains the properties of the Rule Set to create.",
	"properties": {
	"profileName": {
	"type": "string",
	"description": "The name of the profile which holds the rule set.",
	"readOnly": true
	},

You can either change your spec (and maybe service?) to fix this, or add a suppression:

https://github.com/Azure/azure-rest-api-specs/wiki/Swagger-LintDiff#adding-scoped-suppressions