Others

Fix Duplicate Alias Errors When Creating an Exchange Online Shared Mailbox

Ayan MasoodAyan Masood Nov 20, 2026 869 views

Question details

Create a shared mailbox when Exchange Online reports a conflicting alias or address.

Fix Duplicate Alias Errors When Creating an Exchange Online Shared Mailbox
Product
Microsoft Exchange Online
Device & OS
not provided
Scenario
An administrator is creating a shared mailbox, potentially using an address on a secondary domain.
Observed behavior
Mailbox creation may be blocked because an alias, SMTP or proxy address, or LegacyExchangeDN conflicts with an existing recipient.
Before you start

Note the desired mailbox name, alias, and full SMTP address, including its domain. Sign in with an account that can view and manage Exchange recipients; for PowerShell searches, connect to Exchange Online.

Solution 1Recommended

Find and resolve conflicting recipient addresses

Use this approach when Exchange reports that an alias or address is already assigned.

1
Search for the recipient

In the Exchange admin center, open Recipients and search mailboxes, groups, and contacts for the intended name and address. Also check mail-enabled public folders if they are used in your organization.

2
Inspect aliases and addresses

Open any matching recipient and review its alias and email addresses. Check secondary SMTP addresses as well as the primary address; the complete SMTP address must be unique across recipients.

3
Search with PowerShell

In Exchange Online PowerShell, run Connect-ExchangeOnline, then replace the example values and run: Get-Recipient -ResultSize Unlimited | Where-Object { $_.Alias -eq 'reception' -or @($_.EmailAddresses | ForEach-Object { $_.ToString() }) -contains 'smtp:reception@example.com' }. Review any returned recipients.

4
Check a legacy address if reported

If the error identifies a LegacyExchangeDN, set $legacy to that exact value and run: Get-Recipient -ResultSize Unlimited | Where-Object { $_.LegacyExchangeDN -eq $legacy -or @($_.EmailAddresses | ForEach-Object { $_.ToString() }) -contains ('X500:' + $legacy) }. Review any matching recipient before changing it.

5
Resolve the conflict

In the Exchange admin center, edit the conflicting recipient's email addresses or alias only if the value is no longer needed. Then return to Recipients > Mailboxes and retry creating the shared mailbox.

Find and resolve conflicting recipient addresses
Preserve addresses that are still needed: Removing an SMTP or X500 address can disrupt mail delivery or replies to older messages. Confirm its purpose before removing it, and investigate deleted or inactive recipients if no active recipient appears in the search.
Free Microsoft Office alternative

Use WPS Office for Documents While Managing Exchange Online

Exchange Online mailbox conflicts must be resolved in Microsoft administration tools. For everyday documents and spreadsheets, WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility for an easy transition.

Document mailbox setup and troubleshooting notes in WPS WriterOpen and edit Microsoft Word DOCX and Excel XLSX filesUse familiar document and spreadsheet tools in a lightweight suiteMove existing Office files into your WPS workflow
microsoft office alternative - wps office

Frequently Asked Questions

Can two shared mailboxes use the same address on different domains?

Addresses such as reception@example.com and reception@example.net are different full SMTP addresses. Each must be available, and mailbox aliases and other identifiers must also meet Exchange Online's uniqueness requirements.

Where can I check a recipient's secondary email addresses?

In the Exchange admin center, open Recipients, select the mailbox, group, or contact, and review its email addresses. Secondary SMTP addresses can conflict even when they are not the primary address.

Will changing the mailbox display name fix a duplicate SMTP address?

No. Edit the display name from the mailbox properties if needed, but resolve the conflicting SMTP address separately before assigning it to the new mailbox.

Why should I check X500 addresses for a LegacyExchangeDN conflict?

A former recipient's LegacyExchangeDN can be retained as an X500 proxy address on another recipient. Search both the LegacyExchangeDN property and X500 proxy addresses, and do not remove an X500 address without checking whether it is needed for replies to older messages.