Azure / Azure/azure-rest-api-specs
[Azure Key Vault - Key Vault] REST API Review
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 424
Description
New REST API Review meeting has been requested.
**Service Name**: Azure Key Vault - Key Vault
**Review Created By**: Sandeep Sen
**Review Date**: 07/03/2025 04:00 PM PT
**Release Plan**: [1796](https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=a2708b7c-ff51-f011-8779-000d3a302e4a)
**PR**:
**Hero Scenarios Link**: Not Provided
**Core Concepts Doc Link**: Not Provided
**Description**: New Features for 2025-06-01-preview API version:
PFX to PEM flag in Get Certificate.
Add previous version to the Get Secret.
Support for URIs and IP addresses in SAN properties.
TokenConsumed API for BuiltIn certificates creation
Detailed meeting information and documents provided can be accessed [here](https://web.powerapps.com/apps/e41c69de-ef96-44ba-b287-0e012e7c13ae?view=edit&event=9765e3b3-ff51-f011-877a-00224804b6c3)
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation [here](https://aka.ms/azsdk/onboarding/restapischedule)
Contributor guide
Research direction
Start with the REST API onboarding documentation and the linked meeting details and release plan. The issue names four proposed Key Vault API changes but no repository files, tests, or implementation owner; completion would require an agreed review outcome and corresponding specification work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100