Can 365 ignore internal domains when routing email?

%3CLINGO-SUB%20id%3D%22lingo-sub-264991%22%20slang%3D%22en-US%22%3ECan%20365%20ignore%20internal%20domains%20when%20routing%20email%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-264991%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20a%20conundrum%20I've%20got%20concerning%20Users%20accessing%20365%20services%20whose%20email%20is%20provided%20by%20Google%2FG%20Suite.%20We%20currently%20have%20two%20primary%20groups%20of%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGroup%20A%20Users%20have%20their%20emails%20hosted%20by%20Office%20365.%3C%2FP%3E%3CP%3EGroup%20B%20Users%20have%20their%20emails%20hosted%20by%20G%20Suite.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGroup%20A%20can%20currently%20access%20all%20service%20just%20fine%20as%20all%20services%2C%20including%20Email.%20If%20Group%20B%20is%20set%20up%20in%20the%20same%20manner%20as%20the%20above%20with%20the%20exception%20of%20email%2C%20any%20email%20sent%20internally%20between%20Group%20A%20and%20Group%20B%20fails%20as%20it%20is%20assumed%20that%20Group%20B's%20email%20is%20hosted%20by%20365%2C%20and%20so%20doesn't%20reach%20them.%20Any%20email%20sent%20from%20any%20other%20domain%2C%20i.e.%20Yahoo%2C%20to%20Group%20B%20works%20perfectly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20the%20above%20makes%20sense.%20I%20would%20appreciate%20any%20advice%20regarding%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-264991%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-267565%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20365%20ignore%20internal%20domains%20when%20routing%20email%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-267565%22%20slang%3D%22en-US%22%3E%3CP%3EOkay%2C%20that%20cleared%20a%20lot!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%26nbsp%3B%3CSTRONG%3Email%20routing%3C%2FSTRONG%3E%2C%20the%20solution%20is%20same%3A%20set%20the%20domain%26nbsp%3B%3CSTRONG%3Egroupb.ourdomain.com%3C%2FSTRONG%3E%20as%26nbsp%3B%3CSTRONG%3EInternal%20Relay%3C%2FSTRONG%3E.%20That%20changes%20the%20behavior%20so%20that%20if%20you%20send%20email%20to%20example%40groupb.ourdomain.com%2C%20and%20mailbox%20is%20not%20found%20from%20Office%20365%2C%20it%20is%20sent%20to%20where%20MX%20record%20points%20to%20(%3DGoogle).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20that%20is%20already%20setup%2C%20then%20the%20problem%20is%20that%20users%20have%20the%20mailbox%20in%20Office%20365.%20So%2C%20either%20use%26nbsp%3B%3CSTRONG%3EOffice%20365%20ProPlus%3C%2FSTRONG%3E%20license%20(which%20is%20cheaper%20than%20for%20instance%20E3)%2C%20or%20use%20E3%20but%20disable%26nbsp%3BExchange%20Online.%20That%20way%20users%20don't%20have%20mailboxes%20so%20their%20emails%26nbsp%3Bwill%20be%26nbsp%3Brouted%20to%20Google.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-267481%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20365%20ignore%20internal%20domains%20when%20routing%20email%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-267481%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Nestori%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20not%20sure%20if%20I've%20explained%20myself%20very%20well%2C%20sorry.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EGroup%20A%20have%20Microsoft%20Accounts%20and%20have%20their%20Mail%20Services%20provided%20by%20the%20365%20Exchange%20platform.%20%3CSPAN%3EThese%20email%20accounts%20are%20example%40ourdomain.com%20%5Bexample%5D.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3EGroup%20B%20have%20Google%20Accounts%20and%20have%20their%20Mail%20Services%20provided%20by%20the%20Gmail%2FG%20Suite%20for%20Education%20platform.%20These%20email%20accounts%20are%20example%40groupb.ourdomain.com%20%5Bexample%5D.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20would%20like%20for%20Group%20B%20to%20be%20able%20to%20log%20in%20to%20the%20Office%20365%20service%20so%20that%20they%20may%20download%20and%20install%20the%20Office%202016%20applications.%20However%2C%20we%20have%20found%20that%20if%20we%20create%20them%20an%20account%20for%20the%20Office%20365%20platform%20for%20the%20purpose%20of%26nbsp%3Bacessing%20Office%20applications%2C%20any%20email%26nbsp%3Bsent%20internally%20from%20the%20Group%20A%20to%20Group%20B%20fails%20as%20it%20can%20not%20find%20an%20email%20account%20for%20it%20as%20it%20attempts%20to%20route%20email%20internally.%20This%20would%20otherwise%20work%2C%20if%20there%20are%20no%26nbsp%3B%3CSPAN%3E%40groupb.domain.com%20accounts%20in%26nbsp%3Bplace%20on%20365.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20I've%20made%20it%20a%20bit%20cleared%20so%20that%20you%20may%20better%20understand%20-%20thanks%20for%20your%20help!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-267456%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20365%20ignore%20internal%20domains%20when%20routing%20email%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-267456%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Patrick%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20understood%20correctly%20from%20your%20previous%20posts%2C%20your%20MX%20records%20points%20to%20Google%20and%20you%20forward%20mail%20from%20there%20to%20Office%20365.%20If%20so%2C%20all%20you%20need%20to%20do%20is%20to%20go%20to%20%3CSTRONG%3EExchange%20Online%20admin%20center%3C%2FSTRONG%3E%2C%26nbsp%3Bgo%20to%20%3CSTRONG%3Email%20flow%3C%2FSTRONG%3E%20and%20change%20to%20%3CSTRONG%3Eaccepted%20domains%3C%2FSTRONG%3E%20tab.%20Then%20double-click%20the%20domain%20in%20question%20and%20change%26nbsp%3B%3CSTRONG%3EThis%20accepted%20domain%20is%3C%2FSTRONG%3E%20to%26nbsp%3B%3CSTRONG%3EInternal%20Relay%3C%2FSTRONG%3E%20and%20click%20save.%20You%20will%20get%20a%20warning%20about%20missing%20outbound%20connector%2C%20but%20because%20your%20MX%20points%20to%20Google%2C%20that%20is%20not%20an%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20should%20do%20it%2C%20let%20us%20know%20whether%20it%20worked.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266191%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20365%20ignore%20internal%20domains%20when%20routing%20email%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266191%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Vasil%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20for%20the%20slow%20response.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20looks%20promising%2C%20but%20I%20am%20still%20unsure%20this%20is%20what%20we%26nbsp%3Bwill%20need%20to%20do.%20We%20spoke%20to%20Microsoft%20phone%20support%20and%20it%20was%20advised%20the%20proposed%26nbsp%3Bsetup%20we%20want%26nbsp%3Bis%20not%20going%20to%20work%2C%20or%20at%20least%20reliably%20so%2C%20to%20do%26nbsp%3Bwhat%20we%20want%20to%20do.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%26nbsp%3Bwe'll%20need%20to%20rethink.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20both%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265278%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20365%20ignore%20internal%20domains%20when%20routing%20email%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265278%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20will%20need%20to%20setup%20the%20so-called%20%22simple%20domain%20sharing%22%2C%20as%20detailed%20for%20example%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fdomains-faq-1272bad0-4bd4-4796-8005-67d6fb3afc5a%23bkmk_pilot%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fdomains-faq-1272bad0-4bd4-4796-8005-67d6fb3afc5a%23bkmk_pilot%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20any%20case%2C%20you%20will%20need%20to%20configure%20some%20sort%20of%20forwarding%20to%20handle%20the%20flow.%20Depending%20on%20the%20setup%20you%20can%20either%20do%20%22regular%22%20user-level%20forwarding%20or%20set%20up%20connectors%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265201%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20365%20ignore%20internal%20domains%20when%20routing%20email%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265201%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Juan%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20response.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20in%20between%20at%20the%20moment.%20Group%20A%20needs%26nbsp%3Bthe%20benefits%20of%20being%20on%26nbsp%3BOffice%20365%2C%20whilst%20B%20need%20the%20benefits%20of%20being%20on%20Google.%20Not%20the%20ideal%20situation%20to%20be%20in%2C%20but%20we're%26nbsp%3Bcaught%20at%20the%20moment.%20It%20boils%20down%20to%20education%20needs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20what%20you're%20saying%20though%20it%20sounds%20like%20it%20can't%20be%20done.%20I%20would%20have%20thought%20there%20was%20some%20way%20we%20could%20force%20Office%20365%20to%20ignore%20internal%20accounts%20for%20email%20routing.%20So%20as%20it%20stands%20you%20have%20to%20have%20email%20hosted%20-%20not%20just%20the%20account%20-%20with%20365%20in%20order%20for%20the%20other%20Office%20365%20services%20to%20be%20accessed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20not%20making%20a%20lot%20of%20sense%20myself%20when%20reading%20it%20back%2C%20but%20I%20hope%20someone%20can%20decipher%20what%20I'm%20saying!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20again%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265106%22%20slang%3D%22en-US%22%3ERe%3A%20Can%20365%20ignore%20internal%20domains%20when%20routing%20email%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265106%22%20slang%3D%22en-US%22%3EWhich%20platform%20is%20the%20master%20in%20terms%20of%20e-mail%3A%20Google%20or%20Office%20365%3F%20I%20guess%20Google%2C%20if%20so%20you%20have%20to%20have%20both%20Group%20of%20users%20in%20Google%20and%20configure%20e-mail%20redirection%20for%20the%20Group%20of%20users%20that%20is%20already%20in%20Office%20365%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi all,

 

