SharePoint Intermediate Admin Learning Guide

---

Task 1: Designing and Implementing a Global Term Store (Managed Metadata)

---

Objective

Business problem: Without a controlled vocabulary, SharePoint becomes a filing cabinet where everyone invents their own folder names and tags. A document tagged “EMEA,” “Europe,” and “EU Region” by three different people is effectively unsearchable at scale. The Global Term Store solves this by enforcing a single, organisation-wide taxonomy — enabling consistent metadata tagging, filtered navigation, and accurate search refinement across every site collection.

---

Prerequisites

Licenses:

• Microsoft 365 Business Standard or above (SharePoint Online Plan 1/2 included)
• No additional license required for Managed Metadata — it’s included with SharePoint Online

Roles required:

Role	What it can do
Global Admin	Full access — not recommended for day-to-day use
SharePoint Admin	Access to Term Store in Admin Center — preferred
Term Store Administrator	Can manage all groups and term sets — assign this specifically

Principle of least privilege: Don’t use Global Admin for Term Store work. Assign the Term Store Administrator role to whoever owns taxonomy governance — this is a separate delegation from SharePoint Admin.

---

Step-by-Step Execution

Path A: SharePoint Admin Center (GUI)

1. Access the Term Store

• Navigate to: https://[tenant]-admin.sharepoint.com
• Left nav → Content services → Term store

2. Create a Term Store Group

A Group is the top-level container — typically mapped to a business unit or domain (e.g., “Finance,” “HR,” “Legal”).

• Click Add term group
• Name it clearly: use the business unit name, not generic labels like “Group 1”
• Assign Group Managers — these are the people who own this taxonomy domain

3. Create a Term Set within the Group

A Term Set is a controlled list of values (e.g., “Region,” “Document Type,” “Project Status”).

• Select your new Group → click Add term set
• Configure:
  • Name: e.g., Document Type
  • Description: what this term set governs
  • Submission policy: set to Closed to prevent users adding ad hoc terms
  • Available for tagging: toggle ON

4. Add Terms

• Select the Term Set → click Add term
• Build out your hierarchy — Term Sets support up to 7 levels of nesting (use sparingly; flat is usually better)
• Example flat structure for Document Type:
  • Policy
  • Procedure
  • Template
  • Report
  • Proposal

5. Connect a Term Set to a Site Column

• Go to any SharePoint site → Site Settings → Site columns → Create
• Column type: Managed Metadata
• Under Term Set Settings, browse to and select your Term Set
• Add this site column to a content type or list

---

Path B: PowerShell (PnP)

Install PnP PowerShell if you haven’t already:

Install-Module PnP.PowerShell -Scope CurrentUser
Connect-PnPOnline -Url "https://[tenant]-admin.sharepoint.com" -Interactive

Create a Term Group and Term Set:

# Get the default site collection term store
$termStore = Get-PnPTermStore

# Create a new Term Group
$termGroup = New-PnPTermGroup -Name "Enterprise Content" -Description "Global taxonomy for all business units"

# Create a Term Set within the group
$termSet = New-PnPTermSet -Name "Document Type" `
    -TermGroup $termGroup `
    -Lcid 1033 `
    -IsOpenForTermCreation $false `
    -Description "Approved document classification values"

# Add terms to the Term Set
$terms = @("Policy", "Procedure", "Template", "Report", "Proposal")

foreach ($term in $terms) {
    New-PnPTerm -Name $term -TermSet $termSet -TermGroup $termGroup -Lcid 1033
}

Write-Host "Term set created successfully with $($terms.Count) terms."

Verify your Term Store structure:

# List all Term Groups
Get-PnPTermGroup | Select-Object Name, Description

# List Term Sets within a Group
Get-PnPTermSet -TermGroup "Enterprise Content" | Select-Object Name, IsOpenForTermCreation

---

The Admin Gotcha ⚠️

Replication lag will catch you off guard.

After creating or modifying terms in the Term Store, changes can take up to 24 hours to fully propagate across all site collections — though in practice it’s usually 15–60 minutes. This becomes a serious problem if you’re running a go-live or training session the same day you built the taxonomy.

Common mistake: Admins build the Term Store, immediately try to tag a document on a newly created site, and the Managed Metadata column shows an empty picker. They assume something broke and start rebuilding — when the fix is simply waiting.

Real-world mitigation:

• Build and finalise your Term Store at least 24 hours before any user-facing deployment
• Use Get-PnPTerm in PowerShell to verify terms are retrievable before declaring the taxonomy ready
• If you need to force a faster sync for testing, create the Managed Metadata column in the Admin Center Term Store UI rather than PowerShell — GUI changes tend to propagate slightly faster

---