v1.5.1

Compare Source

1.5.1 (2025-06-23)

Acknowledgments

Thank you to our developer community members who helped to make the Event Hubs client libraries better with their contributions to this release:

• Mike Alhayek(GitHub)

Bugs Fixed

• UpdatedConfigureKeyManagementBlobClientOptions to ensure that its dependencies were resolved in the correct scope to prevent issues due to lifetime drift. Previously, a new scope was created to resolveAzureBlobXmlRepository. However,AzureBlobXmlRepository is registered as a singleton and should be resolved from the same scope in which the options are being configured. Creating a new scope introduced unnecessary overhead and potential for unexpected behavior due to differences in service lifetime management.(A community contribution, courtesy ofdanielmarbach)

v1.5.0

Compare Source

1.5.0 (2021-10-14)

Breaking Changes from 1.5.0-beta.4

• TheAllowMultiTenantAuthentication option has been removed and the default behavior is now as if it were true. The multi-tenant discovery feature can be totally disabled by either setting anAppContext switch named "Azure.Identity.DisableTenantDiscovery" totrue or by setting the environment variable "AZURE_IDENTITY_DISABLE_MULTITENANTAUTH" to "true".
• Removed theIsPIILoggingEnabled property fromTokenCredentialOptions, similar functionality is planned to be added toTokenCredentialOptions.Diagnostics in a later release.
• RemovedRegionalAuthority fromClientCertificateCredentialOptions andClientSecretCredentialOptions, along with theRegionalAuthority type. This feature will stay in preview, and these APIs will be added back in1.6.0-beta.1.
• Renamed structTokenCacheDetails toTokenCacheData.
• Renamed classTokenCacheNotificationDetails toTokenCacheRefreshArgs.
• UpdatedCacheBytes property onTokenCacheData to be readonly and a required constructor parameter.

Bugs Fixed

• Fixed issue withAuthorizationCodeCredential not specifying correct redirectUrl (Issue#​24183)

Other Changes

• Updated error messages to include links to the Azure.Identity troubleshooting guide.

v1.4.0

Compare Source

1.4.0 (2021-05-12)

New Features

• By default, the MSAL Public Client Client Capabilities are populated with "CP1" to enable support forContinuous Access Evaluation (CAE).
  This indicates to AAD that your application is CAE ready and can handle the CAE claim challenge. This capability can be disabled, if necessary, by either setting anAppContext switch named "Azure.Identity.DisableCP1" totrue or by setting the environment variable;
  "AZURE_IDENTITY_DISABLE_CP1" to "true". Note: AppContext switches can also be configured via configuration like below:

<ItemGroup>    <RuntimeHostConfigurationOptionInclude="Azure.Identity.DisableCP1"Value="true" /></ItemGroup>

Fixes and improvements

• The Microsoft Authentication Library (MSAL) dependency versions have been updated to the latest
  • Microsoft.Identity.Client version 4.30.1, Microsoft.Identity.Client.Extensions.Msal version 2.18.4.