Skip to content

Commit 7ff60f4

Browse files
Merge pull request SharePoint#6292 from italou/patch-1
Replication of Term sets and terms
2 parents 1627df5 + 236b4b7 commit 7ff60f4

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/solution-guidance/multigeo-managedmetadata.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Manage metadata in a Multi-Geo tenant
33
description: Managed metadata that you define for the default geo ___location of a Multi-Geo tenant is automatically replicated to the tenant's satellite locations, and is only available to the sites hosted in that geo ___location.
4-
ms.date: 11/12/2019
4+
ms.date: 10/09/2020
55
localization_priority: Normal
66
---
77

@@ -23,7 +23,9 @@ The following are important points to know about managed metadata in Multi-Geo t
2323

2424
- Create term groups, term sets, and terms in the default geo ___location. This ensures that they are consistently available across all the geo locations in your tenant.
2525

26-
- When term groups, term sets, and terms are replicated across geo locations, they retain their ID. This allows you to reference term groups, term sets, and terms based on ID, regardless of the geo ___location your code is running in.
26+
- When term groups, term sets, and terms are replicated across geo locations, they retain their ID. This allows you to reference term groups, term sets, and terms based on ID, regardless of the geo ___location your code is running in.
27+
28+
- For term sets and terms to be replicated across geo locations, they need to be set as Available for Tagging.
2729

2830
- The incremental replication process runs hourly. The full replication job runs every three days.
2931

0 commit comments

Comments
 (0)