Hybrid SharePoint - Multiple Environments

%3CLINGO-SUB%20id%3D%22lingo-sub-2736845%22%20slang%3D%22en-US%22%3EHybrid%20SharePoint%20-%20Multiple%20Environments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2736845%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20currently%20working%20in%20an%20environment%20implementing%20a%20Hybrid%20SharePoint%20deployment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn-premise%20we%20have%203%20environments%20in%202%20AD%20domains.%26nbsp%3B%3C%2FP%3E%3CP%3EProd%20SharePoint%20-%20(Prod%20Domain)%3C%2FP%3E%3CP%3EPre-Prod%20-%26nbsp%3B(Prod%20Domain)%3C%2FP%3E%3CP%3EDevelopment%20-%20Development%20Domain%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20the%20issue%20comes%20in%20the%20SharePoint%20online%20tenancy%20setup%20-%20Prod%20is%20talking%20to%20our%20Production%20tenancy%20and%20Dev%20talks%20to%20a%20separate%20tenancy%20because%20its%20in%20a%20separate%20AD%20domain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20tenancy%20we%20could%20link%20Pre-Prod%20to%20is%20our%20Production%20Online%20Tenant%20but%20we%20would%20need%20to%20do%20some%20form%20of%20data%20segregation%20to%20ensure%20prod%20users%20can%20only%20see%20prod%20data%20and%20pre-prod%20users%20could%20only%20see%20pre-prod%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20do%20other%20people%20do%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20other%20option%20is%20to%20accept%20the%20risk%20we%20can't%20test%20hybrid%20functionality%20in%20Pre-Prod%20which%20isn't%20ideal.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2736845%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EEnvironment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%202019%20On-Prem%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi,

 

I am currently working in an environment implementing a Hybrid SharePoint deployment.

 

On-premise we have 3 environments in 2 AD domains. 

Prod SharePoint - (Prod Domain)

Pre-Prod - (Prod Domain)

Development - Development Domain

 

Now the issue comes in the SharePoint online tenancy setup - Prod is talking to our Production tenancy and Dev talks to a separate tenancy because its in a separate AD domain.

 

The only tenancy we could link Pre-Prod to is our Production Online Tenant but we would need to do some form of data segregation to ensure prod users can only see prod data and pre-prod users could only see pre-prod data.

 

How do other people do this?

 

The only other option is to accept the risk we can't test hybrid functionality in Pre-Prod which isn't ideal. 

 

0 Replies