Having domain email addresses outside of Office 365

%3CLINGO-SUB%20id%3D%22lingo-sub-1028768%22%20slang%3D%22en-US%22%3EHaving%20domain%20email%20addresses%20outside%20of%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1028768%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20a%20very%20small%20company%20has%20Office%20365%20Business%20Essentials%20in-place%20for%20few%20key%20people%2C%20and%20they%20want%20to%20have%20additional%20users%20using%20the%20same%20domain.com%20email%20without%20an%20O365%20subscription%20(and%20maybe%20use%20the%20original%20web%20host%20non-exchange%20pop%2Fimap%20email%3F)%2C%20what%20would%20be%20the%20setup%20process%3F%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20I've%20read%20seems%20to%20be%20for%20a%20pilot%2C%20and%20have%20users%20forward%20email%20from%20the%20original%20web%20host%20email%20account%20to%20a%20new%20O365%20email%20address.%3C%2FP%3E%3CP%3ECan%20anyone%20suggest%20a%20document%20that%20may%20provide%20specific%20setup%20details%20for%20this%3F%26nbsp%3B%20Assuming%20it%20can%20be%20accomplished.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1028768%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-1029466%22%20slang%3D%22en-US%22%3ERe%3A%20Having%20domain%20email%20addresses%20outside%20of%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1029466%22%20slang%3D%22en-US%22%3EIf%20you%20mean%20e-mail%20address%20from%20the%20Office%20365%20domain%20without%20a%20license%2C%20your%20only%20option%20really%20is%20a%20Shared%20Mailbox%20(Via%20exchange%20admin)%20and%20then%20you%20can%20set%20the%20forwarding%20on%20that%20mailbox%20to%20the%20other%20domain.%20%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20used%20to%20be%20able%20to%20use%20a%20contact%20to%20do%20the%20forwarding%20but%20I%20don't%20think%20you%20can%20do%20that%20without%20a%20hybrid%20configuration.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1029726%22%20slang%3D%22en-US%22%3ERe%3A%20Having%20domain%20email%20addresses%20outside%20of%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1029726%22%20slang%3D%22en-US%22%3E%3CP%3EHello%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F345303%22%20target%3D%22_blank%22%3E%40Stewart9%3C%2FA%3E%26nbsp%3B!%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20I%20understand%20you%20correctly%20your%20current%20setup%20is%20the%20following%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E1%20IMAP%20mail%20system%20in%20place%20(%20the%20Active%20system%20)%26nbsp%3B%3C%2FLI%3E%3CLI%3E1%20Office365%20tenant%20with%20Exchnage%20Online%20that%20is%20being%20piloted%26nbsp%3B%3C%2FLI%3E%3CLI%3E1%20Custom%20domain%26nbsp%3B%3C%2FLI%3E%3C%2FUL%3E%3CP%3EAnd%20you%20want%20to%20enable%20both%20the%20Office365%20tenant%20and%20your%20current%20Email%20(%20IMAP%20)%20system%20to%20receive%20and%20send%20emails%3F%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20not%20possible%20on%20a%20DNS%20level%20to%20set%20up%20two%20separate%20MX%20records%20for%20the%20same%20domain.%20Meaning%2C%20you%20cant%20set%20up%20two%20separate%20email%20systems%20for%20the%20same%20domain%2C%20this%20will%20cause%20DNS%20errors%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20are%20only%20piloting%20Office365%20at%20the%20moment%2C%20then%20I%20suggest%20that%20you%20do%20the%20following%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3ESet%20up%20email%20contacts%20in%20your%20current%20IMAP%20system%20that%20points%20to%20the%20Office365%20default%20email%20address%20of%20the%20users%3C%2FLI%3E%3C%2FOL%3E%3CP%3EWith%20the%20above%2C%20you%20will%20keep%20your%20MX%20records%20pointed%20to%20your%20current%20IMAP%20system%2C%20meaning%20all%20emails%20will%20go%20there.%20And%20then%20you%20have%20forwarding%20set%20up%20for%20your%20pilot%20users%20that%20sends%20incomming%20emails%20to%20the%20default%20office365%20domain%20(%20company.onmicorosft.com%20)%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20%2Cwhen%20you%20are%20ready%2C%20I%20suggest%20that%20you%20migrate%20the%20data%20from%20the%20current%20IMAP%20system%20to%20Office365%2C%20and%20then%20redirect%20the%20DNS%20MX%20record%20to%20Office365%20instead%20and%20decommision%20the%20current%20IMAP%20system%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20youre%20a%20small%20organization%20with%20not%20many%20users%20or%20email%20integrated%20services%2C%20this%20should%20be%20a%20pretty%20straight%20forward%20process%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet%20me%20know%20if%20you%20need%20further%20assistance%2C%20i'd%20be%20more%20than%20happy%20to.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EKind%20RegardsOliwer%20Sj%C3%B6berg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1031724%22%20slang%3D%22en-US%22%3ERe%3A%20Having%20domain%20email%20addresses%20outside%20of%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1031724%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20really%20boils%20down%20to%20what%20features%20they%20will%20need%20access%20to.%20You%20can%20have%20as%20many%20unlicensed%20users%20as%20you%20want%2C%20and%20you%20can%20even%20get%20them%20access%20to%20some%20services%20without%20assigning%20a%20license.%20However%20if%20they%20want%20to%20send%20messages%20using%20O365%2C%20they%20will%20need%20a%20license.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1032586%22%20slang%3D%22en-US%22%3ERe%3A%20Having%20domain%20email%20addresses%20outside%20of%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1032586%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20clarify%20a%20bit%2C%20My%20small%20company%20has%20two%20users%20now%20on%20O365%20BE%2C%20with%20our%20domain%20setup%20in%20O365.%20So%20I'm%20not%20piloting.%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20I%20work%20with%20a%20few%20other%20small%20companies%20wanting%20to%20do%20this%20also%20if%20possible%2C%20so%20I'm%20the%20test-case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENone%20of%20the%20O365%20account%20features%20would%20be%20needed%20for%20the%20emails%20not%20using%20O365.%26nbsp%3B%20They%20would%20use%20their%20existing%20email%20clients%20(Outlook%2C%20Win%2010%20Mail%2C%20etc.)%20to%20access%20their%20IMAP%20accounts.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20previously%20tested%20Forwarding%20from%20our%20email%20accounts%20(at%20our%20web%20hosting%20company)%20to%20both%20O365%20account%20and%20an%20Outlook.com%20account.%26nbsp%3B%20With%20Forwarding%20setup%20for%20two%20different%20email%20accounts%2C%20a%20high%20percentage%20of%20the%20emails%20forwarded%20did%20not%20show%20up%20in%20the%20O365%20inbox.%26nbsp%3B%20I'd%20be%20afraid%20tell%20a%20customer%20he%20can%20depend%20on%20all%20of%20his%20mail%20being%20delivered%20to%20the%20O365%20account%2C%20and%20by%20the%20way%2C%20they%20would%20have%20to%20keep%20the%20mail%20server%20emptied%20manually%2C%20and%20separately.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20thought%20it%20may%20be%20possible.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

