Sample targets unsupported .NET Core 3.1; please consider upgrade or maintenance signal

[kenwith]

Summary

The Microsoft.SCIM.WebHostSample and Microsoft.SCIM projects in this repository target netcoreapp3.1. .NET Core 3.1 reached end of support on December 13, 2022 (.NET support policy). Several deprecated dependencies are also pinned to 3.1-era versions, including Microsoft.AspNetCore.Mvc.WebApiCompatShim 2.2.0 (discontinued in .NET 5+), Microsoft.AspNetCore.Authentication.JwtBearer 3.1.18, and Microsoft.AspNetCore.Mvc.NewtonsoftJson 3.1.0.

Customer impact

This sample is linked from the Microsoft Learn tutorial Build a SCIM endpoint for user provisioning as the reference implementation. Developers following the tutorial today on a currently supported .NET SDK (.NET 8 LTS or .NET 9) hit incompatibility issues immediately. Examples from this tracker:

• Upgraded Target to Latest Net Core #98 (April 2024) — explicit request to upgrade off netcoreapp3.1. No replies.
• How to deploy this code in azure app service  #102, Autorization on Azure Ad failled #93 — IDX10503: Signature validation failed reports after deploying to Azure App Service. No replies.
• Why not publish Micosoft.SCIM to nuget? #109 — user had to manually port code from .NET 4.5 → .NET 9 because of the missing modern target.

The most recent customer feedback received on the docs side (Dec 2024) was: "The .NET sample is way out of date. To a point where it cannot be built or used."

Existing in-flight work

• PR Updating to use .net8.0 #106 "Updating to use .net8.0" by @AmitavaHazra has been open since March 2025 with one comment and no merge action. If this PR (or a refresh of it) is acceptable, merging it would resolve the core issue.

Why I'm filing this

I'm a Microsoft Entra docs maintainer. I just merged a docs-side PR that adds an as-is/EOL notice to the Learn tutorial that links here (entra-docs-pr#12831) so developers know what to expect before investing time. That mitigates the immediate documentation problem, but the underlying code situation should be tracked here.

Possible paths forward (any one is fine — owner's call)

1. Upgrade to a supported .NET runtime (e.g., review and merge PR Updating to use .net8.0 #106, or open a fresh upgrade effort against current LTS).
2. Archive the repository if it's no longer maintained, so the GitHub UI shows the archived banner and search results signal the status.
3. Update the README to be more explicit about the supported state — e.g., a banner at the top stating the current target framework, the supported .NET versions, and whether contributions/PRs are being reviewed. The current "AS IS" wording is in the README but is easy to miss.
4. Recommend an alternative sample or library for new projects (and document it in the README).

Happy to coordinate from the Microsoft Learn side on whichever path you choose. If a Microsoft owner contact would be helpful for the docs/sample alignment, please point me to the right person.

Thanks!