We help IT Professionals succeed at work.

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

514 Views
Last Modified: 2018-10-25
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="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
  <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
    <User>
      <DisplayName>My account</DisplayName>
      <LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=37345743bcd0a45d6a18aff6-accountname</LegacyDN>
      <AutoDiscoverSMTPAddress>accountname@contoso.com</AutoDiscoverSMTPAddress>
      <DeploymentId>8e854a31-da1d-1456-a0f9-c86572a65bde</DeploymentId>
    </User>
    <Account>
      <AccountType>email</AccountType>
      <Action>settings</Action>
      <MicrosoftOnline>True</MicrosoftOnline>
      <ConsumerMailbox>False</ConsumerMailbox>
      <Protocol Type="mapiHttp" Version="1">
        <MailStore>
          <ExternalUrl>https://outlook.office365.com/mapi/emsmdb/?MailboxId=5f3dc90-2bf0-4566-99a0-546ae3b@contoso.com</ExternalUrl>
        </MailStore>
        <AddressBook>
          <ExternalUrl>https://outlook.office365.com/mapi/nspi/?MailboxId=5f3dc90-2bf0-4566-99a0-546ae3b@contoso.com</ExternalUrl>
        </AddressBook>
      </Protocol>
      <Protocol>
        <Type>WEB</Type>
        <Internal>
          <OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
          <Protocol>
            <Type>EXCH</Type>
            <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
          </Protocol>
        </Internal>
        <External>
          <OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/contoso.com/</OWAUrl>
          <Protocol>
            <Type>EXPR</Type>
            <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
          </Protocol>
        </External>
      </Protocol>
      <Protocol>
        <Type>EXHTTP</Type>
        <Server>outlook.office365.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Basic</AuthPackage>
        <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
        <EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
        <EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
        <SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
        <EcpUrl>https://outlook.office365.com/owa/</EcpUrl>
        <EcpUrl-um>?path=/options/callanswering</EcpUrl-um>
        <EcpUrl-aggr>?path=/options/connectedaccounts</EcpUrl-aggr>
        <EcpUrl-mt>options/ecp/PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=contoso.com</EcpUrl-mt>
        <EcpUrl-ret>?path=/options/retentionpolicies</EcpUrl-ret>
        <EcpUrl-sms>?path=/options/textmessaging</EcpUrl-sms>
        <EcpUrl-publish>?path=/options/calendarpublishing/id/&lt;FldID&gt;</EcpUrl-publish>
        <EcpUrl-photo>?path=/options/myaccount/action/photo</EcpUrl-photo>
        <EcpUrl-connect>?path=/options/socialnetworks&amp;ignore1=&lt;Action&gt;&amp;ignore2=&lt;Provider&gt;</EcpUrl-connect>
        <EcpUrl-tm>options/ecp/?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tm>
        <EcpUrl-tmCreating>options/ecp/?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmCreating>
        <EcpUrl-tmEditing>options/ecp/?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmEditing>
        <EcpUrl-extinstall>?path=/options/manageapps</EcpUrl-extinstall>
        <OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
        <UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
        <OABUrl>https://outlook.office365.com/OAB/cd4567a-45f1-43ce-bffe-67de346790/</OABUrl>
        <ServerExclusiveConnect>On</ServerExclusiveConnect>
      </Protocol>
      <AlternativeMailbox>
        <Type>Delegate</Type>
        <DisplayName>SharedMailbox1 name</DisplayName>
        <SmtpAddress>SharedMailbox1@contoso.com</SmtpAddress>
        <OwnerSmtpAddress>SharedMailbox1@contoso.com</OwnerSmtpAddress>
      </AlternativeMailbox>
      <AlternativeMailbox>
        <Type>Delegate</Type>
        <DisplayName>SharedMailbox2 Name</DisplayName>
        <SmtpAddress>sharedmailbox2@contoso.com</SmtpAddress>
        <OwnerSmtpAddress>sharedmailbox2@contoso.com</OwnerSmtpAddress>
      </AlternativeMailbox>
    </Account>
  </Response>
</Autodiscover>

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.

Bonus:
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!


Bjorn
Comment
Watch Question

Pete LongTechnical Architect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
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?

Pete
Joergen LindSysAdm

Author

Commented:
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.
Adam the 32-bit AardvarkSoftware Developer
CERTIFIED EXPERT

Commented:
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
Joergen LindSysAdm

Author

Commented:
@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.
Joergen LindSysAdm

Author

Commented:
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.
SysAdm
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.