Azure-docs: email scope appears as if it is supported

Created on 30 May 2018  Â·  7Comments  Â·  Source: MicrosoftDocs/azure-docs

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.


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

active-directorsvc assigned-to-author in-progress product-issue triaged

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.

All 7 comments

@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:

@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.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bdcoder2 picture bdcoder2  Â·  3Comments

AronT-TLV picture AronT-TLV  Â·  3Comments

paulmarshall picture paulmarshall  Â·  3Comments

jharbieh picture jharbieh  Â·  3Comments

jamesgallagher-ie picture jamesgallagher-ie  Â·  3Comments