- Fixed an issue where
contentTypepassed tosetSecret()andupdateSecretProperties()was not forwarded to the service request body. #38301
- Fix dependency issue.
- Added support for service API version
2025-07-01which is now the default. #37785 - Added
outContentTypeoption togetSecret()allowing callers to request PEM-format output for certificate-backed secrets (e.g.,outContentType: KnownContentType.PEM). #37785 - Added
previousVersionreadonly property toSecretPropertieswhich returns the identifier of the previous certificate version. #37785
- Added support for service API version
7.6which is now the default. #32947
- Generate code from TypeSpec. This is an internal change that should not affect customers. #31848
- Added support for service API version
7.6-preview.2. #32947
- Generate code from TypeSpec. This is an internal change that should not affect customers. #31848
- Add support for Continuous Access Evaluation (CAE). #31140
- Native ESM support has been added, and this package will now emit both CommonJS and ESM. #31254
- The default service version is now
7.5.
- The default service version is now
7.5-preview.1.
- Updated
SecretClientto support service version 7.4 by default.
- Verify the challenge resource matches the vault domain.
This should affect few customers who can set
disableChallengeResourceVerificationin the options bag totrueto disable. See https://aka.ms/azsdk/blog/vault-uri for more information.
- Fixed an issue where
listPropertiesOfSecretVersionswould fail on the second page when using pagination.
- Migrated to the Core v2 HTTP pipeline. As a result of this migration:
- The response types no longer contain the raw response
_response. To access the raw response, anonResponsecallback has to be passed in the request options bag, for example:let rawResponse: FullOperationResponse | undefined; await client.operationName(/* ...parameters... */, { onResponse: (response) => (rawResponse = response), });
- The re-export of the
PipelineOptionstype from@azure/core-httphas been removed. If you previously relied on this export, consider either using the more specificSecretClientOptionstype or importingPipelineOptionsfrom@azure/core-httpdirectly.
- The response types no longer contain the raw response
- As a result of the migration to Core v2:
- The response types no longer contain the raw response
_response. To access the raw response, anonResponsecallback has to be passed in the request options bag, for example:let rawResponse: FullOperationResponse | undefined; await client.operationName(/* ...parameters... */, { onResponse: (response) => (rawResponse = response), });
- The re-export of the
PipelineOptionstype from@azure/core-httphas been removed. If you previously relied on this export, consider either using the more specificSecretClientOptionstype or importingPipelineOptionsfrom@azure/core-httpdirectly.
- The response types no longer contain the raw response
- Migrated the generated client to
@azure/core-rest-pipeline("Core v2"). See Azure Core v1 vs v2 for more on the difference and benefits of the move.
- This release updates
SecretClientto support service version 7.3 by default.
- Support multi-tenant authentication against Key Vault and Managed HSM when using @azure/identity 2.0.0 or newer.
- Updated SecretClient to use service version 7.3-preview by default.
- Updated the latest service version to 7.3.
- With the dropping of support for Node.js versions that are no longer in LTS, the dependency on
@types/nodehas been updated to version 12. Read our support policy for more details. - Changed TS compilation target to ES2017 in order to produce smaller bundles and use more native platform features.
- Updated our internal core package dependencies to their latest versions in order to add support for Opentelemetry 1.0.0 which is compatible with the latest versions of our other client libraries.
- Added support for the 7.2 version of the Key Vault service API.
- Fixed a bug with
beginDeleteSecretandbeginRecoverDeletedSecretin which unknown service errors wouldn't bubble up properly to the end users. - Fixed an issue where retrying a failed initial Key Vault request may result in an empty body.
- Added a
certificateKeyId?: stringsecret property to use instead of the deprecatedkeyId?: URLand removed"lib": ["dom"]fromtsconfig.json
- Fixed a bug with
beginDeleteSecretandbeginRecoverDeletedSecretin which unknown service errors wouldn't bubble up properly to the end users. - Renamed the
KeyVaultSecretIdtoKeyVaultSecretIdentifier, and exported a method to parse Key Vault Secret Ids:parseKeyVaultSecretIdentifier.
- Improved tracing across the various KeyVault libraries. By switching to a consistent naming convention, ensuring spans are always closed appropriately, and setting the correct status when an operation errors developers can expect an improved experience when enabling distributed tracing.
- We now ensure tracing spans are properly closed with an appropriate status when an operation throws an exception.
- If a traced operation throws an exception we will now properly record the exception message in the tracing span.
- Finally, naming conventions have been standardized across the KeyVault libraries taking the format of
Azure.KeyVault.<PACKAGE NAME>.<CLIENT NAME>.
- Fixed an issue where retrying a failed initial Key Vault request may result in an empty body.
- Updated the Latest service version to 7.2.
- Added a
certificateKeyId?: stringsecret property to use instead of the deprecatedkeyId?: URLand removed"lib": ["dom"]fromtsconfig.json - Added
recoveryId,scheduledPurgeDate, anddeletedOnto a deleted secret's top-level attributes and deprecated these attributes from the deleted secret'spropertiescollection.
- [Breaking] Removed
dist-browserfrom the published package. To bundle the Azure SDK libraries for the browsers, please read our bundling guide: link. - Updated the Key Vault Secrets Long Running Operation Pollers to follow a more compact and meaningful approach moving forward.
- Bug fix: The logging of HTTP requests wasn't properly working - now it has been fixed and tests have been written that verify the fix.
- Added
parseKeyVaultSecretsIdentifierandParsedKeyVaultSecretsIdentifierto help with parsing the unique identifiers of Key Vault Secrets.
4.1.0 had changes both relative to the last GA release, 4.0.4, and the last preview release, 4.1.0-preview.1.
- Fixed bug 9005, which caused parallel requests to throw if one of them needed to authenticate.
- Fixed bug 8378, which caused the challenge based authentication to re-authenticate on every new request.
- Added the optional
apiVersionproperty to theSecretClientoptional parameters. It defaults to the latest supported API version, which currently is7.1-preview. - Added
recoverableDaysas an optional property toSecretProperties.
- Updated dependencies to their latest available versions.
- Fixed the support of dotenv while testing.
- Improved the available documentation, and added a README in the test folder.
- KeyClient's vaultUrl property is now public, but readonly.
- Updated to use OpenTelemetry 0.2 via
@azure/core-tracing.
- This release marks the general availability of the
@azure/keyvault-secretspackage. - All of the public API methods now have their custom option types.
- All of the option types can now receive a
requestOptionsparameter to customize the options sent to the HTTP client. - Renamed
restoreSecrettorestoreSecretBackup. - Removed publicly accessible properties that referenced the
pipelineand thecredentialused during the creation of both theKeyClientand theCryptographyClient.
deleteSecretandrecoverDeletedSecretare now out of the public API. UsebeginDeleteSecretandbeginRecoverDeletedSecretinstead. They both return a Poller (from our package@azure/core-lro) that manages the long running operation.- Renamed
SecrettoKeyVaultSecret. - Renamed most of the date properties to end in the
Onsuffix. - All options should match the method's name.
- All methods that return keyProperties (like the ones that iterate) should contain "propertiesOf" in their names.
- Flattened all the options bag to extend the
RequestOptionsBaseinterface.
- Updated to use the latest version of
@azure/core-tracing,@azure/identity,@azure/core-httpand@azure/core-armpackages
- API Change: Nested classes are now flattened into a "properties" property.
- Improved the tests, the README and upgraded dependencies.
- Added the browser folder to the released bundle.
- Fixed the missing TypeScript types by adding back the generated
.d.tsfile to the package.json
- Added browser support.
- Added support for challenge-based authentication.
- Fix broken links for API references and samples.
- Update custom user agent string to include the right package name and version.
For release notes and more information please visit https://aka.ms/azsdk/releases/july2019preview