Link to home
Start Free TrialLog in
Avatar of Joergen Lind
Joergen LindFlag for Denmark

asked on

Outlook doesn't detect that a mailbox has been migrated to Office 365

We're in the process of migrating our On-Premise Exchange 2013 CU12 to Office 365.
  • Everything is set up.
  • Azure AD Connector is handling the account synchronization
  • It's a hybrid setup.
  • I've migrated a mailbox without errors.
The Mac running Office 365, (Version 16.18) picked up the change in mailserver, prompted for my Office365 login and continued working as before, except it is connecting to Office365.

Now, the PC client, using the same mailbox (it's not a shared mailbox, I'm just running on a PC and a Mac concurrently)  is not so fortunate. The PC is on a Windows domain, the user is logging on to the PDC with DOMAIN\account login.
The Outlook (Outlook for Office 365 MSO (16.0.10827.20118) doesn't pick up the change in mailserver. Instead it connects to the on-premise Exchange Server and says that the mailbox was last updated on Oct 16 2018.

If I run an Autodiscover test from the PC Outlook client, it looks very nice:

<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="">
  <Response xmlns="">
      <DisplayName>My account</DisplayName>
      <LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=37345743bcd0a45d6a18aff6-accountname</LegacyDN>
      <Protocol Type="mapiHttp" Version="1">
          <OWAUrl AuthenticationMethod="LiveIdFba, OAuth"></OWAUrl>
          <OWAUrl AuthenticationMethod="Fba"></OWAUrl>
        <DisplayName>SharedMailbox1 name</DisplayName>
        <DisplayName>SharedMailbox2 Name</DisplayName>

Open in new window

So, why doesn't Outlook pick up the changes.

This is a test migration that should reflect any user in our organisation. So, deleting the Outlook account and setting it up again it NOT the solution that I am looking for.

The mailbox in the iPhone (native App), also doesn't pick up the changes, but I'm not entirely sure if this is expected behavior.

Thanks for any input and/or directions.

Have a great day!

Avatar of Pete Long
Pete Long
Flag of United Kingdom of Great Britain and Northern Ireland image

If you create a new outlook profile on the PC does that connect OK?

Ive seen incorrect auto configure.xml files get 'stuck' in peoples profiles before?

Avatar of Joergen Lind


Yes. If I set up a new profile, the setup and server connection works fine. Even the shared mailboxes, still remaining on the on-premise server, are accessible.
If it's the profile-related issue, you can recreate Outlook profiles for all users automatically via GPO. Here is a video tutorial on how to do this:
How to recreate Outlook profiles
@CodeTwo Software. Nice little video. Good to know.

I do, however, want to keep all the settings, windows sizes etc. etc. that the users has made over time, so re-creating a profile is my last resort - even if it is done automatially via a GPO.
Just thinking - maybe it's because the Outlook client queries the AD and obtain the Exchange server information from the AD, and therefore skips the autodiscovery steps.

Since the non-domain joined mac didn't have these issues, it may be the reason.

Just thinking out loud.
Avatar of Joergen Lind
Joergen Lind
Flag of Denmark image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial