Configuring SharePoint Cloud Hybrid Search – Engineerer
16
post-template-default,single,single-post,postid-16,single-format-standard,wp-custom-logo,bridge-core-3.1.2,qode-page-transition-enabled,ajax_fade,page_not_loaded,,footer_responsive_adv,hide_top_bar_on_mobile_header,qode-content-sidebar-responsive,qode-theme-ver-30.1,qode-theme-bridge,qode_header_in_grid,elementor-default,elementor-template-full-width,elementor-kit-641,elementor-page-1064

Configuring SharePoint Cloud Hybrid Search

This is the first part of a multi-part series about successfully configuring SharePoint Cloud Hybrid Search on a SharePoint 2016 onPremises farm. 

Those are the chapters we will cover in this series:

So what is this Cloud Hybrid Search exactly?

The Cloud Hybrid Search lets you crawl onPremises and Cloud content both together. This means you’ll have one unified search index in the cloud with all your content in it – regardless of its location. File share content can still be crawled onPremises and feeded to the cloud index. Your users will be able to search the cloud search center and find all content that matters to them. The search results are security trimmed and ranked.

Where to start?

Technet provides a neat roadmap, that shows all the steps necessary to successfully configuring the Cloud Hybrid Search. 

I configured Cloud Hybrid Search with the help of the mentioned roadmap. The roadmap helps a lot but doesn’t cover some aspects:

  • How do I keep my staging concept in place (TEST, INT, PROD)?
  • How do I enforce a naming concept for the Cloud Hybrid Search Service Application name and databases?
  • What are the network requirements to successfully configuring Cloud Hybrid Search?
  • What other configuration roadmaps should I follow prior configuring Cloud Hybrid Search?

Let’s get on it

Enough talking about why we want to have Cloud Hybrid Search. Let’s dig deeper!

In the next article, I will show which considerations you should take before installing the Cloud Hybrid Search.