Forum Discussion
Enable Hybrid SharePoint for multiple farms in same domain
Hi
I'm currently working for a customer who is planning to go Hybrid. They're currently on SharePoint 2013 and on a patch level that supports everything except Hybrid App Launcher and Hybrid Taxonomy. They are already using Office 365, have setup DirSync, ADFS and are using Yammer, OneDrive, Exchange and Skype.
The customer has 3 on-premises SharePoint environments; test, uat and prod. All environments are in the same domain. How can I test hybrid SharePoint end-to-end without setting up new domains, sync servers, online tenants and federation servers? Is it even possible?
I understand consequences like having test and uat data in the prod index and sites I follow in test being visible in SharePoint Home.
Is it anything in the online tenant that says which farm is connected? After investigating the hybrid on-boarding scripts for hybrid search, I can only see changes to the farm configuration, except the registration of Service Principals (for Microsoft.SharePoint and Search Content Service)) and associated Service Principal Credentials using current farm's certificate.
To me it seems you can add multiple certificate keys to the service principal (SharePoint Online).
According to Matthew McDermott you can onboard multiple on-prem farms to the same tenant - http://sharepoint.stackexchange.com/questions/188361/sharepoint-2016-hybrid-search-with-multiple-environments/188436 so then I guess so. I didn't think this was the case, but kinda cool I guess :)
3 Replies
According to Matthew McDermott you can onboard multiple on-prem farms to the same tenant - http://sharepoint.stackexchange.com/questions/188361/sharepoint-2016-hybrid-search-with-multiple-environments/188436 so then I guess so. I didn't think this was the case, but kinda cool I guess :)
- Thanks Mikael Svenson. I'm also curious about how it will work with the other hybrid workloads. I guess the taxonomy sync will bring difficult in my scenario.
Seems the sensible setup is to connect a shared services farm (if multiple in prod), and then have a 1:1 with a tenant. For dev/test having separate AD and tentants will probably make the world easier. Would be nice with proper guidance so you could defend why you don't want multiple onprem against one tenant...if that indeed can cause issues :)
