Hybrid Search with SharePoint 2013 and Office 365 Brendan Griffin

Me.About() Senior Premier Field Microsoft Microsoft Certified Master: SharePoint years experience with SharePoint

Agenda What is Hybrid Search? Identity Considerations Deployment Stages Hybrid Search in Action

What is Hybrid Search? Imagine a Scenario… Your company are using SharePoint On-Premises and Office 365 User content is currently stored in both Does this mean that your users have to search both to find content???

What is Hybrid Search? Certainly Not! Hybrid Search provides the ability for Office 365 content to be surfaced in Search results within an On-Premises farm and vice versa End users can perform a single Search query to find content! 3 options are available for configuring Hybrid search

What is Hybrid Search? Option 1 – One-Way Outbound

What is Hybrid Search? Option 2 – One-Way Inbound

What is Hybrid Search? Option 3 – Two-Way Bi-Directional

What is Hybrid Search? This session will focus on the One-Way Outbound topology Easiest of the three options to configure Start with the One-Way Outbound topology first before embarking on more complex Hybrid topologies

Identity Considerations There are three different identity scenarios for Office 365 Hybrid requires the ability to map an On-Premise user to a Cloud Identity – Cloud Identity (only) isn’t an option for Hybrid

Identity Considerations In this session we will use Directory & Password Synchronization Users from the On-Premise AD will be sync’d to Office 365 (Azure AD) – includes a hash of their password Enables users to logon to SharePoint On-Premises and Office 365 using the same username and password – this isn’t SSO though!

Additional Considerations SharePoint On-Premises requires the following Service Applications for Hybrid Search to function o App Management Service o Subscription Settings Service o User Profile Service o Search User Profile Service required to rehydrate users for Security Trimming

Deployment Stages Four Stages to Configure One-Way Outbound Hybrid Search 1.Infrastructure Pre-Requisites 2.Setting up DirSync 3.Establish S2S Trust with Azure ACS 4.Configure SharePoint On-Premises Search

Deployment Steps Infrastructure Pre-Requisites 1.Verify the internal AD domain name with Office 365 – Needs to be a routable domain 2.Perform any required AD remediation – IdFix can helpIdFix 3.Activate Active Directory Synchronisation in Office 365

Demo 1: Infrastructure Pre-Requisites

Deployment Steps Setting up DirSync (AAD Sync) 1.Install and configure the DirSync tool – 2.Assign user licenses in Office 365

Demo 2: Setting up DirSync

Deployment Steps Unhealthy Directory Synchronisation

Deployment Steps Assigning Licenses using the Office 365 Portal

Deployment Steps Assigning Licenses using PowerShell Licenses all users with a Username (UPN) of *.brendg.co.uk Also sets their location to GB

Deployment Steps DirSync Schedule By default DirSync will sync AD users with Office 365 every 3 hours, this can be changed in the Scheduler.exe.Config* file Alternatively a sync can be manually started using PowerShell – automate using a Scheduled Task

Deployment Steps Establish S2S Trust with Azure ACS 1.Replace the STS Certificate within the On-Premises SharePoint farm 2.Register the On-Premises STS as a Service Principal in Office Establish a trust between the On-Premises farm and Azure ACS

Demo 3: Establish S2S Trust with Azure ACS

Deployment Steps Configure SharePoint On-Premises Search 1.Add a Result Source for SharePoint Online 2.Create a Query Rule to display results from SharePoint Online 3.Test!!!

Demo 4: Configure SharePoint On-Premises Search

Demo 5: Alternative Option for Display Search Results

It doesn’t work??? Make sure that the user has a profile in Office 365!

Questions