From only looking at this page, it looks like the email scope is supported and would bring back an email claim. However if I refer to this page: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-limitations, it explicitly states that the email scope is not supported for the v2.0 endpoint. Would be nice to note that in the email scope section.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@col726 Thanks for the feedback ! I have assigned this issue to content author to investigate and update the document as appropriate.
@col726 Thank you very much for your feedback. I'm working with our feature team to rationalize this and we'll update our content accordingly. #in-progress
@SaurabhSharma-MSFT @MohitGargMSFT @femsulu - Hello. After discussions with the feature team, they are working on some code changes that will address the issue filed here. Can you please change the issue type from doc-enhancement to something else like #product-bug or #product-question? I've still got a work item to update the docs once the code has been updated, but for now the issue is not doc-related. Thank you.
Also adding @MicahMcKittrick-MSFT to help change the issue type.
The documentation still looks to be wrong, the limitations page still says you can only request scopes for an app ID that's the same as the client but that's not true
email claim is returned as null
@col726 @andyjenkinson @huchenhai - Thank you all for your feedback. After some discussions with our PM and dev, I've updated the topic to clarify the current email claim behavior:
email claim is returned only if an optional claim is configured and scope is scope=email was specified in the request. However, this behavior will change as the v2.0 endpoint is updated to further comply with the Open ID Connect and OAuth2.0 standards."@SaurabhSharma-MSFT @MohitGargMSFT @femsulu @MicahMcKittrick-MSFT - #please-close
A fix from a related GitHub issue also addresses the question here. See above response and current resolution. We'll be making further changes to the docs as we evolve the v2.0 endpoint to further comply with the standards, but nothing right now that we can add to the docs.
Most helpful comment
@SaurabhSharma-MSFT @MohitGargMSFT @femsulu - Hello. After discussions with the feature team, they are working on some code changes that will address the issue filed here. Can you please change the issue type from doc-enhancement to something else like #product-bug or #product-question? I've still got a work item to update the docs once the code has been updated, but for now the issue is not doc-related. Thank you.
Also adding @MicahMcKittrick-MSFT to help change the issue type.