This is a conundrum I've got concerning Users accessing 365 services whose email is provided by Google/G Suite. We currently have two primary groups of users.

 

Group A Users have their emails hosted by Office 365.

Group B Users have their emails hosted by G Suite.

 

Group A can currently access all service just fine as all services, including Email. If Group B is set up in the same manner as the above with the exception of email, any email sent internally between Group A and Group B fails as it is assumed that Group B's email is hosted by 365, and so doesn't reach them. Any email sent from any other domain, i.e. Yahoo, to Group B works perfectly.

 

I hope the above makes sense. I would appreciate any advice regarding this.

 

Thanks!

7 Replies
Highlighted
Which platform is the master in terms of e-mail: Google or Office 365? I guess Google, if so you have to have both Group of users in Google and configure e-mail redirection for the Group of users that is already in Office 365
Highlighted

Hi Juan,

 

Thanks for the response.

 

We're in between at the moment. Group A needs the benefits of being on Office 365, whilst B need the benefits of being on Google. Not the ideal situation to be in, but we're caught at the moment. It boils down to education needs.

 

From what you're saying though it sounds like it can't be done. I would have thought there was some way we could force Office 365 to ignore internal accounts for email routing. So as it stands you have to have email hosted - not just the account - with 365 in order for the other Office 365 services to be accessed?

 

