09-18-2017 06:06 AM
09-18-2017 06:06 AM
Lately I have been running into an issue with trying to email to an Office 365 group with an external email address. Even with the group having external email enabled, none of the email ecternally is coming through. Does anyone know how this can be fixed?
09-18-2017 07:22 AM
09-18-2017 07:36 AM
This has been an issue from the start. We are trying to have this work and unable to do so. I am not sure that other steps have taken place to ensure external emails can send to Office 365 groups.
09-18-2017 08:15 AM
09-18-2017 08:19 AM
When i look into Message trace on our Ironport I do see that the message was delievered. However when I look on message trace I do not see that anything came through. Is there something specific that needs to happen with Azure such as write back?
09-18-2017 10:53 AM
09-18-2017 11:17 AM
09-18-2017 11:34 AM
Can you do a message trace? Also, there have been some issues with Exchange online for Anti-x piece. Can you look at your spam configurations or quarantine emails? There have been issues going on with message quarantine for last few days with O365 tenant.
09-18-2017 11:50 AM
Hi Steve. My IronPort is telling me that the message is queued for delivery. I believe that this is a mail flow issue. Comes in externally, hits IronPort and then once it hits exchange online, it is not routing correclty to on-prem. In my Delivery scop options for outbound to office 365 within EAC I am seeing there is only firstname.lastname@example.org there. I am going to attempt to add email@example.com along with routing mail through smart host, to see if this makes a difference.
09-18-2017 12:16 PM
08-26-2020 09:50 AM - edited 08-26-2020 09:51 AM
@Tim Ihrig, please make sure, your Domain DNS settings are set up correctly, especially the MX-Record.
Go to: https://admin.microsoft.com/AdminPortal/Home#/Domains and check, if everything shows up ok.
One common problem in your case is caused, when a migration from Exchange on premises is not yet completed to Exchange Online and the DNS-MX record is still targeting the on premises Exchange, which does not know the MS 365 groups.
In that case, the sender might e.g. receive an e-mail error message containing:
autodiscover.[your e-mail domain] Mail delivery failed : returning message to sender