Metadata and Managed Terms

A Choice column stores a flat, hardcoded list of options defined per-site-column, which works fine for a small, stable set of values but becomes hard to govern across a large tenant because every site might define its own slightly different Choice list. A Managed Metadata column instead points to Term Sets stored centrally in the Term Store, a hierarchical taxonomy service shared across the entire tenant, so the same 'Department' or 'Product Line' taxonomy can be enforced consistently everywhere, updated in one place, and support synonyms so users can search using alternate labels that resolve to the same term.

The Term Store organizes vocabulary into Term Group (a top-level container often scoped by department or business unit, with permissions controlling who can manage it), Term Set (a specific taxonomy within a group, like 'Geography' or 'Product Categories'), and individual Terms, which can themselves be nested to represent parent-child hierarchy — for example a 'North America' term containing child terms 'USA' and 'Canada'. Each term has a stable GUID that doesn't change even if the term's display label is renamed or translated, which is what allows tagged content to remain correctly classified across label changes and multiple languages.

Once a Managed Metadata site column is bound to a Term Set, users tagging a list item get type-ahead suggestions pulled live from the Term Store, and multiple terms can be allowed per column if the field is configured to accept multiple values, letting one document carry several tags like both 'Finance' and 'Q3-2026' from different term sets. Metadata Navigation, configured in Library Settings, lets you designate a Managed Metadata column as a navigation hierarchy in the left-hand tree view, so users can filter a large library by clicking through term hierarchy nodes instead of building a manual view filter, and this navigation works efficiently even on libraries near the list view threshold because it uses indexed term lookups.