Fixed Entra Integration and added Entra-protected MCP client and server sample projects #940
+1,581
−6
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.


scopesupport for Entra ID.README.mdfor setup, usage, and troubleshooting.I updated the ClientOAuthProvider to be compatible with MS Entra and added sample projects for that scenario.
PS: This will fix issue 939.
Motivation and Context
It is very important for the SDK to work with MS Entra for authentication and authorization.
How Has This Been Tested?
I tested with my MS Entra tenant. The sample project works and is able to successfully authenticate, exchange the token, and call downstream apis (MS Graph and SharePoint) accordingly.
Breaking Changes
Don't think so.
Types of changes
Checklist
Additional context