[CDN] Add new stable API version 2025-06-01 for Managed Identity Origin Authentication and moving profile CRUD to share.json

[ChenglongLiu]

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:
  • Move profile CRUD to share.json to resolve Azure Front Door Standard/Premium API doc issue
    This commit reorganizes the Swagger configuration by moving a subset of APIs—specifically, the profile operations—into a separate Swagger file.There are no changes to API behavior or functionality; this update is purely structural and aims to improve clarity, maintainability, and the ease of generating documentation.
    This change is based on a longstanding request from the Microsoft Learn API documentation team. The goal is to eliminate the need for manual workarounds during documentation publishing—a process that has persisted since 2021—and to reduce the risk of human error while increasing efficiency.

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.

[openapi-pipeline-app]

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 is awaiting ARM reviewer feedback (label: WaitForARMFeedback).
  To learn when this PR will get reviewed, see ARM review queue at aka.ms/azsdk/pr-arm-review
  For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  
• ❌ The required check named Swagger LintDiff has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

[openapi-pipeline-app]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[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.Cdn
Go	sdk/resourcemanager/cdn/armcdn
Java	com.azure.resourcemanager:azure-resourcemanager-cdn-generated
Python	azure-mgmt-cdn

[mentat9]

    "authentication": {

MSI is normally placed in the top-level "identity" property. Why aren't you following that ARM standard? Ref: https://armwiki.azurewebsites.net/rbac/managed_identities/MSIOnboardingOverview.html?q=identity%20top-level%20property.

---

Refers to: specification/cdn/resource-manager/Microsoft.Cdn/stable/2025-06-01/afdx.json:5236 in 5c450b9. [](commit_id = 5c450b9, deletion_comment = False)

[mentat9]

id

[ARMBlockingComment] Don't reuse top-level property names within the property bag. You could name this property resourceId or something more specific.

[ChenglongLiu]

Hey @mentat9 , all the swagger in share.json here are moved directly from the cdn.json intact. I didn't change anything. This is a strong requirement from doc team.

This has been lingering around since 2021, and we’d like us very much to move away from the manual working around and publishing for efficiency and to avoid human errors. 

[mentat9]

type": "string

Add format: arm-id and (if appropriate) x-ms-arm-id-details. Ref: https://github.com/Azure/autorest/blob/main/docs/extensions/readme.md#x-ms-arm-id-details.

[ChenglongLiu]

updated

[mentat9]

v4

Don't move to older version. Why do you want to change from v6 to v4?

[ChenglongLiu]

updated

[mentat9]

v4

Should stay on v6.

[ChenglongLiu]

updated

[mentat9]

"x-ms-enum"

Consider adding descriptions for each member (just a suggestion, not required).

[mentat9]

@ChenglongLiu - In future, please do refactoring and adding an API version using separate PRs. It's hard for reviewers to see what's changing across API versions when there is also a bunch of refactoring. In this case, I was able to piece together the changes, and since there weren't a lot, I went ahead with ARM review.