Skip to content

[Microsoft Azure Attestation Service] Adding June 2025 Public Microsoft Azure Attestation Data Plane API Version #35360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

olkroshk
Copy link
Contributor

@olkroshk olkroshk commented Jun 19, 2025

Data Plane API Specification Update Pull Request

TDX VMs have been in preview since 2023. Currently, the TdxVm and AzureGuest attestation endpoints are available only through a 'preview' API version and need to be promoted to this new stable API version.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

  • Link to API Spec engagement record issue:

Is this review for (select one):

  • GA release

Change Scope

  • Added 2025-06-01 swagger definitions containing TdxVm and AzureGuest attestation types.
  • Added corresponding examples related to the enabled attestation types.
  • Updated specification/attestation/data-plane/readme.md

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
Swagger-Suppression-Process
to get approval.

Release planner

A release plan should have been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

Click here for links to tools, specs, guidelines & other good stuff

Tooling

Guidelines & Specifications

Helpful Links

Getting help

  • First, please carefully read through this PR description, from top to bottom.
  • 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.
  • 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.

Copy link

openapi-pipeline-app bot commented Jun 19, 2025

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ Your PR requires an API stewardship board review as it introduces a new API version (label: new-api-version). Schedule the review by following aka.ms/azsdk/onboarding/restapischedule.
  • ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. 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. In addition, refer to step 4 in the PR workflow diagram

Copy link

openapi-pipeline-app bot commented Jun 19, 2025

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

@olkroshk olkroshk force-pushed the dev/olkroshk/2025-06-01 branch from f166d1a to 5826a04 Compare June 19, 2025 02:50
@github-actions github-actions bot added the brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. label Jun 19, 2025
Copy link

github-actions bot commented Jun 19, 2025

API Change Check

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

Language API Review for Package
Swagger Microsoft.Attestation

@olkroshk olkroshk force-pushed the dev/olkroshk/2025-06-01 branch from 5826a04 to 62b028a Compare June 19, 2025 06:01
@AzureRestAPISpecReview AzureRestAPISpecReview removed the TypeSpec Authored with TypeSpec label Jun 19, 2025
@olkroshk olkroshk added the PublishToCustomers Acknowledgement the changes will be published to Azure customers. label Jun 19, 2025
@olkroshk olkroshk force-pushed the dev/olkroshk/2025-06-01 branch 2 times, most recently from 760212e to 0e5470f Compare June 19, 2025 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. data-plane new-api-version PublishToCustomers Acknowledgement the changes will be published to Azure customers.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants