Windows OS Hub
  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu

 Windows OS Hub / Outlook / Outlook: The Name Cannot Be Matched to a Name in the Address List

February 28, 2022 ExchangeMicrosoft 365Office 365Outlook

Outlook: The Name Cannot Be Matched to a Name in the Address List

In some cases, when you try to connect a new mailbox hosted on an on-premises Exchange Server or Microsoft 365 (Exchange Online), Outlook shows the following error after you enter your email address and password (or after Autodiscovery is done):

The action cannot be completed. The name cannot be matched to a name in the address list.

Outlook error: The name cannot be matched to a name in the address list

This problem when connecting a mailbox in Outlook may have different reasons. Let’s try to list the most obvious ones.

If a user mailbox has been created recently, you may just need to wait a while before connecting it in Outlook.

Then make sure that the user mailbox is not hidden from the address book. In on-premises Exchange, you need to connect to the Exchange Server host server using PowerShell and run the command below:
Get-Mailbox -Identity k.peterson | Select DisplayName,UserPrincipalName, HiddenFromAddressListsEnabled

If the user is hidden, disable this attribute with the following command:

Set-Mailbox -Identity k.peterson -HiddenFromAddressListsEnabled $false

In Exchange Online (Microsoft 365), you can enable or disable the Hide from address list attribute in Microsoft 365 admin center.

Click Users -> Active Users -> find the user -> Mail -> Edit Exchange Properties. You will be forwarded to Exchange Admin Center (EAC).

microsoft 365 edit exchange user properties

Uncheck the Hide from address lists option.

disable the Hide from address list option

Or, you can clear the HiddenFromAddressListsEnabled attribute via PowerShell using the Set-Mailbox cmdlet (after connecting to an Exchange Online tenant with EXOv2 PowerShell module).

After a while, make sure the user is displayed in the Exchange address book (Global Address List). Connect the Exchange mailbox in Outlook.

If it did not help, remove all saved credentials related to Microsoft Office in Windows Credential Manager (Control Panel -> User Accounts -> Credential Manager -> Windows Credentials).

office 365 clear cached credentials

Delete saved data under the HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity registry key and restart your computer.

remove the office 365 mailbox cached data in registry

Try to create a new e-mail profile in Outlook (Control Panel -> Mail) and connect to your Exchange mailbox.

In on-premises Exchange, make sure if the showInAddressBook user attribute has correct values. Open it in the AD Attribute Editor to make sure that at least two DNs are set:

  • CN=All Users,CN=All Address Lists,CN=Address Lists Container,CN=…
  • CN=Default Global Address List,CN=All Global Address Lists,CN=…

Compare the values with those of other users.

Also, make sure that the following user attributes are filled in and consistent: LegacyExchangeDN, homeMDB, homeMTA, mail, mailNickname, msExchHomeServerName, msExchMailboxGuid, msExchMailboxSecurityDescriptor, proxyAddresses.

If the problem occurs only in Outlook 2019 or Outlook 2016 and the mailbox is located on the on-prem Exchange server, then disable Office 365 AutoDiscover using the ExcludeExplicitO365Endpoint registry parameter:

reg add HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\AutoDiscover /t REG_DWORD /v ExcludeExplicitO365Endpoint /d 1

The ExcludeExplicitO365Endpoint attribute was described in detail in the article Outlook continually prompts for password.

Restart your computer. Outlook should now be able to discover your on-premise Exchange without any problems.

0 comment
1
Facebook Twitter Google + Pinterest
previous post
Search and Delete Emails from User Mailboxes on Exchange Server (Microsoft 365) with PowerShell
next post
Installing PowerShell Core on Linux Distros

Related Reading

Fix: “Something Went Wrong” Error When Installing Teams

May 2, 2023

Send Outlook Emails Using Excel VBA Macro or...

April 11, 2023

Send from Alias (SMTP Proxy Address) in Exchange...

April 6, 2023

How to Use Plus Addressing in Microsoft 365...

April 5, 2023

Save Sent Items in Shared Mailbox on Exchange...

April 3, 2023

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange Server
  • Microsoft 365
  • Azure
  • Windows 11
  • Windows 10
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • PowerShell
  • VMWare
  • Hyper-V
  • Linux
  • MS Office

Recent Posts

  • Configuring Event Viewer Log Size on Windows

    May 24, 2023
  • How to Detect Who Changed the File/Folder NTFS Permissions on Windows?

    May 24, 2023
  • Enable Single Sign-On (SSO) Authentication on RDS Windows Server

    May 23, 2023
  • Allow Non-admin Users RDP Access to Windows Server

    May 22, 2023
  • How to Create, Change, and Remove Local Users or Groups with PowerShell?

    May 17, 2023
  • Fix: BSOD Error 0x0000007B (INACCESSABLE_BOOT_DEVICE) on Windows

    May 16, 2023
  • View Success and Failed Local Logon Attempts on Windows

    May 2, 2023
  • Fix: “Something Went Wrong” Error When Installing Teams

    May 2, 2023
  • Querying Windows Event Logs with PowerShell

    May 2, 2023
  • Configure Windows LAPS (Local Administrator Passwords Solution) in AD

    April 25, 2023

Follow us

  • Facebook
  • Twitter
  • RSS
Popular Posts
  • Outlook Keeps Asking for Password on Windows
  • How to Manually Configure Exchange or Microsoft 365 Account in Outlook 365/2019/2016?
  • Whitelist Domains and Email Addresses on Exchange Server and Microsoft 365
  • Moving Exchange Mailboxes to Different Database
  • FAQ: Licensing Microsoft Exchange Server 2019/2016
  • How to Cleanup, Truncate or Move Log Files in Exchange Server 2013/2016/2019?
  • Search and Delete Emails from User Mailboxes on Exchange Server (Microsoft 365) with PowerShell
Footer Logo

@2014 - 2023 - Windows OS Hub. All about operating systems for sysadmins


Back To Top