Plan hybrid SharePoint in Microsoft 365 taxonomy and hybrid content types
APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
SharePoint hybrid taxonomy enables you to have a single taxonomy that spans SharePoint Server and SharePoint in Microsoft 365. This single taxonomy gives you a single, consistent taxonomy no matter where your sites are located.
You can choose which term groups are shared between SharePoint Server and SharePoint in Microsoft 365 and which are on-premises only or online only.
The shared taxonomy is mastered in SharePoint in Microsoft 365 and a read-only copy is kept updated in SharePoint Server. Shared terms, term sets, and groups are available in both locations.
Farm Administrators can modify Term Groups on-premises. These changes will not replicate to SharePoint in Microsoft 365. It is important that Farm Administrators be notified to not make changes on-premises.
You also have the option of installing hybrid content types. This feature propagates updates made to your SharePoint in Microsoft 365 content types to your SharePoint Server site collections.
Hybrid SharePoint taxonomy and hybrid content types are available in SharePoint Server 2013 and SharePoint Server 2016 with the following [SharePoint updates](/officeupdates/SharePoint in Microsoft 365-updates):
Hybrid taxonomy requires the November 2016 public update or later.
Hybrid content types require the June 2017 public update or later.
Configuration of both features uses the Hybrid Configuration Wizard in the SharePoint admin center, which also has many prerequisites. Be sure to read Hybrid picker in the SharePoint admin center as you plan your hybrid SharePoint taxonomy rollout.
The functionality and configuration procedures are the same for both versions of SharePoint Server.
As with all hybrid scenarios, hybrid SharePoint taxonomy and hybrid content types both rely on your user accounts being synchronized between SharePoint Server and SharePoint in Microsoft 365, though users whose accounts aren't synchronized can still use the replicated and local term sets on-premises.
How hybrid SharePoint taxonomy works
Hybrid SharePoint taxonomy works by replicating changes that you make to your taxonomy in SharePoint in Microsoft 365 to your term store in SharePoint Server. Replication is done at the term group level. Groups that are replicated via hybrid SharePoint taxonomy are set to read-only in SharePoint Server and can only be updated in SharePoint in Microsoft 365. (A term store administrator can still update the SharePoint Server groups, but such updates will be overwritten during the next replication.)
You choose the groups that you want to share across SharePoint Server and SharePoint in Microsoft 365. System and special groups (the System, Search, SearchDirectories, and People groups) can't be replicated, but any other groups that you create can be. (Be sure you're not reusing terms between groups that you replicate and groups that you don't replicate.)
The Taxonomy Groups Replication SharePoint Server timer job polls SharePoint in Microsoft 365 for taxonomy changes on a daily basis and replicates them to the SharePoint Server taxonomy store. This timer job performs a daily update of changes and a weekly full replication. You can reschedule the timer job to meet your needs or run it manually when you want to force an update.
If you already have a taxonomy in SharePoint Server, you can copy it to SharePoint in Microsoft 365 by using PowerShell. This taxonomy - once copied into SharePoint in Microsoft 365 - allows you to create your master taxonomy from your existing SharePoint Server and SharePoint in Microsoft 365 taxonomies, while maintaining the IDs of the terms, term sets, and term groups in those taxonomies.
We recommend that you copy your taxonomy to SharePoint in Microsoft 365 before you set up hybrid SharePoint taxonomy. You can do so at a later time, but you'll have to rerun the Hybrid Configuration Wizard in order to turn on replication for those groups.
Local term sets
You can continue to work with local term sets in both locations. They remain local and aren't affected by hybrid SharePoint taxonomy. These local site-specific terms can't be replicated.
How hybrid content types work
If you already have content types in SharePoint Server, you can copy them to SharePoint in Microsoft 365 by using PowerShell. These content types - once copied into SharePoint in Microsoft 365 - allows you to create your master content types list from your existing SharePoint Server and SharePoint in Microsoft 365 content types. You control which content types are shared across SharePoint in Microsoft 365 and SharePoint Server.
We recommend that you copy your content types to SharePoint in Microsoft 365 before you set up hybrid content types.
Get set up
To get started configuring hybrid SharePoint taxonomy and hybrid content types, be sure you've reviewed the prerequisites for the Hybrid Configuration Wizard, and then read Configure hybrid SharePoint taxonomy and hybrid content types.