Every time you see a blog post about SharePoint 2016, you see the word hybrid. But what exactly is a hybrid infrastructure and what features does the business user get?
In this session we will look at SharePoint Hybrid from a business user point of view to understand what features we get out of it. We will look at Hybrid Team Sites, Hybrid Search, Hybrid Extranet sites and more!
4. There are many variations of passages of lorem
ipsum available, but the majority have suffered
alteration
in some form, by injected humour
THE KEY IS ALWAYS YOU!
PLURALSIGHT AUTHOR
Creating video content for one of the most
popular and best quality online training
sites.
SHAREPOINT EXPERT
Independent SharePoint Consultant,
SharePoint MVP and Top 25 SharePoint
Influencer Worldwide.
About Vlad Catrinescu
@vladcatrinescu
absolute-sharepoint.com
AUTHOR
Author of the book “Deploying SharePoint
2016” for Apress
AMBASSADOR
Partner with KWizCom and Datapolis
5. Agenda
What is
Hybrid?
Why
Hybrid?
Hybrid
Extranet Sites
Hybrid Sites &
Profiles
Partners
App
Launcher
OneDrive for
Business
Business
Connectivity
Services
Hybrid Search
Introduction
Federated
Search
Options
Hybrid Cloud
Search
Conclusion
Result
Blocks
1TB +
LOB Data
Online!
Delve
14. SharePoint in DMZ?
Licensing for External Users?
Forms Based, ADFS, Federation, AD?
Risk of opening SharePoint over the web?
On-going maintenance of external user accounts
Extranet Sites
On-Premises
SharePoint Farm
External Users
Internal Users
16. SharePoint Online is open to the web by default
Easy to create new Site Collections for new
partners
Secure Sharing using Microsoft Accounts
Auditing enabled
Globomantics On-
Premises
Globomantics Office
365 Tenant
Hybrid
Extranet Sites
18. Site following
- Followed sites from both SharePoint on-
premises and SharePoint Online are
consolidated
Profile redirection
- Users are redirected to Office 365 profiles
Extensible app launcher (SP 2016 only)
- Show Office 365 Delve, video and
custom Office 365 tiles in SharePoint
2016 app launcher
Hybrid
Sites
23. Office 365 instead of My Sites
Same client
Between 1TB and unlimited in Office 365
Accessible from anywhere in the world
Backups and growth handled by MS
Advantages
24. Architecture Overview
Starting from SharePoint
2013/2016 on-premises
Starting from
Office 365
1. User logs in Office 365
2. User clicks in OneDrive
in the app launcher
3. User goes to OneDrive in Office 365
1. Users logs SharePoint On-
premises
2. User clicks in OneDrive
in the navigation bar (2013) or app
launcher (2016)
3. User goes to OneDrive in on-
premises MySites
Hybrid Audience
26. On-Premises Business Data Connectivity
Services connects SharePoint to External
Systems
Hybrid BCS Allows you to publish data from On-
Premises systems in SharePoint Online
Communication is encrypted
27. Make Clients / Sales Data available to People on
the road, without VPN!
Allow SharePoint Online Add-ins to consume On-
Prem LoB Data
34. One-way Outbound Topology
Outbound
SharePoint Server
Can Query
SharePoint Online
SharePoint Online
Cannot Query
SharePoint Server
SharePoint Server and SharePoint Online
Search Results
SharePoint Server Search
Center
SharePoint Online Search
Center
SharePoint Online
Search Results
35. One-way Inbound Topology
Inbound
SharePoint Server
Cannot Query
SharePoint Online
SharePoint Online
Can Query
SharePoint Server
SharePoint Server and SharePoint Online
Search Results
SharePoint Server Search
Center
SharePoint Online Search
Center
SharePoint Server
Search Results
36. Two-way (Bidirectional) Topology
Inbound
SharePoint Server
Can Query
SharePoint Online
SharePoint Online
Can Query
SharePoint Server
SharePoint Server and SharePoint Online
Search Results
SharePoint Server Search
Center
SharePoint Online Search
Center
Outbound
SharePoint Server and SharePoint Online
Search Results
38. Out of the box in SharePoint 2016
August 2015 PU+ in SharePoint 2013
One index to rule them all
Enables Office 365 only features such as Delve
Overview
45. Cloud Hybrid Search
Search content on both systems
Office Graph (Delve)
Hybrid Federated Search
Search content on both systems
New Feature Comparison
46. SharePoint On-premises
Query rules
Result sources
Custom iFilters
BCS connectors
Partner connectors
Custom security trimming
Site collection schema mapping
Custom entity extraction
Content enrichment web service
SharePoint Online
Query rules
Result sources
Search Customization Comparison
47. Are you legally allowed to put your index in Office
365?
Legal Considerations
48. Hybrid Federated Search
- No extra cost
Cloud Hybrid Search
- 1 million on-premises items per 1 TB of
pooled SPO storage
Price
Considerations
Pooled storage = 1 TB + 0.5 GB per User
Globomantics
2000 users
1 TB + (0.5 GB x 2000) = 2 TB
2 TB = 2 million items
49. Hybrid Federated Search
- Pure on-premises users can only search
SharePoint Server
- Users with Office 365 licenses can
search both systems
Cloud Hybrid Search
- All users need an Office 365 license
Licensing
Considerations
So what are we going to talk about today. We will first start talking about What is a Hybrid environment and why should we go hybrid? We will then talk about the Hybrid Extranet Sites, so you can collaborate with Partners, easily and securely. Afterwards, we will talk about another feature called Hybrid Sites and Profiles, that allow us to follow sites on Prem and online in a unified page, and also, when running SharePoint server 2016, allows us to have the extensible app launcher. We will continue by talking about Hybrid OneDrive for Business, and how you can get 1TB or more of space in OneDrive for Business. We will then talk about Hybrid Business Connectivity Services, and how you can securely publish Line of Business Data in SharePoint Online, accessible from everywhere.
We will then talk about the different options we have when we want to implement a Hybrid Search Scenario, we have Federated Search that relies on Result Blocks to show the results, as well as well as Hybrid Cloud Search, which is the new, improved way to show search results, as well as enable us for Delve. Then we will finally conclude with a few words on why Hybrid is important, and do a little Q&A Session.
and then get started with all this great stuff!
Let’s get started!
We see Hybrid in many different fields these days, so let’s talk about what is Hybrid. The most common use of Hybrid your probably see today is Hybrid cars , which run on two different technologies such as regular gasoline and electricity. Another tech item that we see marketed as Hybrid are the Surface Pro tablet / Hybrid combos. Lastly a topic that is closest to our subject today is the Hybrid Cloud. We hear the word cloud so often in 2016, with so many different flavors. Cloud Computing, Public Cloud, Private Cloud, Hybrid Cloud, Community Cloud and the list goes on .
Now that we saw a few hybrid technologies, let’s get a bit more SharePoint specific. There is a common misconception that I see around the SharePoint community that I would like to clear up right away. In a Classical Hybrid cloud, not talking about SharePoint, but the general term, we usually associate Hybrid to having a datacenter or a deployment in our datacenter, in our building, while also having resources in a public or private cloud somewhere else
For SharePoint it is a bit different. A Hybrid SharePoint deployment means the link between a SharePoint On-Premises version such as SharePoint Server 2013 or 2016 and SharePoint Online from Office 365. It’s important to note that we do not care where the SharePoint Server is hosted, the SharePoint Server can be hosted in a Microsoft cloud such as Azure, or in our own datacenter. The important thing to remember is that the hybrid is defined as a link between the SharePoint Server application and SharePoint online, wherever they are hosted.
But why do we even want to go Hybrid? A lot of companies already migrated the Exchange Server and Skype for Business in Office 365, without keeping the on-premises equivalent. The reason is that SharePoint Server, is not equal to SharePoint Online in terms of functionality and flexibility.
I know that even for Exchange, and Skype for business there are differences that could stop a company from migrating, however most companies never customized Exchange, and the business users, do not use Exchange, they use Outlook. Moving services such as Exchange and Skype for Business to the cloud doesn’t have as much of a big impact on business users as moving SharePoint. When we compare SharePoint Server 2013 / 2016 with SharePoint Online, we realize that the UI is different, the capabilities are different, and some customizations we did in SharePoint cannot even be migrated to SharePoint Online.
But why not stay either on-premises, or go fully in the cloud? Let’s take a look at the advantages of each platform.
Let’s start with the advantages of SharePoint Online. As you know Microsoft’s vision is to go Mobile-First Cloud-First, so there is definitely a lot of investment in the cloud from Microsoft. As Microsoft pushes updates to SharePoint Online every two weeks, it also pushes cloud-only updates for example Delve, Office 365 Video and Office 365 groups. Furthermore, another big advantage of SharePoint Online is that by default, is accessible all over the world. You can achieve that with On-Premises as well for sure, but with security and infrastructure investments in order to make it secure. Talking about On-Premises, let’s see with all those cool advantages in the cloud, why would companies want to stay on prem?
There are Multiple good reasons to stay on-premises. The first which is a popular one is that On-Prem allows you to customize your SharePoint to answer to your business needs. Being able to easily develop and create custom branding and solutions on SharePoint is the reason why SharePoint is so used now and had such a great success. Since SharePoint Online doesn’t allow developers to do full trust code, also known as farm solutions, and doesn’t give you access to all of SharePoint such as Timer Jobs for example.
Second reason is having control on the data. For political / legal reasons, some companies need to keep their data in their datacenter or within certain geographical boundaries. Third reason is that, even with the latest updates in SharePoint Online, SharePoint On Premises still has some features that SharePoint Online doesn’t. For example all the BI Stack like Scorecards and Dashboards, Reporting Services, Performance Point. On the search side you miss features such as Custom Entity Extraction. Also since there is no more public site in SharePoint online, you cannot have a Internet site on SharePoint anymore. Other Service Applications missing are Word Automation Service as well a PowerPoint automation services. So as you see, if any enterprise is currently using those features, it doesn’t make sense for them to go to SharePoint Online,
To continue on a subject that is tied with both the Control and features is the limits. There are multiple limits that you simply cannot get around in SharePoint Online. Let me give you a few examples that in my experience have annoyed customers the most. The 5000 list item threshold.. It’s a recommended limit in SharePoint onPrem and customers can change it, but it’s a hard limit in SharePoint Online. There is no public crawl schedule in SharePoint Online, so it can either take minutes or a few hours before your content is crawled. Another big one, if you rely on User Profile audiences to show your data, they usually compile every night in SharePoint On Premises, and you can do it manually. In SharePoint online it’s only once per week on the Saturday! So if you add a user to a audience on Monday, they will need to wait one full week to see the expected results!
To continue on, you cannot have a custom url in SharePoint Online, all your URLS are under the form of companyname.Sharepoint.com. And, you cannot create any custom managed paths except the built in teams / sites one.
Lastly, another difference between On-Premises and SharePoint Online is that on SharePoint Online you do not control the release cycle and the updates. For enterprises that want to control new features and updates to their users, it’s almost impossible in Office 365!
So Why Hybrid? Well with Hybrid you get to use both SharePoint Server and SharePoint Online and decide where each workload goes depending on your business users needs. By enabling a hybrid SharePoint deployment you get the benefits of both SharePoint On-Premises and SharePoint Online to answer your business needs so you get the best of both worlds!
So What are the beenfits of a Hybrid SP Infrastructure?
First one Extranet Sites. To understand the advantages of a Hybrid Extranet, let’s take a look at how we did it on premises since it was defently possible. We have a SharePoint Server 2013 or 2016 farm, that internal users can acces from inside the company network. Furthermore, the SharePoint Farm is opened trough the firewall and on the web where external users can acces it as well. There are multiple scenarios and questions we need to ask ourselves before implementing extranet site and opening up our SharePoint farm to the web.
First of all, do we put the SharePoint farm in a DMZ? Do we create a separate SharePoint Farm? We can’t put only a server in DMZ because with the amount of ports we need to open, it kills the principle of a DMZ.
Also what is the licensing of the external users, and how do we authenticate them? Do we use Form Based auth, do we setup a ADFS federation with each partner, do we just create them accounts in our company Active Directory?
Also what is the risk of opening our SharePoint over the web? We need to put a reverse proxy and make sure everything is secure. Lastly, we need to maintain those users accounts ourselves, either the accounts or the ADFS Federation which can put extra load on the internal IT Department as well the partner’s IT Department.
When we talk about Hybrid Extranet sites, we mean putting all the sites that require collaboration with partners in Office 365. Instead of hosting those sites in our on-prem environment we would host them in Office 365. I know this might not make sense for every company, especially those with heavy custom solutions on their extranet sites, but most extranet sites at the clients I have been at are basic, and only used to transfer documents and information.
In Office 365, you can easily invite external users with a Microsoft account, so you do not need to manage accounts, and you do not need to open your network to the outside.
The advantages are that first, SharePoint Online is open by default to the web, so don’t need to open your internal network anymore and don’t need to create a DMZ.
When you need to create a new Site Collection, it’s easy from the SharePoint Online interface and you don’t need to add anything in the DNS, or create anything new except in SharePonit.
The sharing is secure with Microsoft accounts and you don’t need to manage them internally.
Lastly you can easily enable auditing and see what happens on your partner sites
Now that we know what Hybrid Extranet sites is, let’s go in the lab environment and look at them in action!
When we enable Hybrid Sites the first feature we get is the Site Following. Which means that both the sites we follow On-Premises in SHarePOint 2013 or 2016 and SharePoint Online with be consolidated in the Sites Page in Office 365.
We also get the Profile Redirection, so whenever a user clicks on a profile, they will be redirected to the Delve Profile of the user, instead of going to the On-Premises Profile from SharePoint On-Premises, and to a different profile when clicking in Office 365.
Lastly, if you’re running SharePoint 2016, you also get the Extensible App Launcher. The Extensible App Launcher will make Delve and Video appear in your SharePoint 2016 App Launcher as well as your Custom Office 365 tiles.
To understand what the followed sites feature does, let’s look at the problem it’s trying to fix. Before in a Hybrid scenario, we had Sites and Documents that we were following on –premises, which showed up in our SharePoint 2013 / 2016 MySite , and when we followed Sites and Documents in SharePoint Online, they showed up in the Sites Section of Office 365.
With the new Hybrid Team Sites functionality in SharePoint 2013 / 2016 allows you to see sites that you follow either On-Premises or Online, in one place on the Office 365 Sites page. So, it becomes a lot more transparent and better integration than what we had before.
An important thing to consider is that you cannot activate Hybrid Sites without activating Hybrid OneDrive for Business. I think it’s important to know when you plan the Hybrid Features that you will deploy in your organization.
Now that we know what this feature is, let’s go to the lab and test it out!
Let’s do a small overview of the advantages of implementing Hybrid OneDrive for Business . In a Hybrid OneDrive for Business Scenario, the personal space of the user which was hosted in MySites before, is now in Office 365 where it gets between 1 Terabyte and Unlimited Storage, depending on your plan..
Furthermore, it’s accessible from anywhere in the world, so users can easily access it and work from anywhere. Also, all the backups and growth is handled by Microsoft so you don’t have to worry about users putting too much stuff in OneDrive anymore!.
To show you how this all Works, I created two scenarios. In the first one we will have a user starting from Office 365, and one that starts from SharePoint 2013 or 2016 On Premises. Let’s start with the user that starts from Office 365. The User will first Login , then will click the OneDrive in the App Launcher.
That user will then be redirected to OneDrive for Business in Office 365.
Now lets look at the user starting from On Premises. The User will log into a SharePoint 2013/ 2016 site, and click the OneDrive icon either in the navigation bar for SharePoint 2013, or the App Launcher for SharePoint 2016, SharePoint will look if the user is in the Hybrid Audience. We can select some users to keep using OneDrive for Business On Premises and some to use OneDrive in Office 365. If the User is in the Audience we selected to be Hybrid Enabled, they will be redirected to Office 365, and if they are not in that audience, they will go to their On-Premises MySite. We now have a good idea of how it works, so let’s go configure it.
Let’s talk about Hybrid Search. This can get a bit confusing because of the way that Microsoft named the tools and experiences, so et me clarify it right away. Hybrid Search means the integration between SharePoint On-Premises and SharePoint Online Search.
Before, the Hybrid Search option that we had was Federated Search, which allowed us to search SharePoint Online from on-Prem, and SharePoint on-prem from SharePoint Online, however the user experience was not optimal.
IN August 2015 Microsoft shipped a new type of Hybrid Search that is called the “Hybrid Search Experience”, and is technically enabled by the Cloud Search Service Application. And this is where it can get confusing. Trough this course I will use the Cloud Search Service Application, and Federated Search for the different technologies in order to not cause confusion.
We have a full module dedicated on the differences between them both, so I will not go in detail right now, but I will demo the Cloud Search Service Application right away.
We will first look at an overview of both options, the first one being the Federated Hybrid Search, and the second one the Cloud Hybrid Search. We will then look at the User Experience that our business users get when using both those Hybrid Search Options. Finally we will look at other considerations such as costs, legal and limitations.
Hybrid Federated Search is an option that is included Out of the Box in SharePoint 2013 and SharePoint 2016, however, if you are running on SharePoint Server 2013, Microsoft recommends that you farm be patched at least at the May 2014 Cumulative Update level.
In a Hybrid Federated Search topology, both Systems, and by Systems I mean SharePoint On-Premises 2013, or 2016 and SharePoint Online, have their own Index. So SharePoint On Premises hosts it’s own index with On-Premises content, and SharePoint Online hosts it’s own index with SharePoint Online content.
Lastly, there are three possible topologies we can configure, which we will look at in a few minutes.
So let’s take a look at how the Architecture looks for the Hybrid Federated Search. This is a high level overview of how it works, and we will cover it in detail in the respective module. Let’s start with a Business user that goes to the On-Premises enterprise search center to search for a document. The enterprise Search Center will then forward the query to the SharePoint Server 2016 or 2013 Query component, which will then do two things. First, it will go to the On-Premises index to look for the document, and it will also forward the query to the Query component in SharePoint Online, which will look in it’s respective index as well.
The Query Components will then send the results back to the Search Center, which will then be displayed to the end user. Now that we understand the high level Architecture, let’s take a look at the three available Topologies.
Our first topology is called a One-Way outbound topology. Remember than when we use the words inbound and outbound, we always talk from an On-Premises point of view. So in an Outbound topology, SharePoint Server 2016 goes OUTbound to SharePoint Online.
In an Outbound Topology, SharePoint Server can Query SharePoint Online, but SharePoint Online Cannot Query SharePoint Server. Therefore, when a business user does a search from the SharePoint Server Search Center, they will have both SharePoint On-Premises and SharePoint Online Search Results.
However, Users that do searches from SHarePoint Online, will only see SharePoint Online results, and no results from SharePoint On-Premises.
The second available topology is called the One-Way Inbound Topology. As you might have guessed, this is the opposite of the outbound topology, so SharePoint Server receives an INBound connection from SharePoint Online.
In this topology, SharePoint Server On-Premises cannot query SharePoint Online, however SharePoint Online Can Query SharePoint Server. Therefore, when a user does a search from the SharePoint Online Search Center, they can see results from both SharePoint Online and SharePoint on Premises.
On the other side, if a user does a search from SharePoint On Premises, they will only see SharePoint On-Premises results, and not SharePoint Online.
This brings us to the third and final topology called the Two-Way, or Bidirectional Topology. The Two-Way topology is a merge of the Inbound and Outbound Topologies deployed together. In a Two Way topology, SharePoint Server can Query SharePoint Online, and SharePoint Online can query SharePoint Server.
Therefore, when a user does a search from SharePoint ON-Premises they can see both On-Premises and Online results, and if the user does a search in the SharePoint Online Search Center, they can also see both Online and On-Premises Search Results.
Now the we know how the Hybrid Federated Search Works, let’s take a look at the new Cloud Hybrid Search.
The Cloud Hybrid Search is an out of the box option in SHarePoint 2016, and it’s also available in SharePoint Server 2013 once you install the August 2015 Public Update or higher.
The main technical difference between Hybrid Federated Search and Cloud Hybrid Search is that the Cloud Hybrid Search only has one Index file that contains the data for both On Premises and SharePoint Online. This index is stored in Office 365.
By using the Cloud Search Service Application you also enable features such as Delve and the Office Graphs, that are usually cloud only.
So let’s review the Architecture to see how it all works. For the Cloud Hybrid Search, I will start with the backend. First we have the Cloud Search Service Application configured in SharePoint 2013 or 2016 that will crawl our local SharePoint Sites, and it can also crawl SharePoint 2010, 2013 sites and File Shares. The content is then encrypted and sent to the Content Processing Component in SharePoint Online which will break down the content, and put it in the SharePoint Online Index.
When a User does a Search, for example in the SharePoint Online Search Center, it will search in the SharePoint Online Index, and find the information for both Online and On Premises documents.
As you see, there is no more Index On-Premises and the index is now managed by Microsoft in Office 365. Now that we know how both Search Options Work, let’s take a look at the end user experience that they get.
The User Experience is a very important aspect of any IT implementation, and especially for SharePoint since as SharePoint Administrators, we deploy it for our users. If they don’t like the experience, they might not use the product.
Let’s start with the Hybrid Federated Search. In a Hybrid Federated Search, we have two options on how to display results. The first one is a Result Block. A Result block is displayed on a page, and shows us the results from the other system. In this mockup, I am doing a Search for SharePoint 2016 Hybrid in my On-Premises Search Center , and I can see results from Office 365 in the result block at the top, and then results from my local SharePoint 2016 farm under it. The limitations of result blocks are that you can only show 10 results per result block, and users cannot easily change pages, view the most relevant document from either system combined or easily view more results from a specific system.
The second way of displaying Hybrid Federated Search results is by putting results on different pages. In my Search Center I would have a page only for SharePoint Server results, and a page only for SharePoint Online results.
And now let’s take a look at the Cloud Hybrid Search. The Cloud Hybrid Search is supposed to make the User Experience a lot better. Here I have a mockup of me searching SharePoint 2016 Hybrid in my On-Premises Search Center, and as you see no more result blocks. Since the index is now only in one place, you don’t see a different page for results from the other system either. In this mockup, I have the first and last two results that come from SharePoint On Premises, while the middle two come from SHarePoint Online.
As a user I can see the best result from my query, wherever that result is for, and I don’t necessarily know or care where that result is from, as long as it’s the result I am looking for. IN my opinion is this an a lot better use experience for users than the Hybrid Federated Search. However, there are multiple other considerations to talk about when deciding what solution we should go with, so let’s start talking about them.
We know how the architecture behind the Cloud Hybrid Search and Hybrid Federated Search, as well as the user experience they provide. But there are other things to consider before choosing a solutions uch as Legal, Pricing and Limitation
Let’s start with the new Features Comparison between Cloud Hybrid Search and Hybrid Federated Search. Both Systems allow you to search content on both SharePoint On-Premises and SharePoint Online, however the Cloud Hybrid Search also allows you to use the Office Graph or Delve , so it definitely adds some cool extra features
Now let’s also look at the limitations. As we talked in the first module, one of the advantages of SharePoint On Premises is that you can customize it to your needs. SO let’s take a look at some limitations of SharePoint Search.
First, both systems have Query Rules and Result Sources. However, only SharePoint On-Premises has Custom iFilters, BCS Connectors, Partner Connectors, Entity Extrication, Content Enrichment Web Service.
Since for the Cloud Hybrid Search, everything is managed in the cloud, we are limited to the Search Customization Options of SharePoint Online. For Hybrid Federated Search, you could still get the full Search experience for On-Premises results, and the limited experiences for SharePoint Online.
There are also some legal considerations to consider. A reason why some companies do not go to the cloud is because they need to control where the data is stored. With the Cloud Search Service Application, you can indeed get cool features such as Delve on your On-Premises documents, while the documents stay On-Premises.
However, having the index of your documents in Office 365, is like having all their content in the cloud. Are you legally allowed to do that? With Hybrid Federated Search, one system queries the other, so the index of ON-Prem documents stays On-Premises, however with the Cloud Hybrid Search option, all the index is in the cloud.
Another important part to consider is the Prices for implementations. If we look at Hybrid Federated Search, there is no extra cost , meaning that everything is included in the licenses you already pay.
However, with the Cloud Hybrid Search approach, you are limited on sending one million items per 1 TB of Pooled SharePoint Online Storage. Let’s make sure you understand what Pooled Storage is. At the time of recording this course, the Pooled Storage was equal to 1 TB of storage that everyone got by default, and an extra half gigabyte per licensed user. So if we take Globomantics for example, a company that has 2000 users. Globomantics would have 1 Terabyte plus 2000 times 0.5 Gigabytes for a total of 2 Terabytes of Pooled Storage. That means Globomantics could put two million indexed items in SharePoint Online at no additional cost. This only includes On-Premises items, and not SharePoint Online items, as they are already included in your Office 365 licenses.
If Globomantics needs to push more than 2 million items from On-Premises in the Office 365 index, they would need to purchase extra Pooled Storage from Office 365.
Last but not least, Licensing Considerations. In a Hybrid Federated Search Scenario , Pure SharePoint on-Premises users can only search SharePoint Server content. By Pure On-Premises, I mean users without an Office 365 license. And still in Hybrid Federated Search, users with both On-Premises and SharePoint Online licenses can search both systems.
However with the Cloud Hybrid Search, all your users need to have an Office 365 license to see search results. Since all your content is in the Office 365 index, if your users aren’t Office 365 licensed, they won’t be able to access it. So whether all your users or not have an Office 365 license is definitely something to consider.
So let’s go in our demo environment and look at Hybrid OneDrive for Business as well as the Hybrid Search Experience with the Cloud Search Service Application.
Thank you very much for attending my session, I really hope you enjoyed it and that you have a positive view of SharePoint 2016 as it should be the best release of SHarePoint Ever. If you have any Questions, don’t hesitate to use the chat or send me a tweet or add me on LinkedIn!
Thank you again and have a great Conference!