NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #3348 most downloaded on npm
Provides credential implementations for Azure SDK libraries that can authenticate with Microsoft Entra ID
Last release 8 days ago
14 Sep 2026
Release timing varies
gaps range from 8 days to 2 months
Nearly every release is documented
notes for 48 of 51 stable releases
78 versions withdrawn
withdrawn after publishing
7 years old
808 releases · first in 2019
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Improved error messages for AzurePipelinesCredential for Authentication Failed scenarios. #30387
OnBehalfOfCredential now supports taking clientAssertion callback getAssertion. #29711
OnBehalfOfCredential now supports taking clientAssertion callback getAssertion. #29711OnBehalfOfCredential migrated to use MSALClient internally instead of MSALNode flow. This is an internal refactoring and should not result in any behavioral changes. #29890InteractiveBrowserCredential migrated to use MSALClient internally instead of MSALNode flow in Node. This is an internal refactoring and should not result in any behavioral changes. #29894Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Added AzurePipelinesCredential for supporting workload identity federation in Azure Pipelines with service connections.
AzurePipelinesCredential for supporting workload identity federation in Azure Pipelines with service connections.### Bugs Fixed - Managed identity bug fixes
Introducing a new credential AzurePipelinesCredential for supporting workload identity federation in Azure Pipelines with service connections. #29392
AzurePipelinesCredential for supporting workload identity federation in Azure Pipelines with service connections. #29392ClientSecretCredential, ClientCertificateCredential, and ClientAssertionCredential no longer try silent authentication unnecessarily as per the MSAL guidelines. For more information please refer to the Entra documentation on token caching. #29405DeviceCodeCredential migrated to use MSALClient internally instead of MSALNode flow. This is an internal refactoring and should not result in any behavioral changes. #29405UsernamePasswordCredential migrated to use MSALClient internally instead of MSALNode flow. This is an internal refactoring and should not result in any behavioral changes. #29656AuthorizationCodeCredential migrated to use MSALClient internally instead of MSALNode flow. This is an internal refactoring and should not result in any behavioral changes. #29831Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
### Bugs Fixed - Managed identity bug fixes
Adds support for getBearerTokenProvider that returns a callback function to get a token for a given scope. This is useful for scenarios where an expli
getBearerTokenProvider that returns a callback function to get a token for a given scope. This is useful for scenarios where an explicit Entra token is needed without having to worry about the token refreshing details.ClientSecretCredential, ClientCertificateCredential, and ClientAssertionCredential migrated to use MSALClient internally instead of MSALNode flow. This is an internal refactoring and should not result in any behavioral changes. #28873Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
InteractiveBrowserCredential: Added support for using the default broker account. #28979.
InteractiveBrowserCredential: Added support for using the default broker account. #28979.DefaultAzureCredential and ManagedIdentityCredential, with maxRetryCount increased to 5. For more information, see BREAKING_CHANGES.md.ManagedIdentityCredential and DefaultAzureCredential to be overridden by customers.[AutoPR @azure-arm-relay]-generated-from-SDK Generation - JS-6660728 ( #…
[AutoPR @azure-arm-relay]-generated-from-SDK Generation - JS-6660728 (#…
Configurations:
'specification/relay/resource-manager/Microsoft.Relay/Relay/tspconfig.yaml',
SDK Release Type: beta, and CommitSHA:
'f6b53f105b95da05276530a0754a1c71b4f16397' in SpecRepo:
'https://github.com/Azure/azure-rest-api-specs' Pipeline run:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6660728
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://azsdk-releaseplan-dashboard-hveph5aqhhcfhtgu.westus-01.azurewebsites.net/?releaseplan=35919](https://azsdk-releaseplan-dashboard-hveph5aqhhcfhtgu.westus-01.azurewebsites.net/?releaseplan=35919)
**Submitted by**: asiddiquee@microsoft.com
---------
Co-authored-by: azure-sdk <azuresdk@microsoft.com>
Co-authored-by: kazrael2119 <98569699+kazrael2119@users.noreply.github.com>
Co-authored-by: ZiWei Chen <v-ziweichen@microsoft.com>
AzureCliCredential: Added support for the new response field which represents token expiration timestamp as time zone agnostic value. (#28333)new DefaultAzureCredential() will no longer throw when one of the credentials in the chain fails to instantiate. Any creation errors will be logged when getToken is called. #28264Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →