Share an Email Domain Between Microsoft 365 and FirstClass
Question details
The organization needs to route mail for one domain to both Microsoft 365 and FirstClass during a mailbox migration.

- Product
- Microsoft 365 Exchange Online and OpenText FirstClass
- Device & OS
- not provided
- Scenario
- Some mailboxes have moved to Microsoft 365 while others remain on FirstClass, and both groups use the same email domain.
- Observed behavior
- Microsoft 365 connector validation fails when the test recipient exists only on FirstClass.
Identify which system currently receives the domain's MX traffic, the FirstClass mail server's reachable host name, and a working FirstClass-only test address. Confirm that FirstClass can route mail for migrated users to Microsoft 365 without sending it back in a loop.
Configure shared-domain routing for Exchange Online and FirstClass
Use an internal relay domain and an outbound connector to deliver mail for FirstClass-only recipients while piloting Microsoft 365 mailboxes.
Keep the existing MX record pointed at the current receiving system during the pilot unless your routing design requires a change. Domain verification can generally be completed with a DNS TXT record.
Both systems must route only the appropriate recipients to the other system. If FirstClass cannot selectively forward migrated recipients, use a suitable mail relay or redesign the routing before testing.
In the Microsoft 365 admin center, go to Settings > Domains, add the shared domain if needed, and follow the DNS verification instructions. Review proposed DNS changes before applying them.
In the Exchange admin center, go to Mail flow > Accepted domains, select the shared domain, and set its domain type to Internal relay. This allows Exchange Online to route recipients it does not host to another mail system.
Go to Mail flow > Connectors and add a connector from Microsoft 365 to your organization's email server. Scope it to the shared domain and enter the reachable FirstClass server or relay as the smart host; configure TLS to match the receiving server.
In FirstClass or the current inbound mail relay, configure migrated Microsoft 365 recipients to be forwarded to the tenant's Exchange Online mail endpoint. Keep FirstClass recipients local and prevent unknown addresses from bouncing repeatedly between the systems.
In the connector setup, validate using a working address hosted only on FirstClass. If validation fails, review the reported error and check smart-host DNS, SMTP connectivity, TLS settings, and FirstClass recipient acceptance. Test mail to recipients on both systems and from an external sender.

Work with Office files in WPS Office during your migration
WPS Office is a free, lightweight alternative with familiar document, spreadsheet, and presentation tools. Its Microsoft Office format compatibility helps users move their everyday file work with minimal disruption. WPS Office does not configure Microsoft 365 or FirstClass email routing.

Frequently Asked Questions
Do I have to change the domain's MX record during the pilot?
Not necessarily. If the current receiving system can route migrated users to Microsoft 365, you can keep the existing MX record during the pilot. Verify the domain using the DNS method shown under Settings > Domains in the Microsoft 365 admin center.
Why should the shared domain be set to internal relay?
Internal relay allows Exchange Online to route mail for recipients it does not host to another mail system. Set it under Mail flow > Accepted domains, and configure an outbound connector for the shared domain.
Why does validation fail for a FirstClass-only address?
The address can be a valid test recipient if it is reachable through the connector. Check the validation error for smart-host DNS, SMTP connectivity, TLS, or recipient acceptance issues, and confirm the receiving server accepts mail for that address.
How can I avoid a mail loop between the two systems?
Configure the current inbound system to forward only migrated recipients to Microsoft 365, while keeping FirstClass recipients local. Ensure unknown recipients are rejected or otherwise handled rather than repeatedly relayed between the systems.
Does WPS Office migrate FirstClass mailboxes?
No. WPS Office provides document, spreadsheet, and presentation tools; mailbox migration and shared-domain routing must be handled in Microsoft 365, FirstClass, or an appropriate migration service.




