smart relay with exchange 365

Hi-

I am using Exchange 365. We have users in the GAL that are not part of the domain and Exchange just sends the email out.

Now, we are at the point were some of those users need to become part of Exchange 365. Is there a way to setup Smart-hosting so that Exchange doesnt see the user having a mailbox on the system it will forward it to a new server. Even through the user still has an address book entry.

For example:
-Exchange handles mail for (abc.com and xyz.com)
-All users for abc.com are handled by exchange 365
- User joe@xyz.com is handled by exchange 365 and mail gets delivered to his mailbox
-User jane@xyz.com is NOT handled by exchange 365 and all mail will be pushed to somesmtpserver.xyz.com
*** Note Jane is still in the GAL but does not have a license or mailbox on Exchange 365.

Thanks in advance
doctor069Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy LidbetterCommented:
Hi There,

From what you are saying, the users are contacts... not mailboxes.
These need to be manually created, you cannot sync up contacts.

Here is a good blog on how to migrate contacts from on prem to O365 using PowerShell scripts.

Office 365 – How to migrate contacts from Exchange

Regards

Guy
0
Vasil Michev (MVP)Commented:
You can configure the xyz.com domain as internal relay and use the so-called "simple domain sharing" method as detailed here: https://support.office.com/en-us/article/domains-faq-1272bad0-4bd4-4796-8005-67d6fb3afc5a?ui=en-US&rs=en-US&ad=US#bkmk_pilot

That way, if Exchange Online finds a matching recipient in O365 it will deliver the message internally, otherwise it will send it to where the MX record points at. Needless to say, the MX record should not point to O365, but to your other system.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
doctor069Author Commented:
That did the trick. Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.