If a very small company has Office 365 Business Essentials in-place for few key people, and they want to have additional users using the same domain.com email without an O365 subscription (and maybe use the original web host non-exchange pop/imap email?), what would be the setup process?

What I've read seems to be for a pilot, and have users forward email from the original web host email account to a new O365 email address.

Can anyone suggest a document that may provide specific setup details for this?  Assuming it can be accomplished. 

 

4 Replies
Highlighted
If you mean e-mail address from the Office 365 domain without a license, your only option really is a Shared Mailbox (Via exchange admin) and then you can set the forwarding on that mailbox to the other domain.

You used to be able to use a contact to do the forwarding but I don't think you can do that without a hybrid configuration.
Highlighted

Hello@Stewart9 ! 

If I understand you correctly your current setup is the following 

  • 1 IMAP mail system in place ( the Active system ) 
  • 1 Office365 tenant with Exchnage Online that is being piloted 
  • 1 Custom domain 

And you want to enable both the Office365 tenant and your current Email ( IMAP ) system to receive and send emails? 

It is not possible on a DNS level to set up two separate MX records for the same domain. Meaning, you cant set up two separate email systems for the same domain, this will cause DNS errors 

 

If you are only piloting Office365 at the moment, then I suggest that you do the following

 

  1. Set up email contacts in your current IMAP system that points to the Office365 default email address of the users

With the above, you will keep your MX records pointed to your current IMAP system, meaning all emails will go there. And then you have forwarding set up for your pilot users that sends incomming emails to the default office365 domain ( company.onmicorosft.com ) 

 

Then ,when you are ready, I suggest that you migrate the data from the current IMAP system to Office365, and then redirect the DNS MX record to Office365 instead and decommision the current IMAP system 

 

If youre a small organization with not many users or email integrated services, this should be a pretty straight forward process 

 

Let me know if you need further assistance, i'd be more than happy to. 

Kind Regards
Oliwer Sjöberg

Highlighted

It really boils down to what features they will need access to. You can have as many unlicensed users as you want, and you can even get them access to some services without assigning a license. However if they want to send messages using O365, they will need a license.

Highlighted

@Vasil Michev 

To clarify a bit, My small company has two users now on O365 BE, with our domain setup in O365. So I'm not piloting. 

And I work with a few other small companies wanting to do this also if possible, so I'm the test-case.

 

None of the O365 account features would be needed for the emails not using O365.  They would use their existing email clients (Outlook, Win 10 Mail, etc.) to access their IMAP accounts.  

 

I had previously tested Forwarding from our email accounts (at our web hosting company) to both O365 account and an Outlook.com account.  With Forwarding setup for two different email accounts, a high percentage of the emails forwarded did not show up in the O365 inbox.  I'd be afraid tell a customer he can depend on all of his mail being delivered to the O365 account, and by the way, they would have to keep the mail server emptied manually, and separately.

 

I just thought it may be possible.