• “Outlook cannot connect to Office 365 after migration” is a result of inactive Autodiscover endpoints, cached old-server profiles, or outdated Web Account Manager (WAM) identity tokens.
  • Outlook connection problems after a tenant move can also occur due to an incomplete DNS, licensing, or mailbox configuration cutover.
  • Classic Outlook (Win32 Outlook.EXE) and New Outlook for Windows (OLK.EXE, web-based) store profiles, caches, and Autodiscover logic distinctly.
  • Classic Outlook utilizes Windows Control Panel Mail. Including .ost data files, the CTRL+ Right-Click system tray diagnostic menu, HKEY_CURRENT_USER Autodiscover registry keys, and the GetHelpCmd.exe diagnostic utility.
  • New Outlook for Windows connects directly to the Microsoft Cloud endpoint via Windows Web Account Manager (WAM) and stores a local cache in %LocalAppData%\Microsoft\Olk. Also, OWA ignores Classic Mail profiles, .ost files, and Autodiscover registry overrides.
  • Standard profile resets and credential deletion fix roughly 70% of post-migration Outlook failures. But certain connection issues are closely linked with the migration method.

In this comprehensive write-up, you will discover exactly what causes the “Outlook cannot connect to Office 365 after migration” issue. Including the guiding steps to troubleshoot the Outlook connection problem post-cutover on Classic Outlook and New Outlook for Windows.

This guide will share how to prevent Outlook breakage and other post-migration issues beforehand. So, keep exploring till the end.

What You’ll Learn Hide

The First Three Checks

Before editing the registry keys or reinstalling Microsoft 365 apps to fix the “Outlook cannot connect to Microsoft 365” issue, run these three checks first:

  • Test Outlook on the Web: Go to https://outlook.office.com and sign in. If the mailbox loads perfectly in the browser, the problem is local to the Outlook client or Autodiscover.
  • Check DNS and Autodiscover: Ensure the domain’s Autodiscover CNAME configuration points to autodiscover.outlook.com). Also, run the Microsoft Remote Connectivity Analyzer to test remote connectivity & configuration issues.
  • Create a fresh Outlook profile: Provision a clean mail profile (Classic Outlook). Or reset local state (New Outlook for Windows) to extract the old-server .ost cache and tenant anchors.

Why Outlook Cannot Connect to O365 After Migration

Outlook Error or Symptom 

Most Likely Root Cause 

Fastest Fix

  • Outlook keeps asking for a password after migration (Repeated Modern Auth or Basic Auth Loop)
  • Stale WAM/Entra ID tokens, cached Credential Manager entries, MFA or Conditional Access issue, or old Office build restricting OAuth 
  • Clear the Windows Credential Manager. Next, disconnect stale accounts in Access work or school. Then, reset Office “Identity” tokens.
  • Status Bar shows “Disconnected” or “Trying to connect”
  • This happens because the old server endpoint is being cached, MAPI is disabled on the mailbox, or the firewall is blocking MAPI over HTTP
  • Check AutoDiscover and “MAPIENABLED” status. Then, create a new Outlook profile.
  • “Cannot open your default e-mail folders”
  • Corrupted or mismatched OST file pointing to the legacy Exchange server or an old tenant’s Exchange GUID.
  • Inspect OWA and licensing, then provision a new Outlook profile. This will prompt Outlook to generate a fresh .ost file.
  • Outlook still connecting to the old Exchange server 
  • On-premises Active Directory SCP pointer, Root-domain HTTPS Autodiscover, or incorrect DNS response is responsible.
  • Configure “ExcludeScpLookup” and “ExcludeHttpsRootDomain” to “1”. Ensure that “ExcludeExplicitO365Endpoint” is not set to “1”. 
  • Outlook configures the mailbox as IMAP
  • Root-domain Autodiscover or legacy email hosting is interrupting discovery.
  • Review and rectify the AutoDiscover DNS and web-host configuration to fix this issue.
  • “Something went wrong”/ AADSTS error when adding account 
  • It triggers when the Exchange Online license is missing. Also due to an unverified domain cutover and a corrupted Entra ID broker cache.
  • Evaluate Exchange Online licenses in Microsoft 365 Admin Center. Then, wipe out the WAM broker cache.
  • Autodiscover not working after Office 365 migration (cannot find server settings)
  • Missing/misconfigured autodiscover.outlook.com CNAME, GoDaddy/CPanel web host hijacking /autodiscover/autodiscover.xml, or legacy history block.
  • First, resolve the external DNS CNAME record. Next, validate via Remote Connectivity Analyzer.
  • Outlook works on the web but not on the computer 
  • Occurs due to a local profile, authentication, Office installation, or network issue.
  • Try creating and testing a fresh profile and refresh authentication.