I'm not making a lot of sense myself when reading it back, but I hope someone can decipher what I'm saying!

 

Thanks again,

Highlighted

You will need to setup the so-called "simple domain sharing", as detailed for example here: https://support.office.com/en-us/article/domains-faq-1272bad0-4bd4-4796-8005-67d6fb3afc5a#bkmk_pilot

 

In any case, you will need to configure some sort of forwarding to handle the flow. Depending on the setup you can either do "regular" user-level forwarding or set up connectors, etc.

Highlighted

Hi Vasil,

 

Sorry for the slow response.

 

This looks promising, but I am still unsure this is what we will need to do. We spoke to Microsoft phone support and it was advised the proposed setup we want is not going to work, or at least reliably so, to do what we want to do.

 

I think we'll need to rethink.

 

Thanks both,

Highlighted

Hi Patrick,

 

If I understood correctly from your previous posts, your MX records points to Google and you forward mail from there to Office 365. If so, all you need to do is to go to Exchange Online admin center, go to mail flow and change to accepted domains tab. Then double-click the domain in question and change This accepted domain is to Internal Relay and click save. You will get a warning about missing outbound connector, but because your MX points to Google, that is not an issue.

 

That should do it, let us know whether it worked.

Highlighted

Hi Nestori,

 

I'm not sure if I've explained myself very well, sorry.

 

  • Group A have Microsoft Accounts and have their Mail Services provided by the 365 Exchange platform. These email accounts are example@ourdomain.com [example].
  • Group B have Google Accounts and have their Mail Services provided by the Gmail/G Suite for Education platform. These email accounts are example@groupb.ourdomain.com [example].

 

We would like for Group B to be able to log in to the Office 365 service so that they may download and install the Office 2016 applications. However, we have found that if we create them an account for the Office 365 platform for the purpose of acessing Office applications, any email sent internally from the Group A to Group B fails as it can not find an email account for it as it attempts to route email internally. This would otherwise work, if there are no @groupb.domain.com accounts in place on 365.

 

I hope I've made it a bit cleared so that you may better understand - thanks for your help!

Highlighted

Okay, that cleared a lot!

 

For mail routing, the solution is same: set the domain groupb.ourdomain.com as Internal Relay. That changes the behavior so that if you send email to example@groupb.ourdomain.com, and mailbox is not found from Office 365, it is sent to where MX record points to (=Google).

 

If that is already setup, then the problem is that users have the mailbox in Office 365. So, either use Office 365 ProPlus license (which is cheaper than for instance E3), or use E3 but disable Exchange Online. That way users don't have mailboxes so their emails will be routed to Google.