Others

How to Use an Unlicensed Microsoft 365 User as a Mailbox Alias

Khadija Khan Oct 12, 2026 868 views

Question details

The user wants to configure a synchronized on-premises Active Directory user's UPN as an email alias for another Microsoft 365 mailbox, noting that the account does not have an Exchange Online license.

Using an Unlicensed Microsoft 365 User as a Mailbox Alias

Product: Microsoft 365
Device & OS: not provided
Scenario: Attempting to reassign a User Principal Name (UPN) from an unlicensed synchronized on-premises directory account as a proxy address or alias to a different Microsoft 365 mailbox.
Observed behavior: The system blocks the UPN from being directly added as an alias to another mailbox, demonstrating that the lack of an Exchange Online license does not automatically free up the UPN for reuse.

Before you start

Ensure you have global administrator or Exchange administrator privileges in your Microsoft 365 tenant to modify directory synchronization and recipient configurations.

Solution 1Recommended

Review Directory Sync and Exchange Recipient Configuration

Address identity conflicts by adjusting proxy addresses through your on-premises Active Directory or Microsoft 365 Admin Center.

A synchronized on-premises Active Directory account retains its unique UPN in the cloud, even without an Exchange Online license. To use this UPN as an alias for another account, you must properly resolve the identity conflict at the synchronization source.

Verify on-premises Active Directory attributes

Open your on-premises AD environment and review the 'proxyAddresses' and 'userPrincipalName' attributes for the unlicensed user. Ensure the address you wish to use as an alias is not currently bound to this active user.

Consult the Exchange Admin Center

Log in to the Microsoft 365 Exchange Admin Center. Navigate to Recipients > Mailboxes, and check for any existing proxy address conflicts tied to the UPN.

Update the identity design

Work with your IT administrators to change the original user's UPN or remove the account from the synchronization scope. Once the Azure AD Connect sync completes and the UPN is released, you can assign it as an alias to the target Microsoft 365 mailbox.

Review Directory Sync and Exchange Recipient Configuration

Synchronization Delay: Changes made in your on-premises Active Directory may take up to 30 minutes to reflect in Microsoft 365 via Azure AD Connect.

Free Microsoft Office alternative

Try WPS Office as Your Lightweight Productivity Solution

While managing Microsoft 365 exchange aliases requires complex IT configurations, your everyday document work shouldn't be complicated. WPS Office provides a free, highly compatible, and lightweight alternative to Microsoft Office for all your personal and professional document needs.

1. Download WPS Office: Visit the official WPS website and click the free download button for your operating system.
2. Install the application: Follow the straightforward on-screen instructions to install the software on your device.
3. Open your files: Launch WPS Office and seamlessly open your existing Microsoft Office documents without format loss.

Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx)Lightweight software with rapid startup times that won't slow down your deviceFamiliar, easy-to-use tabbed interface for seamless multitaskingEffortless migration from other office suites with no learning curve required

microsoft office alternative - wps office

Frequently Asked Questions

Why does Microsoft 365 block adding an unlicensed synced user's UPN as an alias?

Microsoft 365 maintains strict directory synchronization rules. Even without an Exchange Online license, a synchronized on-premises Active Directory account is a recognized identity in Azure AD. This prevents its UPN from being assigned as a proxy address or alias to another mailbox to avoid routing conflicts.

Can I delete the synced user to free up the UPN for an alias?

Yes. If the user is removed from the on-premises Active Directory and the deletion synchronizes to Microsoft 365, the UPN will be released. However, this permanently removes the user's identity and access, which should only be done if the original account is no longer needed.

How do I correctly set up a shared email address instead of moving aliases?

Instead of reassigning an existing UPN as an alias, consider creating a Shared Mailbox or a Microsoft 365 Group in the Exchange Admin Center. This allows multiple licensed users to access and send emails from a single address without creating directory synchronization conflicts.

Office Quick Solutions