none
On Premise users see email address of O365 users instead of display names in emails

    Frage

  • Hi Team,

    We have a Hybrid setup configured between Exchange 2010 and Office 365.
    The mail flow is working fine.
    Now when the migrated users sends an email to On Premise user the senders email address (O365) is seen as email address instead of display names.

    Can someone help us to troubleshoot this issue.

    Regards,
    Mitesh Jain

    Donnerstag, 18. Mai 2017 06:24

Alle Antworten

  • Hi Mitesh,

    Here is an article explains why this issue occurred, it would help you solve this issue:

    Email messages that are sent from the on-premises environment to Office 365 show email addresses instead of display names in the From field

    CAUSE

    This issue occurs if the hybrid deployment is set up incorrectly. 

    To verify that you're experiencing this issue, examine the email header of an email message that was sent from the on-premises user account. Typically, X-MS-Exchange-Organization-AuthAs should be listed as "Internal." If X-MS-Exchange-Organization-AuthAs is listed as "anonymous" or if it's missing, this indicates an incorrect configuration or an incorrect mail route.

    SOLUTION

    To fix this issue, follow these steps:
    1. Check the mail route. 

      The simplest route is Exchange 2010 mailbox server to Exchange 2010 hub server (hybrid server) to the Exchange Online Protection (EOP) inbound connector to Exchange Online. Make sure that there are no unnecessary network devices such as anti-spam gateway devices between the Exchange 2010 hub server (hybrid server) and EOP. Those devices could remove the necessary header.
    2. Check the remote domain of the on-premises Exchange server. To do this, follow these steps:
      1. In Exchange Management Shell, run the following PowerShell command:

        Get-RemoteDomain < NameOfService>.< DomainName>.com | FL 
        For example: 

        Get-RemoteDomain exchangedelegation.contoso.com | FL 
      2. In the output, make sure that the TrustedMailOutboundEnabledTargetDeliverDomain, and IsInternal attributes are set to True.
      3. If the attributes in step 2B aren't set to True, use the Set-RemoteDomain command to change the value to True.
    3. Check the remote domain in Office 365. To do this, follow these steps:
      1. Connect to Exchange Online by using remote PowerShell. For more info about how to do this, see Connect to Exchange Online using remote PowerShell.
      2. Run the following PowerShell command:

        Get-RemoteDomain <FQDNOfOnPremisesEndConnector> | FL  
      3. In the output, make sure that the TrustedMailnboundEnabled attribute is set to True.
      4. If the attribute in step 3C isn't set to True, use the Set-RemoteDomain command to change the value to True.
    4. Make sure that Transport Layer Security (TLS) is implemented and enabled in both environments and that the fully qualified domain name (FQDN) is set correctly. Check the on-premises send connector and the EOP inbound connector by using the Exchange Server Deployment Assistant at the following Microsoft website:
    5. Check the Exchange certificate of the send connector on the on-premises Exchange servers that are responsible for delivering mail to EOP. The Exchange certificate should have Simple Mail Transfer Protocol (SMTP) enabled and should match the FQDN of the send connector.
    Best Regards,


    Niko Cheng
    TechNet Community Support


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


    Freitag, 19. Mai 2017 03:19
    Moderator
  • Hi mitesh,

    Just checking in to see if above information was helpful. Please let us know if you would like further assistance. If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well.

    Thanks for your understanding.

    Best Regards,


    Niko Cheng
    TechNet Community Support


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

    Montag, 22. Mai 2017 10:00
    Moderator
  • HI Niko,

    Thank You for the reply.

    I have gone through this  article. However there is only one remote domain in O365 as *. so not sure how the command

    Get-RemoteDomain <FQDNOfOnPremisesEndConnector> | FL  

    will work on O365 tenant

    What does FQDNONPremiSESEndConnector mean in the above command.

    Dienstag, 23. Mai 2017 09:48

  • What does FQDNONPremiSESEndConnector mean in the above command.

    It looks that the FQDNONPremiSESEndConnector is a DNS name of the host which is sending out mail from on-premise to Exchange online (Outbound connector). 

    I am facing the same issue and in the EOL I had only one remote domain which was *. 

    I have created another one which reflects the DNS of my Exchange 2016 Outbound->O365 connector and set its TrustedMailnboundEnabled to $true but it didn't resolve the issue. 

    Have you come across any solution?


    BR Michal Ziemba



    Freitag, 30. März 2018 11:40