1. Hybrid OneDrive for Business.
2. Hybrid Sites Features.
3. Hybrid App Launcher.
4. Hybrid Extranet Business-to-Business sites.
5. Hybrid Auditing (Works only in SharePoint 2016).
6. Hybrid Taxonomy and Content Types.
7. Hybrid self-service site creation. (Hybrid self-service site creation is available in SharePoint Server 2013 with the March 2017 PU. November 2017 CU adds this to 2016)
8. Hybrid Search [Query federation]
9. Cloud Hybrid search(CloudSSA).
10. Business connectivity services

• Support client certificate authentication with a wildcard or SAN certificate.
• Support pass-through authentication for OAuth 2.0.
• Accept unsolicited inbound traffic on TCP port 443 (HTTPS).
• Bind a wildcard or SAN SSL certificate to a published endpoint.
• Relay traffic to an on-premises SharePoint Server 2013 or 2016 farm or load balancer without rewriting any packet headers.

• Your users get unified search results, search relevance ranking, and refiners even if your organization has a hybrid deployment with content both on-premises and in Office 365.
• Your users automatically get the newest SharePoint Online search experience without your organization having to update your existing SharePoint servers.
• Your users can use cloud capabilities such as Office Delve also for your on-premises content.
• You no longer have to worry about the size of your search index, because your search index is in Office 365. This means that the footprint of your SharePoint Server 2013/2016 search farm is smaller, and your total cost of ownership for search is lower.
• You don't need to upgrade any of your existing installations of SharePoint to have enterprise search in the cloud because SharePoint Server 2013/2016 supports crawling of existing SharePoint Server 2007, SharePoint Server 2010 and SharePoint Server 2013 content farms.
• You no longer have to migrate your search farm to a newer version of SharePoint because this happens automatically in Office 365.

1. Sign up for Office 365.
2. Register your domain with Office 365.
3. Synchronize accounts with Office 365.
4. Assign licenses to your users.
5. Create cloud hybrid search service application.
6. Onboard cloud hybrid search service application.

• You have a SharePoint 2013 or SharePoint 2016 farm where you plan to implement provider hosted add-ins and/or associate with workflow manager.
• You have a SharePoint 2013 or SharePoint 2016 farm that already has provider hosted add-ins and/or leverages workflow manager.

• Make O365 User Profile service the primary source of user information and let office 365 search take care of the indexing and presentation. With this approach, you do not need to crawl people on premises.
• Crawl the on premises people profile store in addition to O365 crawling the tenant profile store. This will result in the described scenario of duplicate search results for each person, however you can use query transformation to decide which results you want to display. Even providing the ability for end users to choose between the different result sources at query time.

1. Create a new result source or copy the existing people results source
2. Edit the new result source and modify the Query Transformation box to include the Managed Property IsExternalContent as below. {?{searchTerms} ContentClass=urn:content-class:SPSPeople IsExternalcontent:1}
3. Then you can create a new search results page and configure the Core Search Results web part to consume this new search result source.
4. Complete the implementation by adding the new page to the search navigation settings. This will add the new page as a search vertical within the search center, as per the screenshot below.

1. Insert: Creates or overwrites a document’s content and access control list.
2. Security update: Overwrites an existing document’s access control list.
3. Delete: Deletes all content for a document.

1. *.sharepoint.com
2. https://accounts.accesscontrol.windows.net
3. https://login.windows.net/common/oauth2/authorize
4. https://sts.windows.net/*
5. https://login.microsoftonline.com

1. https://provisioningapi.microsoftonline.com
2. *.search.production.us.trafficmanager.net
3. *.search.production.emea.trafficmanager.net
4. *.search.production.apac.trafficmanager.net

2. You also need to ensure that account running the search service (msssearch, noderunner accounts) (for crawl and Query federation scenarios to work) in the Cloud Search Service Application farm have unrestricted outbound internet access. If not, set system level proxy settings for these accounts with netsh. Below are the steps.
3. Make a note of the accounts (account running the search service) either from windows services or taskmanager.
4. Log in to a server in the farm (preferably crawl server) in the Cloud Search Service Application farm. Run the below commands

1. If you cannot log in to the server with the account running search service, you can launch an admin command prompt and manually update the proxy settings. If the command prompt fails to launch with the search service account and correct credentials ensure that the account has log in locally rights on the server.  Below are the steps.
2. Launch a command prompt with the account running the search service account.
3. At the command prompt, type netsh winhttp set proxy proxyservername:portnumber.

1. Browse to a Document library within a SharePoint site and create a column from within the document library settings. Choose single line text as the column type. Name the column as
2. Upload a document of different language and add a value to MyDocLibID column example ID#161516.
3. Browse to SharePoint admin center with a Global administrator or a SharePoint administrator account.
4. Click on Search from the left navigation.
5. Within Search Administration, click on Manage Search Schema.
6. Click on Crawled Properties.
7. Search automatically creates crawled properties for the columns that has been created. Example if you have created a column in your document library called MyDocLibID, you can search for the same in the list of Crawled Properties. It should return the property name as ows_MyDocLIbID. At this stage the property is not mapped to any managed property.
8. 
9. Next you need to create a managed property and map the crawl property. Click on Managed Properties and click New Managed Property.
10. In this example, our focus will be only in the two new properties, as rest of property functionality remains the same as of today. Type in a name of the managed property example “MyDocLibID”.
11.          
12. I have made the property Queryable, Retrievable, Safe (as I want to test anonymous user query functionality), Token Normalization.The key properties for this functionality to work is Language Neutral Tokenization, & Finer Query Tokenization. Select the check boxes next to these properties.
13.  
14. Map the managed property to crawl property that was created for the document library, in this case ows_MyDocLIbID. Within Mappings to crawled properties section click on Add a Mapping.

