Forum Discussion
New Outlook: "Changing the ImapRemoteServerInfo is not allowed" after host migration
Hi everyone!
I've migrated my domain/mailbox from one IMAP host to another in May. It cannot be added to New Outlook for Windows — fails instantly with INVALID_CREDENTIALS INTERACTION_REQUIRED, even when I deliberately enter a wrong password (so it's failing before authentication is even attempted).
Using DevTools (olk.exe -devtools), the Network tab shows the real rejection from Microsoft's backend:
Changing the ImapRemoteServerInfo is not allowed. Attempted to change it from imap.olddomain.sk to imap.newdomain.sk
So New Outlook has a cloud-mailbox / connected-account shadow record for this address, pinned to the old host from a previous add attempt, and the backend refuses to update it. What I've confirmed:
- Webmail and a second mailbox on the same domain/host both work fine → not credentials, not the host.
- The account does not appear in Settings → Accounts (so I can't use "Remove from all devices" which worked on my first account).
- It's on no other device or client.
- App reset didn't help (record is server-side, not local).
- It's been ~7 weeks, so any 30-day inactivity purge hasn't cleared it
How do I get this stuck cloud-mailbox / connected-account record purged when it isn't attached to any removable account? Is there a way to force it, or does this need Microsoft backend action?
56 Replies
- TonyJSCopper Contributor
Hello RobertSparnaaij ,
I have the same issue. I have migrate mailbox : mailto:email address removed for privacy reasons to othe account OVH.
I have launch the DevTools and the result is :
Old IMAP server: pro2.mail.ovh.net (OVHcloud Email Pro, previous platform)
New IMAP server: pro3.mail.ovh.net (OVHcloud Email Pro, migrated on 2026-11-13)
Thank you - kuyukhuseyinCopper Contributor
Hello Robert, I’m also experiencing the same issue with ImapRemoteServerInfo, and I’ve sent you my email address in a private message. I’d be very grateful if you could help me with this. RobertSparnaaij
- abdoul_nayefCopper Contributor
I'm having the same issue after moving our business email accounts to Hostinger, and I've been trying to resolve it for the past two days.
Six of our business email accounts are affected. Everything works in Hostinger Webmail and Thunderbird, but New Outlook keeps reverting to the old IMAP server settings.
I've tried repairing and resetting Outlook, clearing the cache, removing and re-adding the accounts, using app passwords, and checking for updates. Unfortunately, nothing has worked.
Hostinger has also carried out a technical investigation and found no issues with the mail servers, DNS settings, or IMAP authentication in the tested accounts.
Has anyone managed to resolve this permanently? Could someone please help me escalate this to the Outlook team for a possible server-side IMAP reset?
I've already sent a private message with further details.
Any help would be greatly appreciated. Thank you.
- IngoWupperfeldCopper Contributor
Hello Robert,
I am experiencing the same issue after migrating my IMAP account from STRATO to a new Plesk mail server.
New Outlook continues to use the old server configuration, although the new server works correctly.
I tried to send you a private message, but Microsoft Tech Community repeatedly displays the error "Cannot Send Message – Try again in a few moments."
My main concern is that my calendars and contacts are associated with the affected IMAP account and appear to be stored in Microsoft's cloud.
Is there a way to reset the outdated IMAP configuration without losing these calendars and contacts?
Could you also suggest an alternative way to contact you privately?
Thank you for your help.
- TissandierCopper Contributor
I have the same issue:
{
"idpStatusCode": "BadRequest",
"error": "BadRequest",
"errorDescription": "Changing the ImapRemoteServerInfo is not allowed. Attempted to changed it from 'mail.infomaniak.com' to 'imap.fastmail.com'",
"innerError": null
}
This is very frustrating!
It's especially annoying because the add account screen successfully detects all of the Fastmail server settings, so it knows the provider has changed... - niclasgaertnerCopper Contributor
Hi Robert Sparnaaij, a short update on my case from 10.11. (domain moved from IONOS to ALL-INKL, error: Changing the ImapRemoteServerInfo is not allowed, imap.ionos.de -> w0201ec5.kasserver.com).
Today I contacted Microsoft Support via chat. The supervisor confirmed that the issue is caused by cached backend provisioning data and raised it for further review. Case numbers: 7111830960 and 7111830377.
The account is not visible on any device, so "Remove from all devices" is not possible. I already sent you the affected address and the full DevTools payload via private message. I would really appreciate it if you could request the server-side reset for this mailbox as well.
Thank you very much!
- niclasgaertnerCopper Contributor
Same issue here. Mailbox was moved from IONOS (imap.ionos.de) to ALL-INKL (w0201ec5.kasserver.com) on 7 Nov 2026. Webmail and Thunderbird work fine, other mailboxes on the same server work in New Outlook. New Outlook refuses this one ("Your email looks like a shared mailbox"), and it doesn't appear in Settings > Accounts on any device, so "Remove from all devices" isn't possible. Robert, could you please escalate it to the Outlook Team for a server-side reset? I'll send you the address by private message.
- daivareinCopper Contributor
Hi, I have the same issue. I cannot add the email to new outlook
{
"idpStatusCode": "BadRequest",
"error": "BadRequest",
"errorDescription": "Changing the ImapRemoteServerInfo is not allowed. Attempted to changed it from 'imap.domeneshop.no' to 'imap.zoho.eu'",
"innerError": null
}
- ElementmediaCopper Contributor
I have the exact same issue. Does anyone have a solution or best contact method to get this resolved? Maybe still RobertSparnaaij (sorry to bother you).
- ElementmediaCopper Contributor
I have the exact same problem with the domain of a client I helped migrating. Tried contacting support (by chat) but they closed it with the statement that this is not their fault.
Can anyone tell me with the best way to resolve this caching issue?