Outlook 2019 Autocomplete not accessing contacts from Exchange account. Not by name?

%3CLINGO-SUB%20id%3D%22lingo-sub-1280408%22%20slang%3D%22en-US%22%3EOutlook%202019%20Autocomplete%20not%20accessing%20contacts%20from%20Exchange%20account.%20Not%20by%20name%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1280408%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20away%20from%20Outlook%20for%20a%20while%20personally%2C%20using%20emClient%2C%20and%20the%20Outlook%20web%20app.%3C%2FP%3E%3CP%3ENow%20using%20Outlook%202019%20I%20find%20that%20the%20Autocomplete%20doesn't%20work%20out-of-the-box%2C%20by%20Name%2C%20really%3F%3C%2FP%3E%3CP%3EI%20have%20maybe%20900%20contacts%2C%20and%20they%20must%20be%20accessed%20by%20name%20from%20the%20%5B%20TO%20%5D%20dialog%20box%20opening%20for%20each%20email%20sent.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat's%20worse%2C%20recipients%20that%20have%20been%20sent%20messages%20don't%20autocomplete%20by%20name%2C%20keying%20in%20their%20(familiar)%20name%20on%20the%20empty%20To%20field%20displays%20the%20contact's%20email%20address%2C%20not%20their%20name.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20remedy%20for%20this%3F%26nbsp%3B%20I%20can%20install%20an%20app%20like%20emClient%20on%20a%20customer's%20PC%2C%20ad%20the%20Exchange%20account%2C%20and%20the%20first%20email%20sent%20recognizes%20and%20displays%20a%20recipient's%20full%20name%20(from%20the%20Exchange%20acct).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1281400%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%202019%20Autocomplete%20not%20accessing%20contacts%20from%20Exchange%20account.%20Not%20by%20name%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1281400%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20it%20looks%20like%20one%20must%20go%20through%20each%20and%20every%20contact%20manually%20(from%20within%20Outlook)%20and%20fix%20the%20'Display%20as'%20for%20each%20contact%2C%20like%3A%20Recipient%20Name(recipient%40domain.com).%26nbsp%3B%3C%2FP%3E%3CP%3ESteps%3A%3C%2FP%3E%3CP%3E1.%20Delete%20the%20current%20Display%20As%20field%20contents%2C%20tab%20to%20next%20field.%3C%2FP%3E%3CP%3E2.%20After%20tabbing%20away%2C%20the%20Display%20As%20field%20is%20updated%20to%20show%20'recipient%20name%20-%20company(email%20address)'.%3C%2FP%3E%3CP%3E3.%20Save%20contact.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EAfter%20this%20fix%2C%20the%20Autocomplete%20operates%2C%20despite%20the%20fact%20the%20contact%20has%20not%20been%20used%20to%20send%20an%20email.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EYou%20wouldn't%20expect%20MS%20Outlook%20to%20have%20an%20issue%20with%20the%20in-place%20contact%20data%20in%20an%20O365%20Exchange%20account...%26nbsp%3B%20Am%20I%20missing%20something%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I've been away from Outlook for a while personally, using emClient, and the Outlook web app.

Now using Outlook 2019 I find that the Autocomplete doesn't work out-of-the-box, by Name, really?

I have maybe 900 contacts, and they must be accessed by name from the [ TO ] dialog box opening for each email sent.

 

What's worse, recipients that have been sent messages don't autocomplete by name, keying in their (familiar) name on the empty To field displays the contact's email address, not their name.  So a contact like Ted Smith with an email address like maintenance@cherryhill.com displays no clue to the contact's name.

 

Is there a remedy for this?  I can install an app like emClient on a customer's PC, add the Exchange account, and the first email sent recognizes and displays a recipient's full name (from the Exchange acct).

1 Reply
Highlighted

So it looks like one must go through each and every contact manually (from within Outlook) and fix the 'Display as' for each contact, like: Recipient Name(recipient@domain.com). 

Steps:

1. Delete the current Display As field contents, tab to next field.

2. After tabbing away, the Display As field is updated to show 'recipient name - company(email address)'.

3. Save contact.

After this fix, the Autocomplete operates, despite the fact the contact has not been used to send an email.

You wouldn't expect MS Outlook to have an issue with the in-place contact data in an O365 Exchange account...  Am I missing something?