Office 365 multi tenant architecture and deployment

%3CLINGO-SUB%20id%3D%22lingo-sub-16566%22%20slang%3D%22en-US%22%3EOffice%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16566%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20community%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eis%20it%20posible%20to%20connect%20two%20O365%20tenents%3F%20The%20reason%20is%3A%20I%20have%201%20company%20with%202%20different%20O365%20tenants.%20Each%20tenant%20represent%20a%20independent%20brunch.%20Merging%20of%20this%20tenants%20in%20one%20is%20not%20wished.%20See%26nbsp%3BAttachment%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet's%20say%20we%20have%20tenant%20A%20and%20tenant%20B.%20Tenant%20B%20is%20like%20the%20holding%20company%20and%20is%20the%20owner%20of%20the%20root%20mail%20domain%26nbsp%3B%40tenant-b.com.%20Users%20from%20tenant%20A%20need%20to%20be%20able%20to%20send%20and%20recieve%20messages%20over%20this%20tentant%20in%20their%20own%20tenant%20A%20mailbox.%20All%20the%20users%20from%20tenant%20A%20their%20default%20mailadress%20is%20from%20tenant%20B.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENext%20feature%3A%3C%2FP%3E%3CP%3ETenant%20B%20has%20a%20sharepoint%20site%20for%20the%20whole%20company.%20I%20will%20be%20used%20as%20intranet%20site.%20Users%20from%20tenant%20A%20would%20like%20to%20access%20the%20site%20to%20work%20together%20with%20their%20colleagues.%20The%20same%20in%20the%20other%20way.%20So%20if%20tenant%20A%20use%20a%20Sharepointsite%20they%20want%20to%20share%20it%20with%20tenant%20B.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBoth%20tenant%20are%20cloud%20only.%20And%20their%20are%20no%20plans%20to%20place%20an%20on%20premise%20Dirsync%20or%20etc.%20device.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-16566%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-20551%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-20551%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1604%22%20target%3D%22_blank%22%3E%40Muditha%20Chathuranga%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%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%3Bi%20have%20got%20an%20other%20idea.%20Is%20it%20possible%20to%20share%20one%20mail%20domain%20with%202%20O365%20tenants%20over%20an%20hybrid%20configuration%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20what%20i%20mean%20is%2C%20to%20use%20one%20exchnage%202016%20onpremise%20and%20connect%20them%20to%202%20seperated%20O365%20tenants.%20Than%20use%20the%20onpremise%20Exchange%20as%20mailrouter%20to%20share%20one%20mail%20domain%20in%202%20tenants.%20What%20do%20you%20think%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-17711%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-17711%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20the%20Sharepoint%20requirement%2C%20have%20you%20looked%20at%20using%20Azure%20AD%20B2B%3F%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fwww.techmikael.com%2F2016%2F04%2Fsetting-up-azure-business-to-business.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.techmikael.com%2F2016%2F04%2Fsetting-up-azure-business-to-business.html%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-Sonia%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16623%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16623%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Christoph%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20%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%3Bmentioned%2C%20it's%20not%20possible.%20A%20user%20in%20%3CSTRONG%3ETenant%20A%3C%2FSTRONG%3E%20who%20has%26nbsp%3Bsmtp%20addresses%20from%3CSTRONG%3E%26nbsp%3Btenant-a.com%3C%2FSTRONG%3E%20domain%20cannot%20have%20an%20smtp%20address%20from%20%3CSTRONG%3Etenant-b.com%3C%2FSTRONG%3E%20to%20send%20emails.%20Reason%20is%20%3CSTRONG%3Etenant-b.com%3C%2FSTRONG%3E%20is%20not%20added%20to%20%3CSTRONG%3ETenant%20A%20%3C%2FSTRONG%3Eand%26nbsp%3Bthe%20%3CSTRONG%3Etenant-b.com%20%3C%2FSTRONG%3Edomain%20is%20already%20added%20to%20%3CSTRONG%3ETenant%20B.%26nbsp%3B%3C%2FSTRONG%3ETherefore%26nbsp%3Byou%20cannot%20add%20that%20doamin%20to%20%3CSTRONG%3ETenant%20A%20%3C%2FSTRONG%3Eor%20vice%20versa.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20option%20I%20see%20here%20is%2C%20if%20the%20user%20count%20that%20requres%20this%20ability%20in%20%3CSTRONG%3ETenant%20A%3C%2FSTRONG%3E%20is%20less%2C%20create%20accounts%20for%20those%20users%20in%20%3CSTRONG%3ETenant%20B%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3CP%3EMuditha%20Chathuranga%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16612%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16612%22%20slang%3D%22en-US%22%3E%3CP%3ESending%20messages%20from%20Tenant%20B%20to%20Tenant%20A%20is%20easy.%20I%20create%20a%20contact%20in%20tenant%20b%20with%20a%20riderect%20to%20the%20onmicrosoft%20address%20of%20tenant%20a.%20You%20need%20to%20set%20the%20smtp%20alias%20from%20tenant%20b%20as%20default%20in%20this%20contect%20after%20creating.%20Now%20when%20i%20send%20a%20mail%20to%20user1%40tenant-b.com%20it%20will%20be%20redirectet%20to%20user1%40tenant-a.com.%20In%20the%20mail%20the%20recieptentadress%20is%20user1%40tenant-b.com.%20So%20incoming%20is%20working%20good.%20%26nbsp%3BKnow%20i%20need%20tell%20tenant-a%20that%20they%20can%20send%20in%20the%20name%20of%20tent-b.com.%20But%20i%20can't%20add%20an%20accepted%20domian%20to%20the%20exchange%20of%20tenant-a.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20i%20configure%20the%20exchnage%20on%20tenant%20a%20to%20connect%20to%20tenant%20b%20for%20sending%20mails%20in%20the%20name%20of%20tenant%20b%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16593%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16593%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20really%2C%20because%20tenant%20A%20don't%20have%20their%20own%20external%20mailadress.%20%26nbsp%3BOnly%20using%20the%20mailbox%20in%20tenant%20A%20but%20sening%20and%20recieving%20mails%20should%20go%20over%20tenant%20b.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20Idear%20was%20to%20place%20a%20Ad%20Server%20in%20Azure%20with%20AD%20Synch%20and%20connect%20both%20tenants%20to%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16590%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16590%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20need%20it%20as%20accepted%20domain%20in%20order%20to%20receive%20messages.%20As%20I%20mentioned%20there%20are%20several%20workarounds%20(use%20the%20default%20domain%2C%20use%20subdomain%2C%20use%20forwarding)%2C%20but%20it%20depends%20on%20the%20details.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20sure%20what%20a%20server%20in%20Azure%20will%20help%20you%20with%20the%20task%20at%20hand.%20Is%20the%20question%20perhaps%20about%20only%20a%20few%20people%20needing%20such%20functionality%2C%20so%20that%20you%20can%20for%20example%20configure%20both%20tenant-a%20and%20tenant-b%20profile%20in%20the%20same%20Outlook%20client%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16584%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16584%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20need%20to%20add%20the%20same%20domain%20to%20both%20tenants.%20Only%20sending%20and%20recieving%20mails%20over%20the%20same%20domain%20is%20my%20goal.%20At%20tenant%20A%20i%20can%20work%20maybe%20with%20a%20exchange%20sending%20connector.%20But%20what%20a%20bout%20tenant%20B%3F%20He%20need%20to%20redirect%20incomming%20mails%20for%20users%20in%20tenant%20A%20to%20Tenant%20A%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20maybe%20a%20better%20solution%20when%20i%20install%20one%20AD%20Server%20in%20Azure%20and%20connect%20both%20clients%20to%20them%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16581%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16581%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20problem%20here%20is%20that%20you%20cannot%20have%20the%20same%20domain%20added%20in%20more%20than%20one%20O365%20tenant.%20What%20you%20can%20do%20is%20use%20different%20domains%20or%20add%20subdomains%2C%20and%20use%20say%20blabla.tenant-a.com%20in%20tenant-b.com's%20organization.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOther%20than%20that%2C%20you%20can%20forward%20the%20messages%20based%20on%20the%20default%20tenant.onmicrosoft.com%20domain%20(for%20the%20receive%20part)%20and%20%22spoof%22%20the%20domain%20for%20the%20sending%20part.%20Which%20is%20far%20from%20ideal%20and%20will%20likely%20cause%20you%20troubles.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20the%20SPO%20part%20B2B%2Fexternal%20users%20should%20work%2C%20as%20Juan%20mentioned.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-16572%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-16572%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20best%20solution%20is%20to%20do%20the%20merge%20of%20the%20two%20tenants.%20By%20the%20way%2C%20my%20two%20cents%20here%3A%3CBR%20%2F%3E(1)%20I%20don't%20think%20you%20can%20achieve%20the%20e-mail%20integration%20you%20want%2C%20but%20I%20prefere%20some%20of%20the%20Exchange%20experts%20guys%20tell%20your%20options%20here%20(%26nbsp%3B%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%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E).%3C%2FP%3E%3CP%3E(2)%20You%20could%20potentially%20grant%20access%20to%20SPO%20to%20all%20the%20users%20on%20the%20other%20tenant%20using%20Azure%20B2B.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-501077%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20multi%20tenant%20architecture%20and%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-501077%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19496%22%20target%3D%22_blank%22%3E%40Christoph%20Wolf%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20interested%20on%20how%20you%20got%20on%20with%20this%20requirement%20given%20the%20latest%20innovations.%26nbsp%3B%20Indeed%20I%20believe%20there%20is%20concept%20of%20%22tenant%20friending%22%20but%20I%20am%20not%20sure%20how%20this%20working%20practice.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20too%20have%20the%20tenant%20A%20and%20tenant%20B%20.%26nbsp%3B%20%26nbsp%3BThe%20ideal%20is%20the%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3ETo%20publish%20news%20posts%20in%20tenant%20A%20and%20have%20this%20surface%20in%20tenant%20B%20(%20everyone%20in%20tenant%20A%2C%20everyone%20in%20tenant%20B)%20.%26nbsp%3B%20Then%20there%20is%20page%20%2F%20news%20templates%20and%20org%20level%20assets%20(%20would%20this%20needed%20to%20duplicated.%3C%2FLI%3E%3CLI%3ETo%20be%20able%20to%20publish%20and%20share%20SharePoint%20PowerApps%20and%20Flows%20across%20both%20tenants%3C%2FLI%3E%3CLI%3ETo%20roll%20identical%20or%20complimentary%20governance%20across%20both%20tenants%3C%2FLI%3E%3CLI%3EHandle%20search%2C%20term%20ids%2C%20content%20types%20etc%20in%20an%20elegant%20way%26nbsp%3B%20-%20hybrid%20v2%20%3Abeaming_face_with_smiling_eyes%3A%3C%2Fimg%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EAre%20there%20workarounds%20for%20any%20of%20this%20I%20wonder%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi community,

 

is it posible to connect two O365 tenents? The reason is: I have 1 company with 2 different O365 tenants. Each tenant represent a independent brunch. Merging of this tenants in one is not wished. See Attachment

 

Let's say we have tenant A and tenant B. Tenant B is like the holding company and is the owner of the root mail domain @tenant-b.com. Users from tenant A need to be able to send and recieve messages over this tentant in their own tenant A mailbox. All the users from tenant A their default mailadress is from tenant B. 

 

Next feature:

Tenant B has a sharepoint site for the whole company. I will be used as intranet site. Users from tenant A would like to access the site to work together with their colleagues. The same in the other way. So if tenant A use a Sharepointsite they want to share it with tenant B.

 

Both tenant are cloud only. And their are no plans to place an on premise Dirsync or etc. device.

10 Replies
Highlighted

I think best solution is to do the merge of the two tenants. By the way, my two cents here:
(1) I don't think you can achieve the e-mail integration you want, but I prefere some of the Exchange experts guys tell your options here ( @Vasil Michev @Tony Redmond).

(2) You could potentially grant access to SPO to all the users on the other tenant using Azure B2B.

Highlighted

The problem here is that you cannot have the same domain added in more than one O365 tenant. What you can do is use different domains or add subdomains, and use say blabla.tenant-a.com in tenant-b.com's organization.

 

Other than that, you can forward the messages based on the default tenant.onmicrosoft.com domain (for the receive part) and "spoof" the domain for the sending part. Which is far from ideal and will likely cause you troubles.

 

For the SPO part B2B/external users should work, as Juan mentioned.

Highlighted

I don't need to add the same domain to both tenants. Only sending and recieving mails over the same domain is my goal. At tenant A i can work maybe with a exchange sending connector. But what a bout tenant B? He need to redirect incomming mails for users in tenant A to Tenant A?

 

Is maybe a better solution when i install one AD Server in Azure and connect both clients to them?

Highlighted

You need it as accepted domain in order to receive messages. As I mentioned there are several workarounds (use the default domain, use subdomain, use forwarding), but it depends on the details.

 

Not sure what a server in Azure will help you with the task at hand. Is the question perhaps about only a few people needing such functionality, so that you can for example configure both tenant-a and tenant-b profile in the same Outlook client?

Highlighted

Not really, because tenant A don't have their own external mailadress.  Only using the mailbox in tenant A but sening and recieving mails should go over tenant b.

 

My Idear was to place a Ad Server in Azure with AD Synch and connect both tenants to them.

 

Highlighted

Sending messages from Tenant B to Tenant A is easy. I create a contact in tenant b with a riderect to the onmicrosoft address of tenant a. You need to set the smtp alias from tenant b as default in this contect after creating. Now when i send a mail to user1@tenant-b.com it will be redirectet to user1@tenant-a.com. In the mail the recieptentadress is user1@tenant-b.com. So incoming is working good.  Know i need tell tenant-a that they can send in the name of tent-b.com. But i can't add an accepted domian to the exchange of tenant-a.

 

How can i configure the exchnage on tenant a to connect to tenant b for sending mails in the name of tenant b? 

Highlighted

Hi Christoph

 

As @Vasil Michev mentioned, it's not possible. A user in Tenant A who has smtp addresses from tenant-a.com domain cannot have an smtp address from tenant-b.com to send emails. Reason is tenant-b.com is not added to Tenant A and the tenant-b.com domain is already added to Tenant B. Therefore you cannot add that doamin to Tenant A or vice versa.

 

Best option I see here is, if the user count that requres this ability in Tenant A is less, create accounts for those users in Tenant B.

 

Thank you.

Muditha Chathuranga

Highlighted

For the Sharepoint requirement, have you looked at using Azure AD B2B?

http://www.techmikael.com/2016/04/setting-up-azure-business-to-business.html

 

-Sonia

Highlighted

Hi

@Muditha Chathuranga and @Vasil Michev i have got an other idea. Is it possible to share one mail domain with 2 O365 tenants over an hybrid configuration?

 

So what i mean is, to use one exchnage 2016 onpremise and connect them to 2 seperated O365 tenants. Than use the onpremise Exchange as mailrouter to share one mail domain in 2 tenants. What do you think?

Highlighted

@Christoph Wolf @Juan Carlos González Martín 

 

I am interested on how you got on with this requirement given the latest innovations.  Indeed I believe there is concept of "tenant friending" but I am not sure how this working practice.  

 

I too have the tenant A and tenant B .   The ideal is the 

  • To publish news posts in tenant A and have this surface in tenant B ( everyone in tenant A, everyone in tenant B) .  Then there is page / news templates and org level assets ( would this needed to duplicated.
  • To be able to publish and share SharePoint PowerApps and Flows across both tenants
  • To roll identical or complimentary governance across both tenants
  • Handle search, term ids, content types etc in an elegant way  - hybrid v2 :beaming_face_with_smiling_eyes:

Are there workarounds for any of this I wonder ?