Roland Oldengarm - Independent IT Contractor

Living in the coolest little capital Wellington, New Zealand!

How to configure SharePoint 2016 or 2013 Hybrid Search

Hybrid is currently a big hype. Where a year ago the cloud was the way to go and on-premises advised against, companies have now realized the cloud is not suitable for every situation. Especially government organizations or big companies are not able to migrate everything to the cloud. So, Microsoft has invested a lot in hybrid to bring the best of two worlds together: the flexibility and data sovereignty of on-premises and all the cool new features of the cloud.

Part of this is Cloud Search: Make your on-premises documents available in cloud searches, i.e. your SharePoint On-Prem documents should be visible in a search in Office 365. Until September 2015 the hybrid search was meh, it meant two different result sources / verticals. Introduced in August 2015 is the real hybrid search: search results from both on prem as well as Office 365 are combined.

I have set this up and was surprised how easy it was. As a SharePoint guru I’m used to errors, but I haven’t encountered ONE (due to software faults, errors encountered were solely my fault). And that’s pretty amazing as I’ve used SharePoint 2016 which is currently in public preview.

The steps involved are:

  1. Install a SharePoint 2016 VM (SharePoint 2013 with the August 2015 CU or later installed should work as well). How? Look at my blog post How to Install SharePoint 2016 in 30 minutes.
  2. Configure an Office 365 tenant. I’ve set up a demo tenant via www.microsoftofficedemos.com
  3. Set up Azure Active Directory. You’ll need to sync your on-premises accounts to Azure Active Directory. This requires configuring a custom domain and then setting up AAD Sync.
  4. Install a Cloud Search Service Application on-premises. This is almost the same a normal Search Service Application, but then with some extra flags.
  5. Install some software and run on-boarding scripts. This last bit connects your SharePoint On-Premises instance with Office 365

How to install SharePoint 2016

Check out my blog post. Done in half an hour.

Configure an Office 365 Tenant

You will need to either subscribe to Office 365, use an existing tenant, or subscribe to Microsoftofficedemos.com. I’ve done the latter.

Set up Azure Active Directory

You will need to connect your Office 365 subscription to a valid Azure subscription. There is a link in Office 365 Administration which goes to Azure. However, if you want to connect it to an existing Azure subscription, this won’t work. In my case I already had an Azure subscription. If so, you’ll need to log into Azure instead, go to Active Directories, add a new Active Directory, and select “Existing Active Directory”.

Then you can use your existing Azure subscription with a new Office 365 tenant.

Install Cloud SSA, install software, and run on-boarding scripts.

I am not going to reiterate how to do step 4 and 5 as this is outlined perfectly in this extensive blog post.

And it works! How amazing.

People in general have a love-hate relationship with SharePoint. It offers a lot of functionality, there is a high demand for skilled SharePoint people, but the random errors with sometimes no description are annoying. But in this case I only encountered errors when creating the SSA, and that was because I entered wrong values for the database server.

The end result is pretty cool. I’ve ran a search on my demo tenant, and it shows a result from my on-premises SharePoint 2016 environment.

x4W14gF

This is really something you should think about when implementing SharePoint. By leveraging hybrid search, you are able to use Delve for your on-premises documents for example. And it is also possible to crawl SharePoint 2010 documents from you Cloud SSA, making SP2010 documents available in Office 365! How cool is that.

With Cloud Hybrid SharePoint Search you can push your on-premises SharePoint (2010, 2013, 2016) documents to Delve!

3 Comments

  1. Morning Roland,
    I’m not a SharePoint guru, novice…. I’m an AD and Exchange guy. We’re currently in Hybrid, I’m migrating mailboxes to O365 – in batches!!!
    My client just launched their Intranet site on SPO, they are not migrating or moving on-premise SharePoint to SPO. I’ve asked the PM how they’re doing the people search and she said it’s pointed to Delve. I can’t check, no permission. So, the problem is, when you try and find an Employee, you either get some info or you get no results as all. How to rectify this? or point it to the right repository?

    Thanks

    • rolandoldengarm

      February 26, 2016 at 5:06 pm

      Hi Derrick, thanks for your comment.

      Search results in SharePoint are security trimmed, you only see results you’re allowed to open. For documents / pages that is obvious, as that is driven by the permission settings of the sites. For people search it’s a bit different. It should be that everyone in the organisation is able to use the people search and find all people in their organisation.
      Are you saying that some people get all results, but some people get none? What’s the difference between people where it works, and people where it doesn’t? With what account are they logged into Office 365?
      Happy to help.

  2. Edgardo Raring

    March 13, 2016 at 5:10 am

    Remember that at the moment this is just a Preview of SharePoint 2016 open for anyone to test and provide feedback. Microsoft is very open and has been trying hard to implement exactly what their customers ask for in SharePoint.

Leave a Reply

Your email address will not be published.

*