[Event Grid] Add Control Plane API Version 2025-11-15-preview

[priyanshuvats]

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

Next steps that must be taken to merge this PR:

• ❌ The suppressions added to the AutoRest config files (README.mds) require review. Refer to step 1 in the PR workflow diagram, or to step 3, depending on the kind of suppression you did.

Comment generated by summarize-checks workflow run.

[mentat9]

      "type": "boolean"

ARM recommends well-chosen enum values instead of boolean for flexibility, better discoverability, and other reasons. This could be something like scalingType: { Manual, Automatic }.

---

Refers to: specification/eventgrid/resource-manager/Microsoft.EventGrid/EventGrid/preview/2025-11-15-preview/EventGrid.json:18089 in e100da5. [](commit_id = e100da5, deletion_comment = False)

[mentat9]

      "type": "boolean"

Consider enum.

---

Refers to: specification/eventgrid/resource-manager/Microsoft.EventGrid/EventGrid/preview/2025-11-15-preview/EventGrid.json:18108 in e100da5. [](commit_id = e100da5, deletion_comment = False)

[Copilot]

Pull request overview

Adds a new Event Grid ARM (control plane) preview API version 2025-11-15-preview, including the swagger for that version, associated ARM examples, and an update to the repo suppressions to allow the new version to remain in OpenAPI (non-TypeSpec) form for now.

Changes:

• Introduces preview/2025-11-15-preview/EventGrid.json for the new API version.
• Adds a large set of preview/2025-11-15-preview/examples/*.json files for operations/resources in this API version.
• Updates suppressions.yaml to include the new preview version in the TypeSpecRequirement suppression.

Reviewed changes

Copilot reviewed 219 out of 220 changed files in this pull request and generated 7 comments.

File	Description
specification/eventgrid/resource-manager/Microsoft.EventGrid/EventGrid/suppressions.yaml	Adds TypeSpecRequirement suppression for the new preview version path.
specification/eventgrid/resource-manager/Microsoft.EventGrid/EventGrid/preview/2025-11-15-preview/EventGrid.json	New/updated swagger for API version 2025-11-15-preview.
specification/eventgrid/resource-manager/Microsoft.EventGrid/EventGrid/preview/2025-11-15-preview/examples/*.json	New/updated ARM examples for operations in 2025-11-15-preview.

[priyanshuvats]

      "type": "boolean"

ARM recommends well-chosen enum values instead of boolean for flexibility, better discoverability, and other reasons. This could be something like scalingType: { Manual, Automatic }.

Refers to: specification/eventgrid/resource-manager/Microsoft.EventGrid/EventGrid/preview/2025-11-15-preview/EventGrid.json:18089 in e100da5. [](commit_id = e100da5, deletion_comment = False)

@mentat9 there is a precedence of using boolean for auto scaling feature in other products in messaging like event hub here. We prefer to keep it like that for consistency across messaging products, let me know if this is a blocking issue.

[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.EventGrid-EventGrid
Go	sdk/resourcemanager/eventgrid/armeventgrid
JavaScript	@azure/arm-eventgrid
Python	azure-mgmt-eventgrid
Java	com.azure.resourcemanager:azure-resourcemanager-eventgrid
C#	Azure.ResourceManager.EventGrid

---

Comment generated by After APIView workflow run.

[razvanbadea-msft]

PatchBodyParametersSchema

in place of creating multiple entries you can use where with a list of paths. Can you share why you need this suppresssion?

[rohitsemwal16]

EventGrid's PATCH operations use a flat update model (EventSubscriptionUpdateParameters) where properties like destination, retryPolicy, deadLetterDestination are at the top level NOT nested under a properties wrapper.

• This is the existing API contract from previous versions.
• The PatchBodyParametersSchema rule expects PATCH bodies to follow ARM's nested properties pattern, but EventGrid's design predates that convention.

Note: These suppressions were NOT added explicitly in this version, they were already in the previous preview's (2025-07-15) readme tag. This PR just copied the same suppressions into the new package-2025-11-preview tag.

[razvanbadea-msft]

i am talking about formating the suppresions. But are you sure you need to copy them to curent version if you did not added anything new to the properties of patch body?

• code: PatchBodyParametersSchema
  reason: text
  where:
  - path1
  - path2
  - etc

[rohitsemwal16]

Addressed. Used where with list of paths as suggested

[sandipsh]

Checked latest: these PatchBodyParametersSchema suppressions are carry-forward from package-2025-07 for existing paths, and this tag uses consolidated where path lists.