Fix Your Mailbox Has Been Temporarily Moved to Microsoft Exchange Server Error

This Outlook mailbox issue can occur when Outlook identifies a mismatch between the local mail profile and the remote exchange server. And, it can be triggered by various reasons, such as Hybrid environment conflicts or local data corruption.

Hence, understanding why your mailbox has temporarily moved to the Microsoft Exchange Server is crucial. It will resolve the respective error more smoothly.

So, explore this complete troubleshooting guide. It will guide you with the following queries accurately:

• What is the “Your mailbox has been temporarily moved to Microsoft Exchange Server” error?
• Why does it occur?
• And most importantly, how to fix “your mailbox has been temporarily moved to Microsoft Exchange Server”?

What is the “Your Mailbox has been Temporarily Moved to Microsoft Exchange Server” error?

“Your Mailbox has been temporarily moved to Microsoft Exchange Server” is an error that occurs when Outlook detects a mismatch between the local mail profile and the remote Exchange server.

When it happens, Outlook pops up a dialog box with the following message:

Your mailbox has been temporarily moved on Microsoft Exchange server. A temporary mailbox exists, but might not have all of your previous data. You can connect to the temporary mailbox or work offline with all of your old data.

In the dialog box, Microsoft Outlook users are given three options:

• Use Temporary Mailbox (Do Not Click)
• Use Old Data
• And, Cancel.

Do Not Ignore: It is strictly advised not to click “Use Temporary Mailbox”. Because when you connect to this temporary shell, it will permanently overwrite your locally cached emails. Ending up causing serious data synchronization issues. Therefore, always go ahead with “Use Old Data” or “Cancel” before applying the troubleshooting methods to fix the “Exchange mailbox temporarily moved keeps popping up”.

What triggers the Mailbox Moved to Exchange Server error?

Any misalignment between the local mail profile and the remote exchange server can activate the Outlook mailbox moved to the Exchange server issue. Check out the table given below to find out more about it in detail:=

Systool Top Picks: How to Fix Outlook Sync Issues? (Windows, Mac, and Android)

How to fix the “Your Mailbox has been Temporarily Moved to Microsoft Exchange Server” error? 4 Proven Methods

Here are four easy & proven methods to fix “Your Mailbox has been Temporarily Moved to Microsoft Exchange Server”:

#Fix 1: Modify Registry (For Hybrid/ Autodiscover Issues)

Modifying the Registry is a proven fix for the “Your Mailbox has been Temporarily Moved to Microsoft Exchange Server” error. Since Outlook 2016 and modern versions are strictly coded to prioritize the Microsoft 365 cloud. It forces Outlook to stop analysing the cloud first and prefer the local server routing.

This registry edit technique works like a charm in environments with both on-premises Exchange servers and Microsoft 365 Licenses. But before modifying the registry, it is highly advised to back up your registry. It’s a prerequisite!

To back up the registry:

• Open Registry Editor (press Windows Key + R) >> type regedit >> hit Enter.
• Right-click File >> select Export >> click “All” (under Export Range) >> Save the backup on PC.

Steps to Outlook registry fix mailbox temporarily moved

• Open Task Manager (Ctrl + Shift + Esc) >> Find OUTLOOK.EXE (in the details tab) >> right-click it and hit the End Task tab.
• Launch Registry Editor (press Windows key + R) >> copy-paste regedit >> hit Enter key.
• Scroll down through the folders on the left and find this exact path:
  HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover

Note: In Outlook 2013, the folder will be 15.0 instead of 16.0.

• Next, right-click on the empty space (in the right-hand pane) >> choose New >> select DWORD (32-bit) value >> name the string: ExcludeExplicitO365Endpoint.
• Right-click the ExcludeExplicitO365Endpoint key >> modify the value data from 0 to 1 >> press the tab.OK
• Optional Step: To fix autodiscover keeps failing, create another DWORD (32-bit) value in the folder titled: ExcludeHttpsRootDomain. Configure its value to 1. It will prevent Outlook from pinging the domain root before reviewing the correct autodiscover subdomain.
• Lastly, reboot the PC and reopen Outlook. It will force the operating system to read the new registry.

Fix #2: Recreate New Outlook Profiles

Outlook profiles are the core framework that guides the application to the destination of data. Including the signature to use and how to establish a connection to the server. And when this framework gets corrupted, it causes errors like “Your Mailbox has been Temporarily Moved to Microsoft Exchange Server”. In such scenarios, removing old profiles & recreating new ones settles this error!

However, make sure to backup your data prior to removing the old Outlook profiles just in case.  To do so, simply use the ID admin recommended and easy-to-use SysTools OST to PST Converter tool.

Here’s how to delete old Outlook profiles and recreate new ones:

