Skip to content

Commit 737c596

Browse files
Update multigeo-managedmetadata.md (SharePoint#10319)
* Update multigeo-managedmetadata.md Updated full replication job run time from three days to seven days. * markdown formatting fix, timestamp, spell out number --------- Co-authored-by: Andrew Connell <[email protected]>
1 parent 0183344 commit 737c596

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/solution-guidance/multigeo-managedmetadata.md

Lines changed: 3 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: 06/13/2022
4+
ms.date: 07/02/2025
55
ms.localizationpriority: medium
66
---
77

@@ -23,13 +23,14 @@ The following are important points to know about managed metadata in Multi-Geo t
2323
- 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.
2424
- 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.
2525
- For term sets and terms to be replicated across geo-locations, they need to be set as Available for Tagging.
26-
- The incremental replication process runs hourly. The full replication job runs every three days.
26+
- The incremental replication process runs hourly. The full replication job runs every seven (7) days.
2727
- When you programmatically create a term set in the default geo ___location, that term set is automatically replicated. You don't have to make any changes to the APIs.
2828
- In some cases, you might want a term group, term set, or terms to be available only in a satellite ___location, for example, a term that relates to a confidential project that applies to a specific geolocation. In that case, you can choose to create the relevant terms in the applicable geo-___location.
2929
- If you want the term group to be available only in the default ___location, use the `Set-SPOTenantTaxonomyReplicationParameters` PowerShell cmdlet to explicitly specify which term groups from the default ___location are replicated. This cmdlet is part of the [SharePoint Online Management Shell](https://www.microsoft.com/download/details.aspx?id=35588).
3030

3131
> [!NOTE]
3232
> In a multi-geo scenario, there are protected or special term sets within the term store space that will not be replicated, nor will anything under them be replicated. Those groups are:
33+
3334
> - People
3435
> - Search Dictionaries
3536
> - System

0 commit comments

Comments
 (0)