Run regedit as the affected user on the client. Prevent the Office 365 AutoDiscover and Outlook 2019 appears to find the on-premise Exchange server without issue. Outlook 2019 seems to prioritize IMAP, POP3, and then default to Office365 before even attempting on-premise AutoDiscover discovery. Using the in Outlook “Test Email AutoConfiguration” (via the Outlook tray icon, Ctrl+Shift Right click, Test Email AutoConfiguration) fails showing a connection attempt to “” and “” and various connections to * and AutoDiscover to which is incorrect since the account is not on Office 365. The on-premise domain has correct DNS entries for AutoDiscover the Microsoft Remote Connectivity Analyzer connects fine. Adding Exchange account gives “The name cannot be matched to a name in the address list.” which is caused by Outlook being unable to find the user in Office 365. When the client is running Office 2016 or earlier, the problem does not occur. 
Client running Windows 10 with Outlook 2019, not domain joined.Server is onsite/local Exchange 2016 or Exchange 2019 without Office 365.The ADSIEdit data displayed for the affected user shows that the user is properly listed in the necessary Address Lists.The account is properly listed in the Global Address List, not hidden.While adding an Exchange account in Outlook 2019, you enter the email address and user credentials then receive the message “The name cannot be matched to a name in the address list.”
The issue only occured with Office 2019 or newer.
I had a user unable to connect to my on-premise Exchange server. Microsoft Outlook 2019 unable to connect to on-premise Exchange Server "The name cannot be matched to a name in the address list."
0 kommentar(er)
