[4.x] Update Azure.Identity and related dependencies - #3787
Merged
Conversation
Avery-Dunn
marked this pull request as ready for review
April 24, 2026 14:40
Bogdan Gavril (bgavrilMS)
approved these changes
Apr 24, 2026
Bogdan Gavril (bgavrilMS)
force-pushed
the
avdunn/dependency-updates
branch
from
April 27, 2026 11:00
5744c6f to
d575152
Compare
Peter (pmaytak)
approved these changes
Apr 29, 2026
Contributor
Author
|
Copilot resolve the merge conflicts in this pull request |
…onfigurationJsonVersion Co-authored-by: Avery-Dunn <62066438+Avery-Dunn@users.noreply.github.com>
Contributor
Merged master (commit |
This was referenced Jul 6, 2026
Closed
Closed
This was referenced Jul 13, 2026
Closed
Closed
This was referenced Jul 27, 2026
Closed
Closed
This was referenced Aug 3, 2026
Closed
This was referenced Aug 12, 2026
This was referenced Aug 19, 2026
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.
Summary
This PR updates dependency versions on older TFMs (net462/net472/netstandard2.0) to establish a consistent Microsoft.Extensions.* 8.0.x minimum across all non-framework-coupled packages. It also updates Azure.Identity and System.Text.Json for security fixes. See #3795 for ID Web 3.x version
Background
Azure.Identity 1.17.2 (sovereign cloud fixes), pulls in Azure.Core 1.50.0, which introduces a transitive cascade on older TFMs:
DI.Abstractions 8.0.2 defines
ServiceCollection, causing a CS0433 type collision with the full DI package (previously pinned at 2.1.0 via Extensions.Http 3.1.3). Resolving this requires DI ≥ 8.0.0 on older TFMs regardless of approach.Rather than patch individual packages, this PR bumps the entire M.E.* stack to 8.0.x together, establishing a clean baseline that eliminates several 5-year version gaps and aligns with the net8.0 TFM versions.
Dependency changes
Security/behavioral updates (all TFMs):
M.E.* baseline bump (net462/net472/netstandard2.0):
Extensions.Logging.Abstractions was already at 8.0.3 (forced by Azure.Core cascade); DataProtection and System.Security.Cryptography.* are unchanged.
Version management improvements
Directory.Build.propsrestructured to use centralized variables, modeled after MISE:CommonMicrosoftExtensionsVersion = 8.0.0base variableMicrosoft.Extensions base versionsPropertyGroup sets defaults for CachingMemory, ConfigBinder, Configuration, Configuration.Json, DI, Hosting, Http, and Logging using the base variableHardcoded versions replaced with variables in csproj files:
Microsoft.Identity.Web.OWIN.csproj: Configuration, Configuration.Json → variablesMicrosoft.Identity.Web.TokenAcquisition.csproj: Configuration.Json → variableMicrosoft.Identity.Web.Test.csproj: Hosting 3.1 →$(MicrosoftExtensionsHostingVersion)Source code changes
To accommodate the updated dependency versions:
ExcludeSharedTokenCacheCredential = true(excluded by default in Azure.Identity 1.17.2)_logger(Logging.Abstractions 8.0.3 tightens ILogger to non-nullable)#if NET7_0_OR_GREATER— all remaining TFMs use DI 8.0.0+ which hasstring? nameConfigurationManager(Configuration 8.0.0 adds a conflicting type), fixed nullable annotationsIHttpClientFactory.CreateClient(Http 8.0.0 tightens nullable types)_entriesto_coherentState/_stringEntries)No public API or meaningful behavioral changes were made. The only internal API change (
PostConfigure string! → string?) is tracked inInternalAPI.Unshipped.txt.