New Outlook: "Changing the ImapRemoteServerInfo is not allowed" after host migration

Hello Robert,

I found your discussion about the “Changing the ImapRemoteServerInfo is not allowed” error in the new Outlook for Windows.

I have exactly the same problem.

Affected email address: email address removed for privacy reasons

Old IMAP server: w012b4a1.kasserver.com

New IMAP server: imap.strato.de

The error shown in DevTools is:

“Changing the ImapRemoteServerInfo is not allowed. Attempted to change it from w012b4a1.kasserver.com to imap.strato.de.”

My mailbox works perfectly in Outlook Classic and STRATO Webmail. However, I cannot add it to the new Outlook.

I have already reset and completely reinstalled the new Outlook, without success. The affected account is not listed in Outlook’s account settings, so I cannot remove it myself.

Could you please ask the Outlook team to clear the old server-side IMAP configuration for this email address?

Thank you very much for your help!

Subject: Request to reset New Outlook IMAP server association

Hello Robert,

I migrated my custom-domain email account from OVH to Comvive. The email address remains the same, but the IMAP/SMTP server has changed.

New Outlook for Windows accepts the new server settings but fails to connect. I have already tried removing and re-adding the account, resetting and reinstalling Outlook, and the other troubleshooting steps, without success.

I also contacted Microsoft Support more than a month ago and have received no response.

Could you please help me request a server-side reset of the stale IMAP server association (ImapRemoteServerInfo) for my affected email address?

I understand that this reset may delete cloud-only data, including drafts, contacts, calendars, tasks and notes that are not synchronized with my mail provider.

Thank you.

Hello RobertSparnaaij​,

I am facing the exact same host migration lockout issue with a client's mailbox.

We recently migrated to Hostinger, and New Outlook for Windows throws a 400 Bad Request: "Changing the ImapRemoteServerInfo is not allowed."

I have already attempted the "Remove from all devices" method, but the server-side cache remains completely locked to the old IMAP host. Local troubleshooting across multiple PCs has been exhausted, and Microsoft Windows Support confirmed the server-side database block under Case Number 7110532601 before referring us here.

I am sending you a Private Message right now with the affected email address and the full DevTools error payload. I would greatly appreciate it if you could assist us in requesting a backend cache flush for this mailbox.

Thank you!

Hello Robert,

I'm experiencing what appears to be the same issue described in this thread.

My email address mailto:email address removed for privacy reasons was migrated from Junda to STRATO while keeping the same email address.

I previously used this account in New Outlook. Now, when I try to add it using the correct STRATO IMAP/SMTP settings, I receive:

INVALIDCREDENTIALS TEMPORARILYUNAVAILABLE

STRATO webmail works, and the IMAP/SMTP settings are correct.

The account is no longer listed in New Outlook, so I cannot use the "Remove from all devices" option.

Could you please help escalate a server-side reset of the IMAP provider association / ImapRemoteServerInfo to the Outlook Team?

Before the reset, please let me know what mailbox data might be lost so I can confirm.

Thank you!

Same issue here.. moved from ZOHO to uolhost.. and cant log into new outlook, just pmed you RobertSparnaaij​ 

RobertSparnaaij​ 

Hi Robert, I have exactly the same issue. My mailbox email address removed for privacy reasons was migrated from IONOS to CDMON, keeping the same email address. New Outlook still retrieves the old IONOS servers and returns INVALIDCREDENTIALS EXTENDEDERROR. The mailbox works correctly in Classic Outlook, SOGo and on a new device. The account is no longer present in New Outlook, so I cannot use “Remove from all devices”. Could you please escalate my address to the Outlook Team for a server-side reset of the IMAP provider association / ImapRemoteServerInfo cache?

Hi Robert,

I was referred to this discussion by Microsoft Q&A Support because I am experiencing the same issue with New Outlook after migrating my email hosting provider.

Affected email: mailto:email address removed for privacy reasons

Old IMAP server: sc135.idcloudhosting.cloud

New IMAP server: mail.alphasys.id

New Outlook keeps reverting to the old IMAP server even after manually entering the new configuration.

Troubleshooting performed:

1. Removed the account from all devices.
2. Tested on a completely new Windows device.
3. Verified DNS resolution and IMAP/SMTP connectivity.
4. Confirmed that cPanel Autoconfig returns the correct new server.
5. Confirmed another mailbox under the same domain works correctly.

Could you please help escalate this issue to the Outlook Team for a possible server-side reset of the IMAP server association (ImapRemoteServerInfo)?

Thank you for your assistance.

Hi Robert,

I was referred to this discussion by Microsoft Q&A Support because I am experiencing the same issue with New Outlook after migrating my email hosting provider.

Affected email: mailto:email address removed for privacy reasons

Old IMAP server: sc135.idcloudhosting.cloud

New IMAP server: mail.alphasys.id

New Outlook keeps reverting to the old IMAP server even after manually entering the new configuration.

Troubleshooting performed:

