You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the microsoftTeams.people.selectPeople chooser in a MS Teams App context like this:
Unfortunately, when a user object returned by the searchV2 endpoint used by the peoplePicker doesn't have an email attribute, the people picker returns that user with an empty string as it's email as you can see here:
Search for users in peoplePicker and observe searchV2 response:
Confirm peoplePicker selection and console.log the return result.
Is the email not being in the searchV2 response a bug or is this something users or Azure AD admins can configure?
Would it be possible for the peoplePicker to always return email and UPN so clients can handle these cases at their will?
The text was updated successfully, but these errors were encountered:
Hi LeonYasoon! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.
Continuation of #1526
When using the microsoftTeams.people.selectPeople chooser in a MS Teams App context like this:
Unfortunately, when a user object returned by the searchV2 endpoint used by the peoplePicker doesn't have an email attribute, the people picker returns that user with an empty string as it's email as you can see here:
Search for users in peoplePicker and observe searchV2 response:
Confirm peoplePicker selection and console.log the return result.
Is the email not being in the searchV2 response a bug or is this something users or Azure AD admins can configure?
Would it be possible for the peoplePicker to always return email and UPN so clients can handle these cases at their will?
The text was updated successfully, but these errors were encountered: