Team address books (and company-wide address book)
The lifeblood of Microsoft teams is the people that that make up those teams and generate the content within teams. As of now, there is now basic way of listing who those people are within teams.
It would be really great if each team had it's own "people" tab where it would be an address book of all the people who make up that team. Without it, how does a general user even know with whom they are speaking?
Furthermore, it would be good to have the option for a company-wide "people" tab in the left menu, which would function as a general address book.
These features are out-of-the-box options for most other company communication systems and I don't understand why it's not really an option.
Nick Moss commented
Yes this would be a super useful feature
Making Teams more about TEAMS is what Teams should be all about.
A must have surely!
Michael Beaud commented
Absolutely necessary feature for our customers to be able to use MS Teams VoIP. Without this feature we can't implement Teams for our customers.
It is critical to be able to call external contacts via Teams and to be able to see a callers ID for incoming calls.
GAL is a basic core requirement - please add asap
Alex Stender commented
Shouldn't be big challenge for Microsoft to extend the address book functionality and allow Teams to connect with a shared address book or GAL. Right?
Jonathan Lisimaque commented
MS, fix it please !
This feature has to be added!!!!
We have a cutomer that has over 1000 regular callers, but they need to see the callers name when they call and not just the number. This is a fairly basic feature and offered by all the other VOIP solutions we have looked at. This is a major requirement so expect they will go for another provider.
This is an absolutely fundamental Function. Please fix it!
Martin Elliott commented
Skype for Business could point to a shared contract lost, so why did this functionality not get included in Teams? Come on Microsoft listen to the users who pay your salaries!
James Smith commented
I noticed today that about a day after adding a new contact under Users->Contacts in the Microsoft 365 admin center, Teams started recognizing the inbound calls from the mobile number I set for the contact and properly showing the display name I had set.
(I set the mobile number for the contact in this format: +1 xxx-xxx-xxxx [US Phone Number])
(Contact shows as "In Cloud" for the Sync Status on this page.)
This seems promising.
I'm going to check to see if the contacts that are being synced from AD will also be recognized by Teams. (May have to change the AD attribute msExchHideFromAddressList from True to False to unhide some of my contacts from the GAL.)
If this also works, then the next challenges would be:
1. See if there is a way to convert synced contacts to cloud-only contacts (Not really an issue if we can bulk select and delete synced contacts when we decide to remove on-prem AD sync.)
2. Figure out if/how to speed up changes in Office365. (Waiting a day or more for updates to take is not really sustainable for a large corporation.)
Syncing contacts that were created directly in AD does not work. (Pure AD-created contacts do not sync to O365.) It only seems to work if the contact is created from our on-prem Exchange server.
So it looks like if you don't have an on-prem Exchange server which is syncing to O365, then the only method is to bulk upload contacts in csv format, and have an admin update them from the O365 admin center every time there is a change.
So, while inbound caller ID seems to be working against this Contacts list in O365, it still don't allow searching this contact list from within the Teams app to place Outbound calls.
This is an absolutely fundamental Function to be able to call out from a company-wide adress book!!! And to get the call-ID-s sorted with name and company when some known contact are calling us over PSTN!!! Please fix this ASAP!
Kevin Elsden commented
Skype for Business provided the capability to look up contacts in the GAL, but teams doesn't. The absence of this feature is a huge problem for organizations who have multiple M365 tenants but have an amalgamated GAL across those tenants. We are suffering a major backlash from our users since we migrated from SfB to Teams. This is an obvious feature that is missing, in fact I think it's so fundamental that it feels wrong to even refer to it as a "feature", it is essential functionality.
Please get this on the roadmap ASAP
Mike van Gemund commented
and to add: more importantly for CALL QUEUES (the former Skype response groups). Try finding one, especially if you are a large corporate with a complicated naming convention...there is no 'Binging' possible.. The search for a 'headset icon' (which is the right contact associated with the call queue) is problematic. We filled the First Name and Last Name fields of the associated account with handy key-words, and that helped. But it only searches for ONE word per field, AND the word must be 6 digits or longer...
Richard Simcox commented
looking at the roadmap this isnt even considered and users have been wanting it for over a year
Must have in Microsoft Teams
Will be helpful for MS Voiceservices in Teams so you can call customers easiler a.s.o.
So the whole company can us one actual Phonebook
/sign just to get some attention from MS for this topic
I just had a Microsoft Engineer suggest that I provide users with instructions of how to add contacts via Teams as a workaround to not being able to centrally configure firm-wide Teams contacts. I cannot understand why having a single shared GAL is not a given