1. Removed the account from all devices.
2. Tested on a completely new Windows device.
3. Verified DNS resolution and IMAP/SMTP connectivity.
4. Confirmed that cPanel Autoconfig returns the correct new server.
5. Confirmed another mailbox under the same domain works correctly.

Could you please help escalate this issue to the Outlook Team for a possible server-side reset of the IMAP server association (ImapRemoteServerInfo)?

Thank you for your assistance.

I have an IMAP mailbox on a custom domain that was recently migrated from one hosting provider to OVH.

The email address has not changed. It seems, that I have the same problem as in this thread.

Only the hosting provider and IMAP/SMTP server have changed.

Current OVH settings:

IMAP: imap.mail.ovh.net

Port: 993

SSL/TLS

Username: full email address

SMTP: smtp.mail.ovh.net

Port: 465

SSL/TLS

Authentication: username/password

The credentials and current server settings are definitely correct:

Webmail works.

The same mailbox works in Classic Outlook on the same PC.

The same mailbox works with other mail clients.

The problem occurs only in New Outlook for Windows.

When adding the account in New Outlook, I enter the correct OVH password. After clicking Next, New Outlook fails with:

INVALIDCREDENTIALS INTERACTIONREQUIRED

Previously, I also received:

UNKNOWN undefined

Current Session ID:

cb411338-c7af-af4S-8cOf-8cbS6d94a611

I have already tried:

removing and re-adding the account,

restarting New Outlook,

resetting New Outlook,

reinstalling New Outlook,

verifying the OVH IMAP/SMTP settings,

verifying the credentials in Classic Outlook.

None of these changed the result.

This looks very similar to the Microsoft Q&A cases from 2026 concerning migrated IMAP accounts where the email address remains the same but the IMAP server changes.

In particular, this case appears highly relevant:

“New Outlook for Windows won't add a migrated IMAP account — Cloud Mailbox stuck on old server (ImapRemoteServerInfo locked), needs service-level reset.”

Another August 2026 case reports the explicit backend error:

Changing the ImapRemoteServerInfo is not allowed

when the IMAP server was changed after a hosting migration.

Could someone familiar with the New Outlook backend please confirm whether the Microsoft Cloud account associated with my email address may still contain the old IMAP server information?

If so, is there a supported way to reset/re-provision the IMAP Cloud Mailbox so that New Outlook can register the current OVH server?

Microsoft Support has already reviewed the case and confirmed that the issue appears to require deeper investigation, but their current support channel does not have access to modify or reset the IMAP backend association.

I specifically want to use New Outlook. Classic Outlook works, but it does not resolve the New Outlook issue. New Outlook for Windows – IMAP account cannot be added after migration to a new hosting provider

I have an IMAP mailbox on a custom domain that was recently migrated from one hosting provider to OVH.

The email address has not changed. Only the hosting provider and IMAP/SMTP server have changed.

Current OVH settings:

IMAP: imap.mail.ovh.net

Port: 993

SSL/TLS

Username: full email address

SMTP: smtp.mail.ovh.net

Port: 465

SSL/TLS

Authentication: username/password

The credentials and current server settings are definitely correct:

Webmail works.

The same mailbox works in Classic Outlook on the same PC.

The same mailbox works with other mail clients.

The problem occurs only in New Outlook for Windows.

When adding the account in New Outlook, I enter the correct OVH password. After clicking Next, New Outlook fails with:

INVALIDCREDENTIALS INTERACTIONREQUIRED

Previously, I also received:

UNKNOWN undefined

Current Session ID:

cb411338-c7af-af4S-8cOf-8cbS6d94a611

I have already tried:

removing and re-adding the account,

restarting New Outlook,

resetting New Outlook,

reinstalling New Outlook,

verifying the OVH IMAP/SMTP settings,

verifying the credentials in Classic Outlook.

None of these changed the result.

This looks very similar to the Microsoft Q&A cases from 2026 concerning migrated IMAP accounts where the email address remains the same but the IMAP server changes.

In particular, this case appears highly relevant:

“New Outlook for Windows won't add a migrated IMAP account — Cloud Mailbox stuck on old server (ImapRemoteServerInfo locked), needs service-level reset.”

Another August 2026 case reports the explicit backend error:

Changing the ImapRemoteServerInfo is not allowed

when the IMAP server was changed after a hosting migration.

Could someone familiar with the New Outlook backend please confirm whether the Microsoft Cloud account associated with my email address may still contain the old IMAP server information?

If so, is there a supported way to reset/re-provision the IMAP Cloud Mailbox so that New Outlook can register the current OVH server?

Microsoft Support has already reviewed the case and confirmed that the issue appears to require deeper investigation, but their current support channel does not have access to modify or reset the IMAP backend association.

I specifically want to use New Outlook. Classic Outlook works, but it does not resolve the New Outlook issue.

Could someone help me out with this issue?

RobertSparnaaij​ - Hello Robert, I can imagine this is not your main topic to deal with, but will appreciate if you can help me with the same issue - new Mail host - MS keeps the old IMAP details. May I send you over my details?

Best regards

Lyubo