chore(deps): update azure azure-sdk-for-net monorepo#2516
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
|
Thank you for your contribution! 🙏 We will review it as soon as possible. |
75f27e6 to
35fe88d
Compare
35fe88d to
b9099b3
Compare
ff296cb to
d73b028
Compare
83df6b9 to
7c94f19
Compare
5474dd4 to
f7c38ec
Compare
f7c38ec to
ac7b411
Compare
37f7b62 to
d1b2907
Compare
2f404a1 to
65a92d6
Compare
8055e99 to
335c703
Compare
ebc4a72 to
7b89000
Compare
7b89000 to
fb5057c
Compare
fb5057c to
85fccad
Compare
85fccad to
5d2e5b8
Compare
7769786 to
d9f75f7
Compare
7404121 to
4c108c3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.11.4→1.21.01.3.1→1.7.11.4.0→1.7.1Release Notes
Azure/azure-sdk-for-net (Azure.Identity)
v1.21.0Compare Source
1.21.0 (2026-04-10)
Other Changes
Azure.Identitytypes have been moved toAzure.Coreand are now available throughTypeForwardedToattributes. This is a non-breaking change — existing code continues to work transparently. The library's version number now aligns with that ofAzure.Core. See the Migration Guide for details.v1.20.0Compare Source
1.20.0 (2026-03-30)
Features Added
appsettings.json.Breaking Changes
AddAzureClient,AddKeyedAzureClient, andWithAzureCredentialreturn type changed fromIHostApplicationBuildertoIClientBuilderto align with theIClientBuildercomposition change in System.ClientModel.v1.19.0Compare Source
1.19.0 (2026-03-11)
Features Added
ClientCertificateCredentialto specify a path in the form ofcert:/StoreLocation/StoreName/Thumbprintto refer to a certificate in the platform certificate store - such as the Windows Certificate Store on Windows, and the KeyChain on MacOS - instead of a file on disk. For example to load a certificate from the "My" store in the "CurrentUser" location use the pathcert:/CurrentUser/My/E661583E8FABEF4C0BEF694CBC41C28FB81CD870(A community contribution, courtesy of fowl2).Other Changes
Microsoft.Identity.ClientandMicrosoft.Identity.Client.Extensions.Msaldependencies to version 4.83.1.v1.18.0Compare Source
1.18.0 (2026-02-25)
Features Added
Added experimental
Microsoft.Extensions.ConfigurationandMicrosoft.Extensions.DependencyInjectionintegration for Azure SDK clients. For details, see the Configuration and Dependency Injection documentation.The
WorkloadIdentityCredentialOptions.IsAzureProxyEnabledproperty, which enables Azure Kubernetes token proxy mode, is only available in beta releases of this package.AzureDeveloperCliCredentialnow parses JSON error output fromazd auth tokento extract clean error messages instead of including raw JSON in exceptions. Error messages like{"type":"consoleMessage","data":{"message":"ERROR: fetching token: ..."}}are now displayed asERROR: fetching token: ....v1.17.2Compare Source
1.17.2 (2026-04-15)
Other Changes
Microsoft.Identity.ClientandMicrosoft.Identity.Client.Extensions.Msaldependencies to version 4.83.1.v1.17.1Compare Source
1.17.1 (2025-11-18)
Other Changes
Microsoft.Identity.ClientandMicrosoft.Identity.Client.Extensions.Msaldependencies to version 4.78.0.v1.17.0Compare Source
1.17.0 (2025-10-07)
Bugs Fixed
WithTenantIdinstead ofWithTenantIdFromAuthorityto prevent malformed Uris to the authority.Other Changes
BrowserCustomizationOptions.UseEmbeddedWebViewproperty. This option requires additional dependencies on Microsoft.Identity.Client.Desktop and is no longer supported. Consider using brokered authentication instead.v1.16.0Compare Source
1.16.0 (2025-09-09)
Features Added
DefaultAzureCredentialconstructor that accepts a custom environment variable name for credential configuration. This provides flexibility beyond the defaultAZURE_TOKEN_CREDENTIALSenvironment variable. The constructor accepts any environment variable name and uses the same credential selection logic as the existingAZURE_TOKEN_CREDENTIALSprocessing.DefaultAzureCredential.DefaultEnvironmentVariableNameconstant property that returns"AZURE_TOKEN_CREDENTIALS"for convenience when referencing the default environment variable name.AzureCliCredential,AzurePowerShellCredential, andAzureDeveloperCliCredentialnow throw anAuthenticationFailedExceptionwhen theTokenRequestContextincludes claims, as these credentials do not support claims challenges. The exception message includes guidance for handling such scenarios.AZURE_TOKEN_CREDENTIALSor the equivalent custom environment variable is configured toManagedIdentityCredential, theDefaultAzureCredentialdoes not issue a probe request and performs retries with exponential backoff.Bugs Fixed
AzureDeveloperCliCredentialhanging when theAZD_DEBUGenvironment variable is set by adding the--no-promptflag to prevent interactive prompts (#52005).BrokerCredentialis now included in the chain whenAZURE_TOKEN_CREDENTIALSis set todev.DefaultAzureCredentialthat caused the credential chain to be constructed incorrectly when using AZURE_TOKEN_CREDENTIALS in combination withDefaultAzureCredentialOptions.Other Changes
BrokerCredentialis now always included in theDefaultAzureCredentialchain. If theAzure.Identity.Brokerpackage is not referenced, an exception will be thrown whenGetTokenis called, making its behavior consistent with the rest of the credentials in the chain.Microsoft.Identity.Clientdependency to version 4.76.0.Microsoft.Identity.Client.Extensions.Msaldependency to version 4.76.0.v1.15.0Compare Source
1.15.0 (2025-08-07)
Breaking Changes
Behavioral Breaking Changes
SharedTokenCacheCredential. The supporting credential (SharedTokenCacheCredential) was a legacy mechanism for authenticating clients using credentials provided to Visual Studio. For brokered authentication, consider usingInteractiveBrowserCredentialinstead. The following changes have been made:SharedTokenCacheCredentialclass is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheCredentialOptionsclass is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]DefaultAzureCredentialOptions.ExcludeSharedTokenCacheCredentialproperty is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheUsernameproperty is marked as[Obsolete]and[EditorBrowsable(EditorBrowsableState.Never)]SharedTokenCacheCredentialis no longer included in theDefaultAzureCredentialauthentication flowBugs Fixed
AdditionallyAllowedTenantsvalues which will now be matched against tenant IDs without case sensitivity, making the authentication more resilient to case differences in tenant IDs returned from WWW-Authenticate challenges (#51693).Other Changes
BrokerAuthenticationCredentialhas been renamed asBrokerCredential.Added the
EditorBrowsable(Never)attribute to propertyVisualStudioCodeTenantIdasTenantIdis preferred. TheVisualStudioCodeTenantIdproperty exists only to provide backwards compatibility.v1.14.2Compare Source
1.14.2 (2025-07-10)
Other changes
Microsoft.Identity.Clientdependency to version 4.73.1v1.14.1Compare Source
1.14.1 (2025-07-08)
Bugs Fixed
v1.14.0Compare Source
1.14.0 (2025-05-13)
Other Changes
Username,Password,AZURE_USERNAME, andAZURE_PASSWORDin XML comments fromEnvironmentCredentialOptionsandEnvironmentCredentialdue to lack of MFA support. See MFA enforcement details.AZURE_USERNAMEandAZURE_PASSWORDas obsolete due to lack of MFA support. See MFA enforcement details.AZURE_TOKEN_CREDENTIALSenvironment variable toDefaultAzureCredential, which allows for choosing between 'deployed service' and 'developer tools' credentials. Valid values are 'dev' for developer tools and 'prod' for deployed service.v1.13.2Compare Source
1.13.2 (2025-01-14)
Bugs Fixed
DefaultAzureCredentialOptions.TenantIdtwice throws anInvalidOperationException(#47035)ManagedIdentityCredentialdoes not honor theCancellationTokenpassed toGetTokenandGetTokenAsync. (#47156)DefaultAzureCredentialwould not fall through to the next credential in the chain under certain exception conditions.ManagedIdentityCredentialwhen used in aChainedTokenCredentialwhere the invalid json responses do not fall through to the next credential in the chain. (#47470)v1.13.1Compare Source
1.13.1 (2025-11-19)
Other Changes
Azure.Identitydependency to version 1.17.1v1.13.0Compare Source
1.13.0 (2024-10-14)
Features Added
ManagedIdentityCredentialnow supports specifying a user-assigned managed identity by object ID.Bugs Fixed
DefaultAzureCredentialattempts to authenticate with theMangagedIdentityCredentialand it receives either a failed response that is not json, it will now fall through to the next credential in the chain. #45184AzurePipelinesCredentialso it doesn't result in a redirect response when an invalid system access token is provided.Other Changes
AzureEventSourceListener. Previously, the log level was always set toMicrosoft.Identity.Client.LogLevel.Info.AzurePowerShellCredentialnow utilizes the AsSecureString parameter to Get-AzAccessToken for version 2.17.0 and greater of the Az.Accounts module.AzurePipelinesCredential.v1.12.1Compare Source
1.12.1 (2024-09-26)
Bugs Fixed
v1.12.0Compare Source
1.12.0 (2024-06-17)
Features Added
AzurePipelinesCredentialfor authenticating with Azure Pipelines service connections.OnBehalfOfCredentialnow supports client assertion callbacks for acquiring tokens on behalf of a user.ClientAssertionCredentialOptionsnow supportsTokenCachePersistenceOptionsfor configuring token cache persistence.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.