Geekzone: technology news, blogs, forums
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.

542 posts

Ultimate Geek
+1 received by user: 43

Lifetime subscriber

Topic # 242632 6-Nov-2018 16:48
One person supports this post
Send private message quote this post

A lot of head scratching went on with this issue so thought I'd share for the benefit of others.


I had one user complain that they had sent an email and the receiver went to reply and the address error-ed out. The receiver forwarded me the message and the sender address was in the following format


outlook_<random 16 character alphanumeric>


This was particularly weird as we have our own on premise Exchange Server and don't use Office365 or


The sent message was in the users sent messages in their exchange mailbox, but the message wasn't in the Exchange tracking logs.


It turns out that Microsoft has recently created mailboxes for personal Microsoft Account holders and Outlook 2016's implementation of Autodiscover has a failing where it it tries Office 365 before SCP or any other methods. As the users logon details were the same for their Exchange Mailbox as their Microsoft Account (yes I know, I know....), they were prompted at some stage for their password, which they duly entered and Voila! Autodiscover starting sending some outgoing messages (internal and external addresses) via while still retaining and using the Exchange mailbox for storage. Other messages were delivered normally as usual.


Anyway - thank to a handy Reddit post this Autodiscover "feature" can be disabled.


The fix is to create the following Registry key on affected machine:


Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\AutoDiscover (x.0 corresponds to the Outlook version: 16.0 = Outlook 2016)


For Outlook 2016 version 16.0.6741.2017 and later versions, please add the following


DWORD: ExcludeExplicitO365Endpoint
value 1


Hope this helps someone..


References below







Create new topic
18784 posts

Uber Geek
+1 received by user: 5385

Lifetime subscriber

  Reply # 2121349 7-Nov-2018 10:04
Send private message quote this post

Thanks for sharing, we got a few customers hit with this today. 

41 posts

+1 received by user: 7

  Reply # 2123907 12-Nov-2018 08:56
Send private message quote this post

Hit this issue with the Registry keys in a pre-365 migration (Internal Migration), Azure AD Connect was in place so I had about 5 users out of 60 intermittently logging into the 365 mailboxes and sending emails that routed internally in 365 and never arrived with users whose Outlook was still looking at Exchange. Users didn't get prompted for passwords because of AD Connect.

Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:

Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:

Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:

Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.

Geekzone Live »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.