Update search-concept-person.md with emailAddress note#9838
Update search-concept-person.md with emailAddress note#9838dylanstetts wants to merge 2 commits intomicrosoftgraph:mainfrom
Conversation
Added note about emailAddress property availability.
|
Learn Build status updates of commit 5362786: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
|
Learn Build status updates of commit 5362786: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
|
Learn Build status updates of commit 5362786: ✅ Validation status: passed
For more details, please refer to the build report. |
concepts/search-concept-person.md
Outdated
| | userPrincipalName | String | | ||
|
|
||
| > [!NOTE] | ||
| > The emailAddress property is only returned with the beta `/search` endpoint as of now. |
There was a problem hiding this comment.
Hi @dylanstetts - I think this is already subtly inferred by the fact that the v1.0 endpoint doesn't have the emailAddresses property on the person object? Here's a screenshot of the v1 schema.
There was a problem hiding this comment.
Hi @FaithOmbongi, while I tend to agree with you, I believe our customer facing documentation should be abundantly clear and not need to be subtly inferred, but rather stated clearly. I have had escalations for this topic, so inferences are causing customer confusion.
There was a problem hiding this comment.
Also looks like v1.0 does have scoredEmailAddress, which is never returned:
Property Name="scoredEmailAddresses" Type="Collection(graph.scoredEmailAddress)"/
There was a problem hiding this comment.
@dylanstetts - Just noticed more properties are in the beta only list. Let's chat on Teams.
Updated the properties table to indicate which properties are only returned with the beta `/search` endpoint.
|
@microsoft-github-policy-service agree [company="Microsoft"] |
|
@microsoft-github-policy-service agree company="Microsoft" |
|
Learn Build status updates of commit 4bd4b34: ✅ Validation status: passed
For more details, please refer to the build report. |
Added note about emailAddress property availability.
Important
Required for API changes:
Add other supporting information, such as a description of the PR changes:
This is from a customer escalation: https://portal.microsofticm.com/imp/v5/incidents/details/21000000925148/summary
Important
The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.
After you've created your PR, expand this section for tips and additional instructions.
#feedback-addressedto the pull request.For more information, see the Content review process summary.