Forum Discussion
Can't send messages between O365 domains
- Feb 07, 2019
Go to the EAC and configure domain1 as Internal Relay. That way Exchange will no longer try to deliver the messages internally, but instead will look at the MX record and send them on-premises.
Thanks Vasil.
I already tried to do that, but wasn't able to configure connector. It was saying that I cant use email address hosted on O365 for connector validation.
I thought that it meant I cant use email in domain hosted on O365, but the trick was to use unlicensed user.
I'll set up connector , but probably will need help of my Exchange hosting operator, because I'm not sure about correct exchange server name and other settings.
There's no need for connectors in your scenario, ignore the warning.
- Andy_BondFeb 11, 2019Copper Contributor
I found the workaround for that.
If a user@domain1.com has never had mailbox created on O365, I can send messages to him and they get to Exchange on-premise.
But here we'll need to delete O365 mailboxes for all users without deleting O365 users.
It seems like just disabling Exchange online license for a user doesn't work, because we need to wait 30 days for a mailbox to be actually deleted.
Is there some way to delete mailbox immediately?
Thanks
- VasilMichevFeb 11, 2019MVP
Yes, you can do a
Disable-Mailbox
user-PermanentlyDisable- Andy_BondFeb 13, 2019Copper Contributor
Thank you for help Vasil,
I was trying to run it, but it was saying that there is on-place hold.
I searched for a holds, retention policies and so on...
But the trick was just to use this parameter -IgnoreLegalHold
Whereas the account wasn't showing any litigation holds, but.. it worked for me.
One thing you need to know is that licenses should be removed from user to use this cmdlet.
Disable-mailbox <username> -IgnoreLegalHold -PermanentlyDisable
- Andy_BondFeb 11, 2019Copper Contributor
Hi Vasil,
Domain 1 is configured as Internal relay for several days, but messages are still going to Exchange Online mailboxes.