Token caching is a feature provided by the Azure Identity library that allows apps to:
- Improve their resilience and performance.
- Reduce the number of requests made to Microsoft Entra ID to obtain access tokens.
- Reduce the number of times the user is prompted to authenticate.
When an app needs to access a protected Azure resource, it typically needs to obtain an access token from Microsoft Entra ID. Obtaining that token typically involves sending a request to Microsoft Entra ID and may also involve prompting the user. Microsoft Entra ID then validates the credentials provided in the request and issues an access token.
Token caching, via the Azure Identity library, allows the app to store this access token in memory, where it's accessible to the current process, or on disk where it can be accessed across application or process invocations. The token can then be retrieved quickly and easily the next time the app needs to access the same resource. The app can avoid making another request to Microsoft Entra ID, which reduces network traffic and improves resilience. Additionally, in scenarios where the app is authenticating users, token caching avoids prompting the user each time new tokens are requested.
In-memory token caching is the default option provided by the Azure Identity library. This caching approach allows apps to store access tokens in memory. With in-memory token caching, the library first determines if a valid access token for the requested resource is already stored in memory. If a valid token is found, it's returned to the app without the need to make another request to Microsoft Entra ID. If a valid token isn't found, the library will automatically acquire a token by sending a request to Microsoft Entra ID.
The in-memory token cache provided by the Azure Identity library:
- Is thread-safe.
- Can be used by multiple threads concurrently.
Note: When Azure Identity library credentials are used with Azure service libraries (for example, Azure Blob Storage), the in-memory token caching is active in the HttpPipeline layer as well. All TokenCredential implementations are supported there, including custom implementations external to the Azure Identity library.
As there are many levels of cache, it's not possible disable in-memory caching. However, the in-memory cache may be cleared by creating a new credential instance.
Persistent disk token caching is an opt-in feature in the Azure Identity library. The feature allows apps to cache access tokens in an encrypted, persistent storage mechanism. As indicated in the following table, the storage mechanism differs across operating systems.
| Operating system | Storage mechanism |
|---|---|
| Linux | Keyring |
| macOS | Keychain |
| Windows | DPAPI |
With persistent disk token caching enabled, the library first determines if a valid access token for the requested resource is already stored in the persistent cache. If a valid token is found, it's returned to the app without the need to make another request to Microsoft Entra ID. Additionally, the tokens are preserved across app runs, which:
- Makes the app more resilient to failures.
- Ensures the app can continue to function during a Microsoft Entra ID outage or disruption.
- Avoids having to prompt users to authenticate each time the process is restarted.
The sample showcases how to activate persistence token caching in the credentials offered by the Azure Identity library.
When authenticating a user via InteractiveBrowserCredential, DeviceCodeCredential, or UsernamePasswordCredential, an AuthenticationRecord can be persisted as well. It's returned from the authenticate API and contains data identifying an authenticated account. It's needed to identify the appropriate entry in the persisted token cache to silently authenticate on subsequent executions. There's no sensitive data in the AuthenticationRecord, so it can be persisted in a non-protected state.
Here is an example of an application storing the AuthenticationRecord to the local file system after authenticating the user.
Once an application has configured an InteractiveBrowserCredential, DeviceCodeCredential, or UsernamePasswordCredential to persist token data and an AuthenticationRecord, it's possible to silently authenticate. This example demonstrates an application setting the TokenCachePersistenceOptions and retrieving an AuthenticationRecord from the local file system to create an InteractiveBrowserCredential capable of silent authentication.
The credential created in this example will silently authenticate given that a valid token for corresponding to the AuthenticationRecord still exists in the persisted token data. There are some cases where interaction will still be required such as on token expiry, or when additional authentication is required for a particular resource.
The following table indicates the state of in-memory and persistent caching in each credential type.
Note: In-memory caching is activated by default. Persistent token caching needs to be enabled as shown in this code sample.
| Credential | In-memory token caching | Persistent disk token caching |
|---|---|---|
AuthorizationCodeCredential |
Supported | Supported |
AzureCliCredential |
Not Supported | Not Supported |
AzureDeveloperCliCredential |
Not Supported | Not Supported |
AzurePowershellCredential |
Not Supported | Not Supported |
ClientAssertionCredential |
Supported | Supported |
ClientCertificateCredential |
Supported | Supported |
ClientSecretCredential |
Supported | Supported |
DefaultAzureCredential |
Supported if the target credential in the credential chain supports it | Not Supported |
DeviceCodeCredential |
Supported | Supported |
EnvironmentCredential |
Supported | Supported |
InteractiveBrowserCredential |
Supported | Supported |
ManagedIdentityCredential |
Supported | Not Supported |
OnBehalfOfCredential |
Supported | Supported |
UsernamePasswordCredential |
Supported | Supported |
WorkloadIdentityCredential |
Supported | Supported |