• Open the Windows Control Panel >> find & select Mail (Microsoft Outlook). Change the “View by” (in the top-right corner) to “Small Icons” to locate quickly.
• Right-click the “Show Profiles” button (in the pop-window). It will open “Profile Manager”.
• Select & remove each profile >> hit Apply.
• Right-click Add >> enter the name for the new profile (use Outlook_Fix or CorpMail_2026 >> click OK.
• Enter email address and password (in the sign-in window). Here, Outlook will exercise a clean Autodiscover lookup to identify the authentic Exchange server instead of depending on damaged cached paths.
• Finally, set the toggle to “Always use this profile” (in the mail window) >> choose the new profile (from the dropdown menu) >> press OK.

Fix #3: Rename the .ost and .pst Cache Files

As we know, Outlook utilizes .ost (Offline Storage Table) files to store local copies of emails to make the emails quickly accessible and run the app faster. But when Office 365 Groups are used, it creates a companion .nst file. And, when these file sheets are corrupted, Outlook gets overwhelmed and assumes the mailbox was moved. Resulting in issues like “exchange mailbox temporarily moved keeps popping up”.

Most troubleshooting blogs suggest deleting these corrupted files as the only method to fix this issue. Indeed, it works! But it is not considered a safe IT practice as it removes all the files. Instead, rename them! It disables the damaged files. And ensures the files are also backed up for future use.

Steps to rename the .nst files:

• Open Task Manager (Ctrl + Shift + Esc) >> look up for OUTLOOK.EXE (in the details tab) >> right-click it and hit the End Task tab.
• Launch Run dialog (press Windows + R key) >> copy-paste the path: %localappdata%\Microsoft\Outlook >> hit Enter. It will open the AppData Folder.
• Right-click the “Views” tab at the top (in the File Explorer Window) >> Ensure the File name extension is checked. Now, you can see the .ost and .pst parts of the file names.
• Search the files named after the email address, like ([email protected] and [email protected]).
• Select the .ost file >> click Rename >> add .old to the end. After renaming, it will look like ([email protected]).
• Now, repeat the same process for the .nst files.
• Lastly, you will notice “Updating Inbox” at the top bottom-right corner of Outlook. Keep the Outlook open & active until it shows “All folders are up to date”.

Fix #4: Uncheck the Exchange Online License (For Admins Only)

Unchecking the Exchange Online License box prevents Outlook from finding a cloud mailbox. And routes it straight to the on-premise server. It is a Microsoft 365 admin-only fix to resolve the mailbox temporarily moved to the Exchange server. Because it requires specific privileged permissions.

Instructions to uncheck the Exchange Online License:

• Go to admin.microsoft.com >> log in with Global Admin or Exchange Admin Credentials.
• Navigate to Users (on the left-hand navigation pane >> select Active Users.
• Search for the users encountering the Outlook error >> right-click on their display name. It will open the right- hand flyout pane.
• Select the Licenses and apps tab (at the top of the flyout plane).
• Scroll down & go to the Apps section >> click the downward arrow next to it to expand the list. It will reveal isolated micro-services.
• Go through the app list >> find Exchange Online (Plan 1) or Exchange Online (Plan 2) >> uncheck the box next to it.

Note: Do not uncheck other boxes such as Microsoft Teams and SharePoint Online.

• Finally, hit Save Changes (at the bottom).

Once the Exchange Online License is unchecked, wait 15 to 30 minutes. Because Microsoft’s backend Azure Active Directory takes time to deprovision the cloud mailbox. After that, ask users to restart their computers and Open Outlook.

Trending Right Now: How to IMAP Error Code 0x800ccc0e in Outlook

Author’s Final Words

How to fix the “Your Mailbox has been Temporarily Moved to Microsoft Exchange Server” error is a common query asked by IT admins and everyday Microsoft users.

This issue has the potential to leave users in a panic. However, once you understand why it happens, you can effortlessly resolve it by following the simple steps mentioned in this blog post.

So, if you ever experience this dreadful error again, you can refer to this trusted guide anytime, simply by bookmarking this enterprise-grade guide.

People Also Liked: Resolve Microsoft Outlook Email Error Codes & Messages Effortlessly – 2026 Guide

FAQs (Frequently Asked Questions)

Q.1 How to fix the mailbox temporarily moved on the Exchange server without losing data?

Since the Exchange mailbox keeps all the data on the server. Creating a new Outlook profile will bypass this error. So, here are the easy steps to fix the mailbox temporarily moved on the Exchange server without losing data:

• Do not click the “Use Temporary Mailbox” option >> close it.
• Go to the Control Panel >> click Mail Settings.
• Create a new Outlook profile

Q.2 Why does my Outlook mailbox temporarily move to the MS Exchange server happen after an update?

Microsoft routinely updates its Autodiscover protocols to prioritize Microsoft 365 cloud environments. Therefore, an update can modify your local XM configurations. Resulting in ignoring the designated Exchange server and hitting an empty Office 365 endpoint. However, you can fix this issue by implementing the ExcludeExplicitO365Endpoint registry key.

Q.3 Can I fix Office 365 mailbox temporarily moved error by turning off Cached Exchange Mode?

Yes, you can turn off the Cached Exchange Mode to fix the Office 365 Mailbox temporarily moved error. It will force Outlook to read data directly from the server in real time. To use this temporary diagnostic step:

• Go to File >> Account Settings >> right-click email >> uncheck Use Cached Exchange Mode.