Fix an IMAP Migration Endpoint Error in Microsoft 365
Question details
The user needs to create an IMAP migration endpoint in Microsoft 365 for a FuseMail migration.

- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- Creating and testing an IMAP migration endpoint in the Exchange Online interface and PowerShell.
- Observed behavior
- Both Microsoft 365 methods fail because the IMAP server returns a BAD response to the ID command, although third-party tools can connect.
Confirm the source IMAP server name, port, encryption setting, and mailbox credentials with the email provider. You will also need an account with permission to manage Exchange Online migrations.
Test the IMAP server and create a new endpoint with PowerShell
Use Exchange Online PowerShell to retest the connection and collect details if endpoint creation still fails.
Open PowerShell, install the ExchangeOnlineManagement module if needed with Install-Module ExchangeOnlineManagement, and run Connect-ExchangeOnline. Sign in with an account authorized to manage migrations.
Run Test-MigrationServerAvailability -IMAP -RemoteServer imap.example.com -Port 993 -Security Ssl, replacing the server, port, and security setting with the values supplied by your provider.
If the test succeeds, run New-MigrationEndpoint -IMAP -Name "FuseMail IMAP" -RemoteServer imap.example.com -Port 993 -Security Ssl, substituting your verified server settings.
If the test or endpoint creation fails, copy the complete PowerShell error and record the server name, port, and encryption setting. Share these details with Microsoft support and the source email provider; do not include passwords.

Move a few mailboxes with Outlook PST export and import
Use classic Outlook as a manual workaround when only a small number of mailboxes need to be moved.
Import PST files through Microsoft 365 network upload
Use network upload when PST files are available and an administrator wants to import them into Microsoft 365 mailboxes.
Use WPS Office for Everyday Documents After Your Migration
WPS Office is a free, lightweight, easy-to-use alternative with a familiar interface and compatibility with common Microsoft Office formats, making it easier to move existing document workflows. It does not fix Exchange Online migration endpoints or migrate email.

Frequently Asked Questions
Why does the IMAP endpoint fail when another tool can connect?
The available error does not establish the cause. Exchange Online reports a BAD response to the IMAP ID command, so collect the complete error and server settings and contact Microsoft support and the source provider.
How can I test the IMAP server from Exchange Online PowerShell?
Connect with Connect-ExchangeOnline, then run Test-MigrationServerAvailability with the -IMAP, -RemoteServer, -Port, and -Security parameters using your provider's settings.
Can I move email without a working IMAP migration endpoint?
Yes. For a few mailboxes, export source email to PST files in classic Outlook and import it into the Microsoft 365 mailboxes. Administrators can also use Microsoft 365 network upload for PST imports.
Will an IMAP migration include contacts and calendars?
IMAP generally moves email only. Export and import contacts and calendars separately using a method supported by the source service and destination account.
Does WPS Office resolve the Exchange Online endpoint error?
No. The endpoint error must be investigated in Exchange Online and with the source email provider. WPS Office is an alternative for working with Office-compatible documents.




