Outlook Cannot Send From Alias After Tenant Change: Fix

After a Microsoft 365 tenant change, such as a domain migration or tenant-to-tenant migration, some users cannot send email from an alias address in Outlook. The error typically says the message cannot be sent because the account does not have permission to send from that address. This problem occurs because the alias is not properly linked to the user’s mailbox in the new tenant environment. This article explains why the alias fails after a tenant change and provides the exact steps to restore sending from aliases in Outlook.

Why Sending From an Alias Fails After a Tenant Change

When a tenant change occurs, the user object and its associated mailbox move to a new Exchange Online organization. The alias addresses are usually migrated correctly as proxy addresses on the user object. However, the send-as permission that Outlook relies on to allow sending from an alias is not automatically transferred. Outlook stores the alias as a send-as identity in the user’s profile, but after the tenant change, the underlying permission is missing or points to a now-invalid object ID. Exchange Online checks the send-as permission on the mailbox where the alias resides. If that permission is not present, Outlook rejects the attempt to send from the alias.

Another common root cause is that the alias is still configured as a shared mailbox or distribution group in the old tenant. Even though the user object moved, the alias resource may not have been migrated. The new tenant sees the alias as an external address and blocks sending from it. In less common cases, the Outlook profile retains stale autocomplete cache entries that map the alias to an old routing address, causing a delivery failure.

Steps to Fix Send-From-Alias After Tenant Change

Follow these steps in order. Do not skip any step.

1. Verify the alias exists as a proxy address on the user mailbox
   Sign in to the Exchange Admin Center at admin.exchange.microsoft.com. Go to Recipients > Mailboxes. Select the affected user. Click Mailbox and then Email addresses. Confirm the alias email address is listed as an SMTP proxy address. If not, click Add, select SMTP, enter the alias, and set the type to Proxy. Save the changes.
2. Grant send-as permission for the alias on the user mailbox
   In the same Exchange Admin Center, with the user mailbox still open, go to Mailbox delegation. Under Send As, click Edit. Add the user’s own primary SMTP address. This grants the user permission to send as the alias. Click Save. Wait 15 minutes for replication.
3. Clear the Outlook autocomplete cache
   Open Outlook. In a new email message, start typing the alias address. If a suggestion appears, highlight it and press Delete on your keyboard. This removes any stale cache entry. Alternatively, go to File > Options > Mail. Under Send messages, click Empty Auto-Complete List. Click Yes.
4. Remove and re-add the alias in Outlook account settings
   Go to File > Account Settings > Account Settings. Select your Exchange account and click Change. Click More Settings. Go to the Advanced tab. Under Open these additional mailboxes, remove any entry that matches the alias. Click OK. Then click Next and Finish. Restart Outlook. Open Account Settings again, click Change, More Settings, Advanced. Under Open these additional mailboxes, add the alias email address. Click OK, Next, Finish. Restart Outlook.
5. Rebuild the Outlook profile if the alias still fails
   Close Outlook. Open Control Panel. Set View to Small icons. Click Mail (Microsoft Outlook). Click Show Profiles. Select your profile and click Remove. Click Yes. Open Outlook again and create a new profile using the primary email address. After the profile is created, go to Account Settings and add the alias under Open these additional mailboxes as described in step 4.

If Outlook Still Cannot Send From the Alias

The alias was a shared mailbox in the old tenant

If the alias was previously a shared mailbox with its own mailbox in the old tenant, that shared mailbox may not have been migrated. In the new tenant, create a new shared mailbox with the alias address. Then grant the user full access and send-as permission to that shared mailbox. The user must add the shared mailbox to Outlook using File > Account Settings > Account Settings > Change > More Settings > Advanced > Open these additional mailboxes.

Outlook shows a permission error even after permissions are assigned

This usually means the permissions have not replicated to all Exchange Online servers. Wait 60 minutes and try again. If the error persists, remove the user from the send-as permission, save, then add the user back. This forces a fresh replication. You can also use the Exchange Online PowerShell cmdlet Add-RecipientPermission with the -Trustee parameter to verify the permission exists.

The alias sends but the recipient sees a different from address

This indicates the alias is not set as the primary send-from address in Outlook. When composing a new email, click the From button in the message window. Select Other Email Address. Type the alias address manually. The alias must be selected each time you send from it. To make it the default, you cannot change the default from address for an Exchange account in Outlook; you must use the alias as the primary SMTP address in Exchange Admin Center.

Item	Tenant Change Before Fix	Tenant Change After Fix
Alias permission	Missing or points to old tenant object	Granted on the user mailbox in new tenant
Outlook profile	Stores stale alias mapping	Fresh profile with correct permissions
Autocomplete cache	Contains old routing address	Cleared and rebuilt with new tenant data
Shared mailbox (if applicable)	Not migrated or missing permissions	Created in new tenant with full access

You can now send email from an alias address in Outlook after a tenant change. Verify the fix by sending a test message to a secondary account and checking the From header. If you manage multiple users, consider exporting the alias list from the old tenant and importing it as proxy addresses in the new tenant before granting permissions. This prevents missing alias issues across your organization.