Skip to content

Added 2026-05-15 public preview version with Batch revocation and WESP program type changes in CP#42683

Open
amritas wants to merge 15 commits intoAzure:mainfrom
amritas:amshanbh/maypublic
Open

Added 2026-05-15 public preview version with Batch revocation and WESP program type changes in CP#42683
amritas wants to merge 15 commits intoAzure:mainfrom
amritas:amshanbh/maypublic

Conversation

@amritas
Copy link
Copy Markdown
Contributor

@amritas amritas commented Apr 27, 2026

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

New stable API version 2026-03-01 for OperationalInsights with two additions:

Added "protectionLevel" property to table properties. A string enum with values "General" (table data accessible through standard permissions) and "Protected" (table data isolated by default, requires explicit scoped authorization).

Added "dataAuthorizationMode" property to workspace features. A nullable boolean that enables data authorization mode for the workspace.

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.

@amritas amritas added the DoNotMerge <valid label in PR review process> use to hold merge after approval label Apr 27, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 27, 2026

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
    This PR has ARMModelingReviewRequired label. This means it is introducing a new Resource Provider namespace or a new resource type. New RPs and new resource types require a discussion with the ARM Modeling Review team before merging.
    Please schedule a meeting at ARM API Modeling Office Hours.
    For details of the ARM review, see aka.ms/azsdk/pr-arm-review


Comment generated by summarize-checks workflow run.

@github-actions github-actions Bot added ARMReview new-api-version resource-manager RPaaS TypeSpec Authored with TypeSpec WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required NotReadyForARMReview and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Apr 27, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 27, 2026

API Change Check

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

Language API Review for Package
Swagger Microsoft.CodeSigning
TypeSpec Microsoft.CodeSigning
Go sdk/resourcemanager/artifactsigning/armartifactsigning
JavaScript @azure/arm-artifactsigning
Python azure-mgmt-artifactsigning
Java com.azure.resourcemanager:azure-resourcemanager-artifactsigning

Comment generated by After APIView workflow run.

@amritas amritas added the PublishToCustomers Acknowledgement the changes will be published to Azure customers. label Apr 27, 2026
@amritas amritas requested a review from Copilot April 28, 2026 07:15
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new 2026-05-15-preview API version for the CodeSigning ARM (control plane) specification, including a batch certificate revocation action and a new programType property on certificate profiles.

Changes:

  • Adds a new package-2026-05-15-preview tag and a new generated Swagger file for the preview version.
  • Introduces a new batch revoke action (revokeCertificates) and a RevokeCertificateList request model.
  • Adds new preview examples for operations, CodeSigningAccounts, and CertificateProfiles.

Reviewed changes

Copilot reviewed 31 out of 31 changed files in this pull request and generated 16 comments.

Show a summary per file
File Description
specification/codesigning/resource-manager/readme.md Adds a new preview package tag and sets it as the default tag.
specification/codesigning/resource-manager/Microsoft.CodeSigning/preview/2026-05-15-preview/codeSigningAccount.json New preview Swagger (generated) including new action + models.
specification/codesigning/CodeSigning.Management/main.tsp Adds the 2026-05-15-preview TypeSpec version enum entry.
specification/codesigning/CodeSigning.Management/models.tsp Adds programType and a new RevokeCertificateList model.
specification/codesigning/CodeSigning.Management/CertificateProfile.tsp Replaces single revoke action with batch revoke action.
specification/codesigning/**/examples/2026-05-15-preview/*.json Adds new examples for the preview API version (both generated + source examples).
Comments suppressed due to low confidence (1)

specification/codesigning/resource-manager/Microsoft.CodeSigning/preview/2026-05-15-preview/codeSigningAccount.json:1

  • Several string properties appear to have well-known formats but are missing format annotations: accountUri should be format: uri, and certificate createdDate/expiryDate should be format: date-time (SCHEMA-FORMAT-DETECT). The examples currently use non-ISO date strings (e.g., 3/14/2023 5:27:49 PM), which also violates EX-FORMAT.
{

Comment thread specification/codesigning/resource-manager/readme.md Outdated
Comment thread specification/codesigning/resource-manager/readme.md
amritas and others added 4 commits April 28, 2026 12:58
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…ng/preview/2026-05-15-preview/codeSigningAccount.json

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@mikekistler mikekistler added the BreakingChange-Approved-BranchPolicyException Changes violate the branch policy but exception has been granted. aka.ms/azsdk/pr-brch-deep label May 4, 2026
@github-actions github-actions Bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 4, 2026
@github-actions github-actions Bot added ARMModelingReviewRequired NotReadyForARMReview and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMModelingReviewRequired ARMReview BreakingChange-Approved-BranchPolicyException Changes violate the branch policy but exception has been granted. aka.ms/azsdk/pr-brch-deep BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required DoNotMerge <valid label in PR review process> use to hold merge after approval new-api-version NotReadyForARMReview PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager RPaaS TypeSpec Authored with TypeSpec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants