This guide walks you through diagnosing and fixing missing mail aliases and shared mailboxes after a Microsoft 365 migration. You’ll learn where these objects live in the admin center, how to verify they actually migrated, and the exact PowerShell commands to restore them when the GUI shows nothing.
What You’ll Need
- Global admin or Exchange admin access to the Microsoft 365 admin center
- PowerShell installed (Windows PowerShell 5.1 or PowerShell 7)
- The
ExchangeOnlineManagementmodule installed (runInstall-Module -Name ExchangeOnlineManagementif missing) - Your migration source details (tenant name, CSV export, or old server records) to compare against
Step-by-Step
- Confirm the migration actually completed. Go to Admin centers > Exchange > Migration and check the status of your batch. If it shows “Failed” or “Synced with errors,” resolve those first—missing aliases often come from incomplete syncs.
- Check the recipient list in the new tenant. In the Exchange admin center, go to Recipients > Mailboxes and Recipients > Shared. Look for the specific mailbox or shared mailbox that’s missing aliases. If the mailbox itself is absent, the migration didn’t create it—skip to Step 6.
- Open the mailbox’s properties. Double-click the mailbox, then select Email options (or Email addresses in older UI). You’ll see a list of SMTP addresses. The primary address is the one in bold; all others are aliases. If you see only the primary, the aliases were not migrated.
- Compare against your source. Pull the alias list from your old system. If you have a CSV export from the source (e.g., from a previous PowerShell script), compare the two lists. Common mismatches: aliases that were on the source but not on the target, or aliases that got renamed during migration.
- Re-add missing aliases via the GUI (quick fix). In the mailbox properties, click + Add, type the alias, choose the domain (e.g.,
@contoso.com), and save. Repeat for each missing alias. This works for both user mailboxes and shared mailboxes. - Use PowerShell for bulk restoration. If many aliases are missing, run this in Exchange Online PowerShell:
Connect-ExchangeOnline
Then for a single mailbox:Set-Mailbox -Identity "user@contoso.com" -EmailAddresses @{Add="alias1@contoso.com","alias2@contoso.com"}
For a shared mailbox:Set-Mailbox -Identity "shared@contoso.com" -EmailAddresses @{Add="alias1@contoso.com"}
To add aliases from a CSV file, loop through the rows withForEach. - Verify the shared mailbox is actually a shared mailbox. In Exchange admin, check Recipients > Shared. If the object exists but appears as a regular user mailbox, the migration may have created it as a user. Convert it with:
Set-Mailbox -Identity "shared@contoso.com" -Type Shared - Check for domain/tenant routing issues. If the alias domain (e.g.,
@oldcompany.com) isn’t a verified domain in the new tenant, Exchange will silently drop aliases using that domain. Go to Admin centers > Settings > Domains and verify all source domains are added and verified. - Wait for directory synchronization. If you’re syncing from on-premises Active Directory, changes can take up to 30 minutes. Force sync with:
Start-ADSyncSyncCycle -PolicyType Delta
Then re-check the aliases. - Check for duplicate alias conflicts. If an alias already exists on another mailbox in the target tenant, the migration will skip it. Search for the alias across all recipients:
Get-Recipient -ResultSize Unlimited | Where-Object {$_.EmailAddresses -match "alias@contoso.com"}
If found, remove it from the conflicting mailbox first, then add it to the intended one.
Common Mistakes
- Forgetting to verify domains. Aliases pointing to unverified domains are silently dropped. Always add and verify every source domain in the new tenant before migration.
- Confusing primary SMTP with aliases. The primary address is not an alias. If you only see the primary, that’s normal—aliases are additional addresses.
- Using the wrong PowerShell parameter.
-EmailAddressesreplaces the entire list. Using@{Add=...}adds to the existing list; using a plain string overwrites everything, wiping remaining aliases. - Editing the wrong mailbox type. Shared mailboxes are managed under Recipients > Shared, not Mailboxes. Editing a shared mailbox as a user mailbox can change its type.
- Assuming the migration tool copies everything. Most migration tools copy mailbox content (email, calendar) but may not copy SMTP aliases unless explicitly configured. Always review the migration settings for “email address” or “proxy address” options.
Tips
- Export aliases before migrating. Run
Get-Mailbox -ResultSize Unlimited | Select-Object Identity, EmailAddresses | Export-Csv aliases.csvon the source to have a backup list. - Use a migration CSV. If you’re doing a cutover or staged migration, include a column for aliases in your CSV and map it in the migration endpoint.
- Test with a single mailbox first. Migrate one mailbox, verify aliases, then run the full batch. This catches configuration issues early.
- Document all aliases in a central spreadsheet. This makes post-migration verification faster and helps when users report missing addresses.
- Schedule a verification script. After migration, run a PowerShell script that compares the source CSV to the target and outputs any missing aliases.
Troubleshooting
Aliases still missing after re-adding them? Wait 15–30 minutes for replication. If they disappear again, check if a user or group has the same alias—Exchange will remove duplicates automatically.
PowerShell says “The operation couldn’t be performed because the object couldn’t be found.” This usually means the mailbox identity is wrong. Use the full primary SMTP address or the GUID from the admin center.
Shared mailbox won’t accept aliases. Ensure the mailbox is not in a “soft-deleted” state. Check Get-Mailbox -SoftDeletedMailbox and restore it if needed.
Aliases appear in PowerShell but not in Outlook. Outlook caches the GAL (Global Address List). Rebuild the offline address book by running Update-OfflineAddressBook -Identity "Default Offline Address Book" in Exchange Online PowerShell.
Migration batch shows “Completed with warnings.” Click the batch and review each row’s error details. The warning often says “proxy address was skipped” or “duplicate address ignored.”
Frequently Asked Questions
Why did aliases disappear during migration?
Most often because the target domain wasn’t verified, the migration tool wasn’t configured to copy proxy addresses, or the alias already existed on another object in the new tenant.
Can I add aliases to a shared mailbox without PowerShell?
Yes. In Exchange admin center, go to Recipients > Shared, open the mailbox, select Email options, and add the alias manually.
Do aliases affect mailbox size or licensing?
No. Aliases are just additional SMTP addresses pointing to the same mailbox. They don’t consume extra storage or require additional licenses.
How do I find all mailboxes with a specific alias?
Run Get-Recipient -ResultSize Unlimited | Where-Object {$_.EmailAddresses -contains "SMTP:alias@domain.com"} in Exchange Online PowerShell.
Can I migrate aliases from Google Workspace or on-premises Exchange?
Yes, but you must export them first. For on-prem Exchange, use Get-Mailbox | Select-Object -ExpandProperty EmailAddresses. For Google Workspace, use the Admin SDK to export aliases, then add them manually or via CSV import.
What if the alias domain is not in my new tenant?
Add the domain in Microsoft 365 admin center and verify it (DNS TXT record). Until verified, Exchange will not accept aliases using that domain.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix msmpeg2vdec.dll Errors in Windows
- How to Update Sonos App and Speakers
- Unlock iPad Without Apple ID: Is It Possible?
- iOS 18 WhatsApp Notifications Not Working? Fix
- Fix Windows Cannot Locate Suitable Printer Driver
- Monster Hunter World PC Crash: Solved?