Step-by-Step: Fix Outlook Not Connecting to Microsoft 365 After Migration

Follow these six steps in order—beginning with 2-minute isolation checks before moving to credential resets, profile rebuilds, and registry overrides.

Step#1: Isolate Client vs. Server (Outlook or Exchange Online)

The first step in troubleshooting “Outlook Cannot Connect to Office 365 After Migration” is to determine whether Outlook or Exchange Online is at fault.

So, before configuring a single setting on the Windows workstation, check whether the mailbox works on Microsoft’s side. Also, ensure where Autodiscover is actually sending traffic.

Sign in to Outlook on the Web:

  • Open an IPPrivate/Incognito browser window.
  • Go to (https://outlook.office.com).
  • If a “500 Something went wrong” or UserHasNoMailboxAndNoLicenseAssignedError message appears, stop troubleshooting Outlook. This is a server-side licensing or provisioning issue. (Go to Step 2).
  • And if the migrated inbox opens normally, this indicates that Exchange Online is healthy.

Utilize the Microsoft Remote Connectivity Analyzer (ExRCA):

  • Go to [https://testconnectivity.microsoft.com].
  • Select the “Exchange Online” tab.
  • Run the “Outlook Connectivity Test”. This will confirm Autodiscover and MAPI-over-HTTP externally.
  • Also, expand any visible red “X” markers. If ExCRA fixes an IP associated with the old Exchange server, GoDaddy, or a web host instead of Microsoft, the Public DNS or web server is dictating the Autodiscover.

Run Test E-Mail AutoConfiguration (Classic Outlook Only):

  • Sign in to Outlook on the web: Open an InPrivate/Inconito browser window
  • With Classic Outlook open, hold “CTRL” >> right-click the Outlook icon in the Windows system tray (near the clock).
  • Select “Test E-mail AutoConfiguration” >> enter the migrated email address.
  • Uncheck “Guessmart and Secure Guessmart Authentication”. Check only “Use Autodiscover” >> click “Test”.
  • Assess the “Log” tab to see Outlook retrieve XML from [https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml]. Or redirect directly to Microsoft 365. If it hits an internal .local URL or the company website root domain first, note that URL and apply in Step 5.

Step#2: Check DNS Records, Exchange Online Licensing, and MAPI Status

Checking DNS records, Exchange Online licensing, and MAPI access is crucial. This is because an overlooked admin toggle during cutover week is the primary factor responsible for Outlook not connecting to Microsoft 365 after a migration issue. Remember, a successful mailbox migration doesn’t establish that every DNS record and mailbox configuration has been updated correctly.

Review Public DNS Records:

  • Open the Command Prompt or PowerShell.
  • Next, run the following command to verify how your workstation resolves Autodiscover and mail routing:
nslookup -type=cname autodiscover.yourdomain.com
nslookup -type=mx yourdomain.com
  • Replace “yourdomain.com” with your domain.
  • In order to check the exact DNS values for the domain:
  • Go to Microsoft 365 Admin Center >> click “Settings”.
  • Click “Domains” >> select your domain >> DNS records.

If the internal Active Directory runs split-brain DNS (an internal zone matching the public domain name), inspect the internal DNS server. Make sure it also has an autodiscover CNAME pointing to autodiscover.outlook.com. Instead of the old internal “A” record pointing to an on-premises Exchange server.

Note: First, confirm that the destination cutover is over. Only after that, remove stale mail-routing records only after . Allow for the published DNS TTL when testing changes.

Inspect Licensing, MAPI, and Modern Auth (Admin Checks)

To review the Exchange Online License:

  • Go to Microsoft 365 Admin Center.
  • Open “Users” >> select “Active Users”.
  • Select the affected user >> open “Licenses and Apps”.
  • Ensure an appropriate license is assigned.
  • Lastly, expand the license. Then, make certain that the “Exchange Online” services plan is enabled.

To confirm whether MAPI-over-HTTP is enabled:

  • Connect to Exchange Online PowerShell and check the user’s CAS mailbox flags:
Connect-ExchangeOnline
Get-CASMailbox -Identity "[email protected]" | Format-List MAPIEnabled, OWAEnabled, EwsEnabled
  • If MAPIEnabled returns False, desktop Outlook cannot connect even though OWA works. Enable it immediately by running the command:
Set-CASMailbox -Identity "[email protected]" -MAPIEnabled $true

To verify Conditional Access & Office Build:

  • Access Microsoft Entra admin center (entra.microsoft.com).
  • Review “Protection” >> Sign-in logs for the user.
  • Search for “Interrupted” or “Failure” entries caused by MFA registration loops, legacy auth blocks, or device compliance policies.
  • In Classic Outlook:
  • Check “File” >> select “Office Account”.
  • Click “Update Options” >> Update Now. This will make certain that the machine runs a current Microsoft 365 Apps Click-to-Run build supporting Modern Authentication (OAuth 2.0).

Step #3: Clear Cached Credentials, WAM/ Entra Tokens, and Old Tenant Identities

“Outlook keeps asking for password after migration” is one of the most frustrating post-migration Outlook problems. Outlook repeatedly requests the password because Windows or Office continues to present authentication information linked to the old tenant.

Clearing Credential Manager or removing an old password from Credential Manager does not necessarily remove every cached identity or WAM token. This is because modern Microsoft 365 authentication relies on Windows Web Account Manager (WAM) and cached Entra ID broker tokens that withstand standard credential wipes.

So, to clear Cached Credentials, WAM/ Entra Tokens, and Old Tenant Identities:

  • Close Outlook and all other Microsoft 365 apps. Also end any running OUTLOOK.EXE or OLK.EXE processes in Task Manager.
  • Clear Windows Credential Manager: Open Control Panel >> go to “User Accounts” >> select “Credential Manager” >> click “Windows Credentials”.
  • Delete any standard entry starting with MicrosoftOffice16_Data, ADAL, MS.Outlook, Exchange, or the migrated email address.
  • Disconnect inactive Work or School Accounts (WAM Reset):
  • Wipe out Cached Office Identity Registry Entries:
    • Press Win+R >> type “regeit” >> hit Enter.
    • Go to: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities.
    • Export the “Identity” key as a backup. Next, remove the subkeys inside “Identities”. This will delete stale cached tenant GUIDs. And tokens without deleting local files.
    • Also confirm whether “EnableADAL” is not configured to “0” by reviewing HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity. If “EnableADAL” exists and equals “0”, delete it or set it to “1”.
  • Lastly, restart Windows so the AAD Broker Plugin (Microsoft.AAD.BrokerPlugin) configures fresh tokens on next sign-in.

For Entra-joined and hybrid-joined devices, manually deleting WAM cache or BrokerPlugin folders is not recommended. Instead, use Microsoft’s documented signoutofwamaccounts.ps1 procedure where applicable. This approach is safer than manually dismantling Windows authentication state.

If the password prompts continue:

  • Confirm whether Outlook is signing in with the destination UPN.
  • Ensure MFA registration or authentication requirements change during tenant moves.
  • Inspect Microsoft Entra sign-in logs for Conditional Access failures.
  • Make certain that the destination account has the required permissions to access Exchange Online.

Remember, a persistent authentication prompt is not necessarily proof of an incorrect password. It may indicate that the authentication process is failing after the credentials are entered.

Step #4: Create a New Outlook Profile

Recreating the Outlook profile after the cross-tenant data transfers or IMAP/GoDaddy cutover every time is critical to resolve “Cannot open your default e-mail folders’ or prevent silent sync stalls. This issue occurs when \existing profiles preserve the old mailbox GUID and server endpoints.

Follow the given instructions to recreate the Outlook profile (Classic Outlook and New Outlook for Windows):

Classic Outlook:

  • Start by closing Outlook completely.
  • Access “Control Panel” >> open “Mail (Microsoft Outlook)”.
  • Click “Show Profiles” >> select “Add”.
  • Enter a new profile name. Add the migrated M365 email account
  • Complete the Microsoft 365 Modern Authentication/MFA prompt. This will allow Outlook to configure the mailbox.
  • Back in the “Mail” window, select “Always use this profile”.
  • Next, choose the new profile from the drop-down >> click “OK”.
  • Finally, launch Outlook. This will provision a fresh OST file in %LocalAppData%\Microsoft\Outlook and sync the cloud mailbox.

Pro-Tip: You can also launch the profile picker by holding the “Shift” key while starting Outlook. Or by running the “Outlook.exe /profiles” command.

Important Note: If you need to reference offline data, preserving the old Outlook profile only for a few days is considered a healthy practice.

New Outlook for Windows (Remove Account or Reset Local State):

Unlike Classic Outlook, New Outlook is not dependent on Control Panel Mail profiles. Also, applying manual OST rebuilding, Autodiscover registry overrides, or Ctrl + Right-Click > Test E-mail AutoConfiguration will not work.

For New Outlook, remove & re-add the account. Removing an account from New Outlook clears out its locally cached account from that device. It does not remove the mailbox from Exchange Online.

Note: Always be certain you are removing the correct account before proceeding.

Steps to Remove the Account from New Outlook:

  • Open New Outlook >> click the “Settings” gear icon (at the top right).
  • Go to “Accounts” >> click “Your Accounts” >> select “Email accounts”.
  • Locate the targeted account.
  • Click “Manage” (next to the migrated mailbox).
  • Click “Account Details” >> select “ Remove”. When prompted to remove the Outlook account from this device or all devices, choose “Remove from this device”. Go ahead with “All Devices” only if stale old-tenant metadata is recurring across Outlook Mobile/Desktop.
  • Next, add the destination account again using “Add Account”.
  • Finally, close the New Outlook >> press “Win+R” and run: olk.exe –clearLocalState to clear the Local State.

If the account still struggles to reconnect or the app still loops:

  • Open “Windows Settings” >> go to “Apps”.
  • Click “Installed Apps” >> locate “Outlook (New)”.
  • Click the three dots >> select “Advanced options”.
  • Try the “Repair” option first. Use “Reset” only if necessary. Resetting the app data will clear the local application data and settings. This will require configuring the account again.

Alternatively, back up and delete %LocalAppData%\Microsoft\Olk. Then, relaunch the New Outlook. Add the Microsoft 365 account.

Step 5: Fix Persistent Autodiscover Redirects Using Registry Settings (Classic Outlook Only)

Correcting stubborn Autodiscover redirects using the Registry Settings is a key step to fix complicated post-migration Outlook connection problems.

When Classic Outlook is still connecting to the old server after migration, its strict Autodiscover lookup priority is usually the culprit. On domain-joined computers, Outlook verifies Active Directory Service Connection Points (SCP) and the root domain HTTPS URL: [https://yourdomain.com/autodiscover/autodiscover.xml] before querying autodiscover.yourdomain.com or Microsoft 365.

Hence, Outlook can be taken over before it reaches Exchange Online if;

  • A legacy on-premises Exchange server remains in Active Directory
  • WordPress/cPanel website returns a “200 OK”
  • Redirect on the root domain

Critical Warning: Take a secure backup of the Windows Registry prior to making any changes.

  • Open Registry Editor using “regedit” and inspect: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover. Also inspect HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\AutoDiscover to make sure an old Group Policy is not overriding the values.
  • Next, check or create the following DWORD (32-bit) values:

Registry Value (DWORD)

What it does  Recommended Post-Migration Setting  When to consider it 

ExcludeExplicitO365Endpoint 

Stops Outlook from using the complete M365 Autodiscover endpoint.

O (or delete the value)

Ensure that it is not set to 1after the cutover. Otherwise, it will actively restrict Outlook from discovering the Online mailbox.

ExcludeScpLookup 

Prevents Outlook from querying Active Directory SCP records.

1

When the domain-joined PC is querying a stale on-premises SCP in Active Directory.

ExcludeHttpsRootDomain 

Rules out root-domain HTTPS AutoDiscover discovery 

1

When the root website or web host is returning the wrong AutoDiscover response. Also, it eliminates GoDaddy, cPanel, and marketing website controls.

ExcludeLastKnownGoodURL  Prevents the utilization of the cached last Known Good AutoDiscover URL 1

When an existing profile is continuously using an obsolete discovery endpoint.

  • To test these on an affected workstation effectively, use PowerShell and run:
$path = "HKCU:\Software\Microsoft\Office\16.0\Outlook\AutoDiscover"
if (!(Test-Path $path)) { New-Item -Path $path -Force | Out-Null }

Set-ItemProperty -Path $path -Name "ExcludeScpLookup" -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name "ExcludeHttpsRootDomain" -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name "ExcludeLastKnownGoodURL" -Value 1 -Type DWord
Remove-ItemProperty -Path $path -Name "ExcludeExplicitO365Endpoint" -ErrorAction SilentlyContinue
  • During Autodiscover, if Classic Outlook still initiates Basic Auth instead of Modern Auth, evaluate this companion key under “HKEY_CURRENT_USER\Software\Microsoft\Exchange”:
$exchPath = "HKCU:\Software\Microsoft\Exchange"
if (!(Test-Path $exchPath)) { New-Item -Path $exchPath -Force | Out-Null }
Set-ItemProperty -Path $exchPath -Name "AlwaysUseMSOAuthForAutoDiscover" -Value 1 -Type DWord
  • After applying these values, restart Outlook or recreate the profile by following the steps shared in step 4.

Step #6: Run Microsoft Outlook Diagnostics (Windows Get Help & GetHelpCmd.Exe)

Another effective approach to fix Outlook not connecting to Office 365 after Microsoft 365 workload transfer is using Microsoft’s diagnostic tools.

Many troubleshooting guides will instruct you to install the standalone Microsoft Support and Recovery Assistant (SaRA). Do not search for SaRA, as Microsoft has retired the standalone app from supported Windows troubleshooting workflows. Also, the SaRA command-line utility has been removed from in-support Windows updates as of March 10, 2026 (KB5086902).

Microsoft has shifted its relevant Outlook troubleshooting experiences to Windows Get Help and its command-line utility, GetHelpCmd.exe.

Windows Get Help App (End Users & Help Desk)

  • Press the “Start” key >> search for “Get Help” and open the built-in Windows app.
  • Next, depending on the issue, search for:

Note: These guided troubleshooters are applicable for Classic Outlook. The same diagnostic workflow will not repair New Outlook.

Diagnostic 

Purpose 

Set up Microsoft 365 email in Outlook

Classic Outlook profile setup problems 
Outlook password problem

Authentication and password prompts loops

Classic Outlook connectivity troubleshooter 

Outlook connectivity failures
Classic Outlook advanced diagnostics 

More comprehensive configuration investigation 

Run GetHelpCmD.exe (For Administrative Outlook Diagnostics):

Investigating remote or scripted diagnostics across multiple affected computers? Utilize Microsoft’s command-line version of Get Help.

The Outlook scan scenario produces a complete diagnostic report of Outlook, Windows, Office build, Autodiscover configuration, and mailbox connectivity in %localappdata%\saralogs\UploadLogs (or using a custom directory using –LogFolder C:\Logs) to identify hidden add-in, GPO, or registry issue immediately.

Important Limitation: The Outlook Scan scenario in “GetHelpCmd.exe” is supported for Classic Outlook only. It can not be applied to New Outlook for Windows. Also, it’s noteworthy that each download build also expires 90 days after its build date. So, it is crucial to pull the latest ZIP before a migration weekend every time.

  • Download the latest GetHelp Command Line tool from Microsoft’s documentation.
  • Extract the ZIP packages.
  • Open the “Command Prompt” in the extracted folder and run:

GetHelpCmd.exe -S ExpertExperienceAdminTask -AcceptEula

  • For a diagnostic log, run:

GetHelpCmd.exe -S ExpertExperienceAdminTask -AcceptEula -LogFolder C:\temp

Note: Ensure the Office build version is up to date. This is because an outdated Office Click-to-Run build can introduce complications to modern authentication and connectivity troubleshooting.

Migration-Specific Outlook Connection Problems

Some Outlook connection failures are closely linked with the migration method. So, explore the following migration-specific Outlook connection problems to prevent irrelevant fixes:

Exchange On-Premise/ Hybrid to Microsoft 365

Active Directory and internal networking frequently override the public M365 DNS records in on-premises and hybrid environments. This creates perplexing failures where devices and OWA work fine, but office desktops struggle.

Root Cause 

Affected Client & Symptom  Verification Check 

Exact Fix & Prevention 

Ongoing On-Premises SCP Pointer (and “Ghost” Servers)

Classic Outlook 

(domain-joined computers)

It connects to an inactive internal server or stalls on Autodiscover while OWA and mobile work.

Open Exchange Management Shell and run: 

Get-ClientAccessService | Select-Object Name, AutoDiscoverServiceInternalUri 

Once the mailboxes are moved, clear the SCP once by running: Set-ClientAccessService -Identity “ServerName” -AutoDiscoverServiceInternalUri $null

Open adsiedit.msc  >> Configuration >> CN=Services → CN=Microsoft Exchange → CN=[Org] → … → CN=Protocols → CN=Autodiscover 

Next, remove the orphaned serviceBindingInformation object, or push ExcludeScpLookup = 1 using GPO/Intune.

Missing RemoteRoutingAddress or ExchangeGuid Mismatch

On-premises Autodiscover cannot redirect Outlook to Exchange Online without an appropriate @yourtenant.mail.onmicrosoft.com routing address or matching GUID.

Classic Outlook 

Connection lags, fails to redirect, or rejects the migrated mailbox.

Run on-premises: Get-RemoteMailbox -Identity “[email protected]” | Format-List RemoteRoutingAddress, TargetAddress, ExchangeGuid

Populate the appropriate “@yourtenant.mail.onmicrosoft.com RemoteRoutingAddress / TargetAddress” and make sure the on-premises “ExchangeGUID matches Exchange Online.

Split-Brain Internal DNS Issues

Internal AD forward lookup zone for “yourdomain.com” still retains an “A” record pointing to the legacy Exchange LAN IP

Classic Outlook (Office LAN & VPN)

“Works at home, fails in the office” behaviour.

Run the command: nslookup autodiscover.yourdomain.com from an office/VPN PC and look for a private LAN IP.

Switch the internal DNS “A” record for “autodiscover.yourdomain.com” pointing to “CNAME: pointing to “autodiscover.outlook.com”.

Firewall, Proxy, or TLS Inspection Blocks 

Legacy proxies engineered for RPC-over-HTTP or set up for SSL inspection drop MAPI-over-HTTP and OAuth traffic.

Classic & New Outlook 

Irregular disconnects, blank login prompts, or stalled syncs on corporate networks.

Inspect the same workstation off-network (mobile hotspot) or confirm proxy logs for dropped outlook.office365.com / login.microsoftonline.com traffic.

Exclude Microsoft 365 Optimize and Allow category endpoints from TLS/SSL inspection and proxy authentication.

Cross-Premises Shared Mailbox & Automapping Lags 

User’s primary mailbox is in Exchange Online, and an automapped shared/delegated mailbox (msExchDelegateListLink) remains on-premises (or vice versa).

Classic Outlook 

Stops at “Loading Profile” or loops continuously on password prompts.

Review delegated/shared mailbox locations in Exchange Admin Center and check “msExchDelegateListLink” in AD

Whenever possible, move tightly coupled primary and shared mailboxes in the same migration batch.

 

Microsoft 365 Cross Tenant Migration

In Office 365 tenant to tenant migration cross-tenant transfers, the public email address ([email protected]) usually stays the same. This causes both users and Windows to assume no internal changes have been made.

Also, this migration path often retains users with an Outlook profile configured for the source tenant.

  • Cache Profile, .ost, and Exchange Mailbox GUID Anchoring: Regardless of an unchanged email address, the destination tenant provides a fresh Exchange Mailbox GUID and Microsoft Entra Tenant ID. Trying to resume a pre-migration Classic Outlook profile will definitely trigger “Cannot open your default e-mail folders” errors or silently stop the sync. Therefore, always provision a fresh profile after cutover.
  • Device Entra ID Join & Primary Refresh Token (PRT) Lock-in (classic & New Outlook): This is the most overlooked cause of continuous “AADTS” errors after cross-tenant cutover. If a computer running on Windows 11 is still “Microsoft Entra Joined” or “Hybrid Entra Joined” to the source tenant, Windows Web Account Manager (WAM) automatically populates the old tenant’s Primary Refresh Token into Outlook. Resulting in rolling authentication back to the source tenant in both Classic and New Outlook. To verify on the endpoint, open Command Prompt and run: “dsregcmd /status”.
  • Review “TenantName”, “TenantId”, and “AzureAdPrt: Yes”: Users will hit recurring token loops if the “TenantId” still shows the source tenant. This can be resolved by migrating or rejoining the workstation to the destination Entra ID tenant. Or temporarily disconnect inactive workplace accounts by accessing Windows Settings >> Accounts >> Access work or school.
  • Incomplete Domain Cutover & Verification Locks: Make sure every reference to the source domain (user UPNs, proxy addresses, Microsoft 365 Groups, Teams channels, distribution lists, and SharePoint sites) is switched back to @sourcteenant.onmicorosft.com. Especially before validating a custom domain on the destination tenant. Also, if a premature cutover leaves users signing in with temporary .onmicrosoft.com UPNs while their primary SMTP address is mismatched, Outlook Autodiscover and Modern Auth prompts will fail.
  • DNS TTL Lag & Local Resolve Caching: The split connectivity issues caused by entering cutover weekend with a 24-hour or 48-hour TTL on MX or autodiscover records. In this scenario, half the users move to the new tenant and the other half remains linked to the old tenant. To prevent this always, drop TTLs to 3000 seconds (5minutes) at least 3 days before cutover. Then run “ipconfig/flushdns” on endpoints immediately after DNS changes.
  • New Outlook cloud Metadata CarryOver: New Outlook for Windows syncs accounts by routing metadata to Microsoft’s cloud backend. Therefore, simply shutting down the app or reinstalling it will not delete the outdated source-tenant pointer. To fix this, remove the mailbox by navigating to Settings >> Accounts >> Your Accounts >> run “olk.exe –clearLocalState” from the Run dialog. Lastly, re-add the target tenant.

Pro-Tip: Verify the migration reports against the actual destination mailbox. This is because missing delta synchronization leads to incomplete content. Regardless of whether Outlook itself connects successfully.

GoDaddy, cPanel, or IMAP to Microsoft 365

Root Cause

Affected Client & Symptom  Verification Check 

Exact Fix & Prevention

Classic Outlook checkers [https://yourdomain.com/autodiscover/autodiscover.xml] first. cPanel/GoDaddy web hosting blocks it with legacy IMAP settings.

Retrieves legacy IMAP settings or displays an SSL certificate mismatch pop-up. Run the command in the PowerShell: Invoke-WebRequest -Uri “[https://yourdomain.com/autodiscover/autodiscover.xml](https://yourdomain.com/autodiscover/autodiscover.xml)” -MaximumRedirection 0 -ErrorAction SilentlyContinue | Select-Object StatusCode, Headers 

If the server returns 200, 301/302, or 401 (instead of 404 or refusal), disable the AutoConfig/Autodiscover in WHM/cPanel or configure ExcludeHttpsRootDomain = 1 using registry/GPO.

Remaining GoDaddy Federation (sso.godaddy.com) loop

Classic & New Outlook 

Experiencing blank white sign-in windows or continuous redirects to a broken sso.godaddy.com login page.

Open Microsoft Graph and run: 

Connect-MgGraph -Scopes “Domain.Read.All”

Get-MgDomain -DomainId “yourdomain.com” | Select-Object Id, AuthenticationType, IsVerified

Make sure “AuthenticationType returns “Managed” (complete defederation if it still displays “Federated”). After that, disconnect the old GoDaddy account in Windows Settings >> Accounts >> Access work or school.

Old providers (Intermediate, Rackspace, Network Solutions, cPanel) left “A” records or “ _autodiscover._tcp SRV fallback records.

Classic Outlook 

It silently moves back to the old mail provider whenever the standard HTTPS autodiscover fails.

Try querying public DNS for “A”, “autodiscover._tcp.yourdomain.com SRV” records.

Wipe out all legacy “autodiscover A” records and “autodiscover._tcp SRV” records. Preserve only a single CNAME: autodiscover>> autodiscover.yourdomain.com.

IMAP Profile Carryover  (This computer only) data problem 

Trying to switch server names when an existing IMAP profile breaks sync. Deleting it prematurely removes non-synced local data 

Classic Outlook 

Throws sync failures when denying an IMAP profile. Or deleting Contacts, Calendars, and Tasks, causing permanent loss.

Check the old IMAP mailbox folder list on Classic Outlook for folders tagged (This computer only).

Warning: Before removing the old IMAP profile, export all (This computer only) Contacts, Calendars, and Tasks to a .pst file. Next, create a new Exchange Online profile and import the .pst. 

How to Prevent Outlook Connection Failures and Other Post-Migration Issues

The best approach to prevent broken Outlook endpoints and other post-cutover issues is utilizing a certified & structured migration utility such as the SysTools Office 365 to Office 365 migration tool.

Download Now Purchase Now

Using this software for cross-tenant data transfer can tactfully bypass inconsistencies that occur due to incomplete or inconsistent tenant moves. This includes mismatched mailbox mappings, interrupted batch transfers, missing delta syncs after DNS cutover, or users cut over before archives and permissions finish syncing.

Trivia: Roughly 30% of Microsoft 365 migrations experience at least one major issue, such as data loss, significant downtime, or security misconfiguration.

Enterprise-Grade Features for a Seamless, End-to-End Migration:

  • Automated CSV User and Folder Mapping: Allows accurate mapping of source and destination users in bulk via CSV templates. Ensure mailboxes, aliases, and folder hierarchies reach the correct target accounts, eliminating manual misconfigurations.
  • Concurrent Multi-Workload Transfers: Support for transferring Exchange Online mailboxes, OneDrive documents, SharePoint sites, Teams data, personal chats, shared mailboxes, in-place archives, and public folders in parallel. Allows concurrent user migration for larger projects (20 users at a time per account).
  • Selective and Delta Migration Support: Provides date-range filters to move only relevant data. Delta migration to capture newly provisioned data.
  • Summary Reporting: Provides detailed pre-and post migration summary reports for complete mailbox migration verification.

Where it helps:

  • Preparing user mappings before cutover.
  • Transferring supported workloads in planned batches.
  • Running delta migrations for newly arrived data.
  • Identifying unsuccessful transfers using migration summary information.

Where it does not help:

  • SysTools migration utility does not automatically repair an already broken Outlook profile. Also, it doesn’t clear Windows VAM tokens, fix an outdated Autodiscover SCP, or correct a local firewall. You are still required to verify DNS, licensing, authentication, and Outlook profile configuration separately.

Pro-Tip: To ensure a technically controlled cross-tenant transfer, always maintain a pre-migration account map. Also, inspect destination licensing, validate the final DNS cutover, and analyse migration reports. Only then reconfigure users’ Outlook clients.

Frequently Asked Questions

#1: How long does it take for Outlook to connect after a cross-tenant transfer?

There is no fixed Outlook connection time. However, Outlook usually connects within 15 minutes to 2 hours. It depends on mailbox provisioning, DNS propagation, authentication, and the Outlook profile. And if DNS TTL values were set to 24-48 hours before cutover, some remote users may encounter intermittent delays until the local ISP DNS caches expire.

#2: Do I need to create a new Outlook profile after moving one tenant to another?

Yes. You need to create a new Outlook profile after moving M265 content to another tenant, even if the email address is identical. This is because cross-tenant migration changes the underlying Microsoft Entra Tenant ID, including the Exchange mailbox GUID. Recreating a fresh Classic Outlook profile, or removing and re-adding the account in New Outlook, bypasses .ost mismatches. Including password loops, and “cannot open your default e-mail folders” errors.

#3: Why does Outlook keep asking for my password after moving to M365?

Outlook keeps prompting for a password after moving to the destination tenant because Outlook is using cached legacy credentials in Windows Credential Manager. WAM tokens linked to the previous tenant or server, MFA/Conditional Access checks, and an outdated Office build can also result in repeated authentication prompts. Always investigate Entra sign-in logs before repeatedly resetting passwords. Also, wiping out both Credential Manager and the Windows Access work or school token can break the loop.

#4: Will recreating my Outlook profile delete my emails?

Absolutely not. Creating a new Outlook profile doesn’t delete existing messages stored in the Exchange Online mailbox. Exchange Online emails, calendars, and contacts live on Microsoft’s cloud servers, not in the local Outlook profile. Provisioning a new profile only produces a fresh local cache (.ost file) and re-syncs the mailbox. Only local-only PST archives or non-synced IMAP folders need manual backup. Or re-attachment beforehand. So verify them before removing old profiles or data files.

#5: Does the new Outlook for Windows use Classic Outlook Autodiscover registry keys?

No. New Outlook for Windows connects using cloud-synced Microsoft endpoints and Windows WAM. The Registry overrides, such as ExcludeScpLookup, ExcludeHttpsRootDomain, and ExcludeExplicitO365Endpoint. And only controls Classic Outlook (OUTLOOK.EXE). Therefore, to fix New Outlook connection issues after a tenant move, remove and re-add the account, clear WAM entries, or run olk.exe –clearLocalState.

#6: Why can’t I download Microsoft SaRA to fix Outlook after migration?

The Microsoft SaRA can’t be used to fix Outlook after migration because Microsoft has retired the standalone Microsoft Support and Recovery Assistant (SaRA). Including removing the SaRA command-line utility from Windows starting March 2026.

#7: Why is Outlook still reconnecting to my old Exchange server after moving to the new tenant?

Outlook is still reconnecting to the old Exchange server after migration because the Outlook profile may be using a cached Last Known Good Autodiscover URL. This issue can also occur due to using obsolete Active Directory SCP, or an incorrect HTTPS Autodiscover response. To fix this, review the Autodiscover XML, check DNS, and test a new Outlook profile. Also, rectify the underlying discovery configuration instead of applying multiple registry exclusions without the ordered approach.

#8: Outlook works on the web but not on my desktop. Does that mean my migration failed?

Not necessarily. Successful access to Outlook on the Web means that the destination mailbox is accessible via the web. “Outlook doesn’t work on the desktop” issue is usually a result of a stale Outlook profile, authentication, tokens, Autodiscover, MAPI configuration, or network limitations. You can only treat your mailbox migration as a failure if it is unsuccessful after isolating these client-side factors.