1. Browse to your site with a site collection administrator.
2. Click Settings, and then click Site settings.
3. Under Site Collection Administration, click Search Schema.
4. 
5. In the Property Name column on the Managed Properties tab, in the Filter box type the Name of the Managed Property
6.  Optionally you can create a new one by clicking on the New Managed Property tab.
7. 
8. New Managed property creation steps at site collection level are identical to the ones we discussed above for tenant level. Follow the steps below if you are editing an existing custom managed property. From search results in step 4 above click on the managed property, and select Edit/Map property.
9. Scroll down to the new settings on the Edit Managed Property page, check the two new managed properties (Language Neutral Tokenization, Finer Query Tokenization) to turn on the new capabilities and then click OK.
10. 
11. Now if you look up documents associated with this manage property, you will be able to leverage the enhanced Wordbreaking features mentioned above.

 

To configure hybrid self-service site creation

1. Log on to a server in your SharePoint Server farm as the farm administrator.
2. From your SharePoint Server computer, open a web browser and log on to Office 365 as a global administrator.
3. In the SharePoint Online Admin Center, click configure hybrid.
4. On the hybrid picker page, click Hybrid Picker.
5. Follow the wizard and choose Hybrid self-service site creation when prompted, noting that additional information is required before the feature can be deployed.
6. When prompted, choose the web application with which you want to use hybrid self-service site creation.
7. When the web application has been provided, the feature selection show as the screen shot below
8. When the hybrid picker wizard completes, hybrid self-service site creation will be enabled for the web application that you selected.

Manage hybrid self-service site creation in Central Administration

1. In Central Administration, click Application Management.
2. On the Application Management page, under Site Collections, click Configure self-service site creation.
3. In the Web Application section, select the web application where you want to manage hybrid self-service site creation, and then select or clear the Create Site Collections in SharePoint Online check box.
4. Click OK

Manage hybrid self-service site creation with PowerShell

1. Get the Web Application Object $webapp = Get-SPWebApplication http://<web application url> 
2. To Check the current setting of SelfServiceSiteCreationOnlineEnabled property $webapp.SelfServiceSiteCreationOnlineEnabled returns True or False
3. To enable the feature, update the property to True and Validate $webapp.SelfServiceSiteCreationOnlineEnabled = $true $webapp.update() $webapp.SelfServiceSiteCreationOnlineEnabled Will return True 
4. To disable the feature update the property to False and Validate $webapp.SelfServiceSiteCreationOnlineEnabled = $false $webapp.update() $webapp.SelfServiceSiteCreationOnlineEnabled Will return False

Validating Hybrid Self Service Site Creation

1. Login to the on premises web application configured for hybrid self service sites above as a hybrid enabled user. This means a user synchronized to Office 365 and enabled for hybrid workloads via an audience as explained above.
2. Navigate to the url in the Self Service Site Collection Management page, the image above shows https://<On Premises Site url>/_layouts/scsignup.aspx
3. A hybrid enabled user will be redirected to O365 Groups Creation page. You may be asked to authenticate and then the following screen is displayed
4. Enter the required settings and then click Next. Also note the TeamSite name and email address are checked for uniqueness
5. Add additional Owners and members if required which the group and site are being created. Click finish when the button is activated
6. You will be redirected to the new Site Collection in the O365 tenant

1. Browse to enterprise search people results page example https://contoso.sharepoint.com/search/Pages/peopleresults.aspx
2. Edit Search Results page.
3. Edit People Results Web part.
4. Change query.
5. Change Query Text from {searchboxquery} to {searchboxquery} –“SPS-HideFromAddressLists”:1
6. Apply changes.
7. Check-in changes and publish the page.

1. You have a SharePoint 2013 or SharePoint 2016 farm where you plan to implement provider hosted add-ins and/or associate with workflow manager.
2. You have a SharePoint 2013 or SharePoint 2016 farm that already has provider hosted add-ins and/or leverages workflow manager.

The Workflow Manager TrustedSecurityTokenIssuer uses a wildcard realm (e.g. “<guid>@*”) instead of a specific realm identifier. This means workflows will keep working even  after changing the SPAuthenticationRealm.

• Tenant: https://contoso.sharepoint.com

•  https://accounts.accesscontrol.windows.net

• *.search.production.us.trafficmanager.net
• *.search.production.emea.trafficmanager.net
• *.search.production.apac.trafficmanager.net

This script and blog article are for use in configuring an outbound search hybrid experience between SharePoint 2013 Server and SharePoint Online. In preliminary testing this also works with SharePoint 2016.

Pre Requisites for completing the configuration process 

• You need to log in to SharePoint Server with an account that has farm administrator and a local server admin privilege.
• The account should also be a local administrator across all SharePoint boxes in the farm.
• The script assumes that the Root Site Collection of the SharePoint Web Application either is a search center or has a search center web within it e.g. http://sharepoint.contoso.com/search . If this is not the case, then additional configuration of result sources and query rule will be required to retrieve search results from SharePoint online.

Executing the Configuration Wizard 

1. Extract hybridwizard.ps1 and the resources files from the downloaded zip archive to a folder named c:\scripts. This is a requirement for this version, however in a future release we will include a direct download capability for updated components.
2.  You can execute the script from the ISE or from the PowerShell command console
3.  Open Elevated PowerShell Session or elevated ISE session and execute hybridwizard.ps1.

Service Application Validation 

Installation Progress Status

Authenticate to Azure AD

Self-Signed Certificate Generation

Hybrid Wizard Completion Confirmation

Hybrid Validation