none
Outlook email reply from a on-prem exchange account with a different address like outlook_DE17DABEEA3868F7@outlook.com RRS feed

  • 问题

  • Hi experts, 

    recently some of Outlook email user of on-premises exchange account found that when they reply email, their FROM address auto changed to a different address like outlook_DE17DABEEA3868F7@outlook.com, instead of their usual business email address username@companydomian.

    Would you be able to share with me, the cause why this happen,  the solution how to prevent it or fix it?

    Thank you for your time.

    pingatwork

    2021年1月20日 1:59

全部回复

  • Hi,

    Welcome to our forum. According to your description, your issue seems to be more related to Exchange account instead of Outlook desktop client, in order to solve your issue better, I moved your thread to the exchange forum, thanks for your understanding.

    Besides, due to here we mainly focus on chinese issue now, and the English forum has been migrated to Microsoft Q&A forum. If you still need English support, it is suggested to post your issue and updates in the Microsoft Q&A Outlook forum and we would continue to research it with you there, thanks for your understanding and hope your issue would be resolved soon.

    Regards,

    Jade Liang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact:tnsf@microsoft.com.

    2021年1月20日 5:48
  • Hi,

    Welcome to the Exchange forum.


    Sorry I need to ask the following questions in order to get some more information:

    1.What version of Exchange(including CU version) are you using? Is it a hybrid environment deployed with Microsoft 365?

    2.Did the "outlook_DE17DABEEA3868F7@outlook.com" appear to be from address on the recipients' side?

    3.Does the problem only occur when the affected users reply to emails? If they send emails directly instead, will the problem persist?

    4.Do the affected users have outlook.com accounts configured in their Outlook clients?

    If so, please confirm if the users are actually sending messages with their Exchange accounts.


    According to this article:Fixes or workarounds for recent issues on Outlook.com

    it seems to be the known issue on Outlook.com accounts.


    Here are some suggestions:

    1.Please try using OWA for test and see if the affected users have the same problem.

    2.If the problem is only with Outlook clients, please recreate the Outlook profiles for the affected users and see if the problem persists.


    Regards,

    Kael Yao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    • 已编辑 Kael Yao 2021年1月20日 8:35
    • 已建议为答案 Kael Yao 2021年1月21日 8:10
    2021年1月20日 8:33
  • Hi Jade,  

    noted and thank you very much for the info.

    pingatwork

    2021年1月21日 9:47
  • Hi Kael,

    Thanks for pointing me to this article:Fixes or workarounds for recent issues on Outlook.com

    1.What version of Exchange(including CU version) are you using? Is it a hybrid environment deployed with Microsoft 365?  

    ON-Prem EX2016 Version 15.1 ‎(Build 1713.5)‎ Standard, no MS365.

    2.Did the "outlook_DE17DABEEA3868F7@outlook.com" appear to be from address on the recipients' side?

     yes

    3.Does the problem only occur when the affected users reply to emails? If they send emails directly instead, will the problem persist?

    yes when replying email

    4.Do the affected users have outlook.com accounts configured in their Outlook clients?

    no, 

    If so, please confirm if the users are actually sending messages with their Exchange accounts.



    2021年1月21日 9:54
  • Hi,

    Thanks for your information.

    Are the affected users using Outlook 2016 16.0.6741.2017 and later versions?

    You can refer to this article on how to check the version of Outlook.


    If so,please follow these steps:

    1.Start "regedit.exe" on the affected clients

    2.Locate "HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover"

    3.Create a DWORD value named "ExcludeExplicitO365Endpoint" and change the value to "1"

    Restart Outlook and see if the problem persists.


    If it doesn't help with your problem,please run a Test E-mail autoconfiguration via affected Outlook clients to check if the autodiscover process works properly.

    You may also try migrating the affected user mailboxes to another database to see if it can solve this problem.

    Regards,

    Kael Yao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    2021年1月22日 7:16