Outlook Hybrid Account Loop Between Local and Cloud Mailbox: Fix

When you open Outlook in a hybrid Exchange environment, you may see a repeated prompt asking you to choose between your local mailbox and your cloud mailbox. This loop prevents you from accessing any email. The issue occurs because Outlook detects two conflicting Autodiscover responses — one from the on-premises Exchange server and one from Exchange Online — and cannot determine which mailbox profile to use. This article explains the root cause of the hybrid account loop and provides the specific steps to stop the loop and connect to the correct mailbox.

Why the Hybrid Loop Happens

The hybrid mailbox loop is caused by a conflict between two Autodiscover endpoints. When a user has a mailbox that is still hosted on-premises but is also mail-enabled in Exchange Online, Outlook sends an Autodiscover request to the on-premises server. The on-premises server returns a redirect pointing to Exchange Online. Outlook then contacts Exchange Online, which returns a redirect back to the on-premises server. This redirect loop creates the repeated prompt asking you to select a mailbox.

Three conditions must be present for the loop to occur. First, the user mailbox is still located on the on-premises Exchange server. Second, a remote mailbox or mail user object exists in Exchange Online for the same user. Third, the Autodiscover service on the on-premises server is configured to redirect to Exchange Online for cloud-hosted mailboxes. When Outlook follows the redirect chain, it never lands on a final Autodiscover response that matches the local profile.

How Outlook Decides Which Mailbox to Open

Outlook uses the Autodiscover service to locate the correct mailbox server. The client first checks the Active Directory SCP (Service Connection Point) for an Autodiscover URL. If found, it sends an Autodiscover POST request. In a hybrid configuration, the on-premises Exchange server examines the recipient address and, if the mailbox is flagged as a remote mailbox, returns an HTTP 302 redirect to the Exchange Online Autodiscover URL. Exchange Online then returns an HTTP 302 redirect back to the on-premises server. Outlook cannot resolve this circular reference and displays the mailbox selection dialog each time it starts.

Steps to Break the Hybrid Mailbox Loop

Follow these steps in order. Each step removes a piece of the loop. After completing all steps, restart Outlook.

1. Delete the existing Outlook profile
   Open Control Panel. Click Mail (Microsoft Outlook). Click Show Profiles. Select the profile that shows the loop behavior. Click Remove. Click Yes to confirm. This deletes the cached Autodiscover data that is causing the redirect loop.
2. Create a new Outlook profile manually
   In the same Mail dialog, click Add. Type a name for the new profile. Click OK. In the Add Account dialog, select Manual setup or additional server types. Click Next. Select Microsoft Exchange Server or compatible service. Click Next. In the Server field, type the FQDN of your on-premises Exchange server. In the User Name field, type the user alias. Click Check Name. After the name resolves, click Next and then Finish.
3. Disable MAPI over HTTP on the client
   Open Registry Editor. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Exchange. Right-click the Exchange key and select New > DWORD (32-bit) Value. Name it MapiHttpDisabled. Set the value to 1. Click OK. This forces Outlook to use RPC over HTTP instead of MAPI over HTTP. In a hybrid environment, RPC over HTTP does not follow the Autodiscover redirect chain as aggressively, which stops the loop.
4. Exclude the on-premises SCP lookup
   In Registry Editor, navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover. Right-click the AutoDiscover key and select New > DWORD (32-bit) Value. Name it ExcludeScpLookup. Set the value to 1. Click OK. This prevents Outlook from querying Active Directory for an Autodiscover SCP. Outlook will use the DNS-based Autodiscover method instead, which can resolve to Exchange Online directly.
5. Restart Outlook and test the connection
   Close Registry Editor. Open Outlook. When prompted, select the new profile you created. Outlook should connect to the on-premises mailbox without showing the mailbox selection dialog. If the loop still appears, proceed to the next section.

If Outlook Still Shows the Loop After the Main Fix

The mailbox is still in Exchange Online but should be on-premises

If the user mailbox was migrated to Exchange Online but the on-premises Autodiscover still points to the local server, the loop persists. Verify the mailbox location in the Exchange admin center. Open the Exchange admin center. Go to Recipients > Mailboxes. Search for the user. If the mailbox type shows Office 365, the mailbox is in Exchange Online. In that case, remove the on-premises profile and create a new profile using the user’s email address. Outlook will connect directly to Exchange Online.

The Autodiscover DNS record points to the wrong server

Outlook uses the Autodiscover CNAME record in DNS. If the CNAME points to the on-premises Exchange server but the mailbox is in Exchange Online, Outlook follows the wrong path. Open a command prompt. Run nslookup autodiscover.yourdomain.com. If the response shows an on-premises server IP, update the DNS CNAME record to point to autodiscover.outlook.com. Wait for DNS propagation and restart Outlook.

The on-premises Exchange server still has an active Autodiscover redirect

The on-premises Exchange server may have an Autodiscover virtual directory that redirects all requests to Exchange Online. This is common in hybrid deployments where the cloud is the primary mailbox location. If the mailbox is still on-premises, remove the redirect. Open Exchange Management Shell. Run Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -MapiHttpModuleUrl $null. Then run Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri $null. This stops the on-premises server from redirecting Autodiscover requests.

Item	On-Premises Mailbox	Exchange Online Mailbox
Profile creation method	Manual with server FQDN	Automatic with email address
Autodiscover target	On-premises Exchange server	autodiscover.outlook.com
MAPI over HTTP setting	MapiHttpDisabled=1 recommended	Default (MAPI over HTTP enabled)
Registry key required	ExcludeScpLookup=1	None
Loop risk	High if remote mailbox exists in cloud	Low

You can now connect to the correct mailbox without the loop. After completing the steps, verify that Outlook opens directly to the Inbox. If you manage multiple hybrid users, consider setting the ExcludeScpLookup and MapiHttpDisabled registry keys via Group Policy to prevent the loop on new machines. As an advanced tip, run the Microsoft Remote Connectivity Analyzer Autodiscover test to confirm which server Outlook resolves before you deploy the registry changes.