Add Microsoft.Dashboard 2025-08-01 to public repo #37950
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
bot
added
ARMReview
new-api-version
resource-manager
RPaaS
TypeSpec
joshelton1
added
the
PublishToCustomers
|
Syncs changes from RPSaaSMaster PR (https://github.com/Azure/azure-rest-api-specs-pr/pull/24859) to public repo. We are an RPSaaSMaster-based service, just syncing to public repo for breaking change validation for future versions. Release plan: https://aka.ms/sdk-release-planner?release-plan-id=a4d3950a-159f-f011-b41c-6045bd07ef68 |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
kevin-tong-msft
approved these changes
Oct 7, 2025
|
Breaking changes previously reviewed and approved in https://github.com/Azure/azure-rest-api-specs-pr/pull/24859 |
mikekistler
added
the
BreakingChange-Approved-Previously
github-actions
bot
added
WaitForARMFeedback
This was referenced Oct 10, 2025
pmoana-ms
pushed a commit
that referenced
this pull request
Oct 23, 2025
* add 2025-08-01 tsp + swagger * run tsp compile --------- Co-authored-by: kevin-tong-msft <[email protected]>
MaryGao
pushed a commit
to Azure/azure-sdk-for-js
that referenced
this pull request
Oct 28, 2025
…949 (#36295) Configurations: 'specification/dashboard/Dashboard.Management/tspconfig.yaml', API Version: 2025-08-01, SDK Release Type: stable, and CommitSHA: '1a264b0556093b945a58a13eb39ec660afac0e04' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5481949 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. **Release plan link:** [https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=a4d3950a-159f-f011-b41c-6045bd07ef68](https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=a4d3950a-159f-f011-b41c-6045bd07ef68) **Submitted by**: [email protected] ## Release Plan Details - Release Plan: https://aka.ms/sdk-release-planner?release-plan-id=a4d3950a-159f-f011-b41c-6045bd07ef68 Spec pull request: Azure/azure-rest-api-specs#37950 Spec API version: 2025-08-01 --------- Co-authored-by: joshelton1 <[email protected]> Co-authored-by: Joshua Shelton <[email protected]> Co-authored-by: Jeremy Meng <[email protected]>
rads-1996
pushed a commit
to rads-1996/azure-sdk-for-js
that referenced
this pull request
Oct 31, 2025
…949 (Azure#36295) Configurations: 'specification/dashboard/Dashboard.Management/tspconfig.yaml', API Version: 2025-08-01, SDK Release Type: stable, and CommitSHA: '1a264b0556093b945a58a13eb39ec660afac0e04' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5481949 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. **Release plan link:** [https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=a4d3950a-159f-f011-b41c-6045bd07ef68](https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=a4d3950a-159f-f011-b41c-6045bd07ef68) **Submitted by**: [email protected] ## Release Plan Details - Release Plan: https://aka.ms/sdk-release-planner?release-plan-id=a4d3950a-159f-f011-b41c-6045bd07ef68 Spec pull request: Azure/azure-rest-api-specs#37950 Spec API version: 2025-08-01 --------- Co-authored-by: joshelton1 <[email protected]> Co-authored-by: Joshua Shelton <[email protected]> Co-authored-by: Jeremy Meng <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection 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!
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:
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.
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 ApiViewcomment 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
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.