chore(deps): update azure azure-sdk-for-net monorepo #156
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.12.0->1.13.24.6.0->4.7.0Release Notes
Azure/azure-sdk-for-net (Azure.Identity)
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 (2024-10-24)
Bugs Fixed
ManagedIdentityCredentialfrom attempting to detect if Workload Identity is enabled in the current environment. #46653DefaultAzureCredentialfrom progressing pastManagedIdentityCredentialin some scenarios where the identity was not available. #46709v1.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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.