Forum Discussion
External Email recieved by 365 Groups
We have figured out what we can do (hopefully). We are going to change our MX record to point to 365. Once that is done, we have written a script that will create placeholders in 365, allow us to remove the on-premise DL, then rerun the script with a Finish parameter that changes the group name and primary SMTP over to the actual DL. Doing it this way, we can move smaller sections of DLs and keep the disruption to the business to a minimum.
I will write back to confirm this works.
Jason
I have created an Uservoice some time ago about this. this is regarding aliases in the office Group.
https://office365.uservoice.com/forums/286611-office-365-groups/suggestions/17439772-make-a-group-alias-available-for-receiving-externa
Thanks for the response. I have looked into and tried both, with the following results:
VasilMichev - Not sure what the attribute is specifically called, but we do not have the premium subscription to Azure, so the article says it won't work anyway.
Jerry Meyer - Tried your solution to add the onmicrosoft.com smtp address as primary and let it sync. Still no go.
Here is what I am trying and what I am recieving.
I have a on-premise distribution group with one member. That member is a contact with the email address as testold@<domain>.com and a target address with TestGroup01@<tenant>.mail.onmicrosoft.com (can't use the <tenant>.onmicrosoft.com address because it tells me that address can not be used to route mail). When I try to send to the on-premise account, it reaches the contact then gives me an NDR stating the target email is restricted and requires authentication. But the attribute -RequireSenderAuthenticationEnabled is set to $false, and the accept messages are set to "All Senders" and the reject set to "No senders".
Not sure what I am missing, but do you have any other suggestions?
Jason
I have found an Blog with a suggested work arround. http://www.michev.info/Blog/Post/1071/5-4-1-ndrs-when-sending-external-messages-to-modern-groups-aka-dbeb-and-groups-dont-play-well-together
Maybe your answer is in there.Edit: After i posted it i noticed that it is Vasil's Blog :)
Thanks, but already been through that one as well. Doesn't work in my situation.
Got anything else?
Jason
Jason, we have the same config (hybrid with on-prem and cloud groups). Our primary email domain umail.miami.edu still goes to our on-prem servers first and then cloud. After we migrate our groups, we create a contact on-prem with the external address of group@tenant.onmicrosoft.com. I'm not usre why you're getting "(address can not be used to route mail)." Here is a screenshot of the email properties of one of our groups.
