Skip to content

Update search-concept-person.md with emailAddress note#9838

Open
dylanstetts wants to merge 2 commits intomicrosoftgraph:mainfrom
dylanstetts:patch-10
Open

Update search-concept-person.md with emailAddress note#9838
dylanstetts wants to merge 2 commits intomicrosoftgraph:mainfrom
dylanstetts:patch-10

Conversation

@dylanstetts
Copy link
Copy Markdown
Contributor

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.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Only PRs that have met the minimum requirements for content review and have this label are reviewed.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

Added note about emailAddress property availability.
@dylanstetts dylanstetts added customer support issue Doc issue raised from customer support ready for content review PR is ready for a content review - content development and tech review are complete. labels Mar 23, 2026
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 5362786:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
❌Error Details

  • Line 0, Column 0: [Error: download-failed] Download failed for file 'https://docs.microsoft.com/api/resources/sandbox/verify'. Try closing and reopening the PR. If you get this Error again, file an issue.
  • Line 0, Column 0: [Error: download-failed] Download failed for file 'https://docs.microsoft.com/api/resources/sandbox/verify'. Try closing and reopening the PR. If you get this Error again, file an 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.

@dylanstetts dylanstetts reopened this Mar 23, 2026
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 5362786:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
❌Error Details

  • Line 0, Column 0: [Error: download-failed] Download failed for file 'https://docs.microsoft.com/api/resources/sandbox/verify'. Try closing and reopening the PR. If you get this Error again, file an issue.
  • Line 0, Column 0: [Error: download-failed] Download failed for file 'https://docs.microsoft.com/api/resources/sandbox/verify'. Try closing and reopening the PR. If you get this Error again, file an 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.

@dylanstetts dylanstetts reopened this Mar 24, 2026
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 5362786:

✅ Validation status: passed

File Status Preview URL Details
concepts/search-concept-person.md ✅Succeeded

For more details, please refer to the build report.

| userPrincipalName | String |

> [!NOTE]
> The emailAddress property is only returned with the beta `/search` endpoint as of now.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Image

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

@dylanstetts dylanstetts Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also looks like v1.0 does have scoredEmailAddress, which is never returned:

Property Name="scoredEmailAddresses" Type="Collection(graph.scoredEmailAddress)"/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dylanstetts - Just noticed more properties are in the beta only list. Let's chat on Teams.

@FaithOmbongi FaithOmbongi added content review in progress needs author feedback Waiting for author (creator) of issue to provide more info and removed ready for content review PR is ready for a content review - content development and tech review are complete. labels Mar 26, 2026
Updated the properties table to indicate which properties are only returned with the beta `/search` endpoint.
@dylanstetts
Copy link
Copy Markdown
Contributor Author

@microsoft-github-policy-service agree [company="Microsoft"]

@dylanstetts
Copy link
Copy Markdown
Contributor Author

@microsoft-github-policy-service agree company="Microsoft"

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 4bd4b34:

✅ Validation status: passed

File Status Preview URL Details
concepts/search-concept-person.md ✅Succeeded

For more details, please refer to the build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content review in progress customer support issue Doc issue raised from customer support needs author feedback Waiting for author (creator) of issue to provide more info

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants