External Contacts Not Displayed with 'Friendly Name'
Please provide a way to rename a Contact, or have a Contact displayed with a 'user-friendly' name.
External Contacts are displayed with an unfriendly name (it appears to be their SMTP address). Typically there is no easy way to determine the person with just this address when looking for their entry in the Contacts list. We previously used Skype For Business and this displayed external contacts with a Friendly Name but after we were forced into using Teams, this functionality was lost.
Image of Contact list attached
Alexei Subbotsky commented
Still having this issue, no friendly names even for those External users who are themselves provisioned in Office 365.
Dwight Burford commented
Now that was interesting! When I was logging my vote for this request, I was directed to input my email address to vote. So I did. But then the form required that I enter my name as well. That is the functionality I was expecting in Teams when adding a guest to a Team. Unlike some of the commenters below, this issue is still unresolved on our Teams implementation. Hope this gets implemented soon. Its quite awkward/unprofessional to only show an email from a team member. Thanks.
the issue we experience occurs at the point in which you add an external user, you are provided one opportunity to create the friendly name for that user. Once created you cannot edit or update the contact. As an Admin, I can see the external contact in Azure, but any changes or edits I make do not reflect in Teams. Also, if I delete the contact, when I try to re-add it in Teams it is somehow identified by the same email address and I do not have the opportunity to set the friendly name of the contact. Somewhere the "system" remembers that contact forever.
I would like the ability to update external contacts that I add in Teams.
Please, we are having this issue. Some of the organizations having autogenerated emails aliases, which are not usable.
It looks like has been partially implemented. When I add a contact it shows me the persons display name (instead of e-mail address). However I have hundreds of existing contacts that display with e-mail addresses. It's really incontinent because display names are last name (comma) first name and e-mail addresses are first initial last name. Finding contacts is a pain!
A recent (Jan 2020 first week) fix has enabled display of external user Friendly names but apparently only if the external user is a Teams/Office 365 user. The Teams client (and the latest SfB client) can detect that the remote user across Federation is a Teams users, and also show their Friendly name.
However, the problem still exists if the external user is a pure Skype for Business user or Trusted Application reachable across federation. In this case, only the SIP URI (email style) shows, and not the Display Name.
So: If remote user is Teams user, friendly name will show. If remote user is SfB On-premise user, friendly name does not show (as of Jan 14, 2020)
Attila Kovács commented
We have recently faced the same problem, but after opening a case at Microsoft, the issue seems to be fixed by 10th of January, 2020. You need to sign out and sign in to have the correct display names showed in Teams' Contacts and Recent view.
Bob Reiter commented
this is a real pain when trying to see a contact name to chat or if multiple external user join a call of who is actually in the meeting Joe Smith or Jack Smith when it shows their email address of Jsmith12 and JSmith23 - Who is who?
Microsoft needs to fix this ASAP since they force migrated us to Teams
Agree that this is a problem. All of the friendly names of the contacts that were migrated from Skype for Business seem to have been lost.:-(
xternal Contacts are displayed with an unfriendly name (it appears to be their SMTP address). Typically there is no easy way to determine the person with just this address when looking for their entry in the Contacts list. We previously used Skype For Business and this displayed external contacts with a Friendly Name but after we were forced into using Teams, this functionality was lost.