Managed Metadata Column

A Managed Metadata column connects a list or library to the Term Store, so users tag items by picking from a managed term set instead of typing free text. As they type, it suggests matching terms and synonyms, or they browse the term tree. You point it at one term set (or a single branch of it), allow a single or multiple values, optionally set a default, and decide whether users may add new terms. Because the field stores the term's underlying ID, renaming a term in the Term Store updates every tagged item automatically.

Choice Column, Enterprise Keywords, Lookup Column, Managed Metadata, Metadata, Term Set, Term Store

Department and region tagging: point a column at a shared Departments term set so every site tags people and documents with the same official values
Document type classification: a Document Types column keeps contracts, policies, and reports labeled consistently across libraries for filtering and search
Client and project taxonomies: tag deliverables with the same client or project list used everywhere, then roll content up by client in search and rollup web parts
Multilingual tagging: one term carries labels in several languages, so users pick and filter in their own language while the stored term stays a single record
Search refinement: managed metadata column values feed search refiners, letting users narrow results by department, product, or region
Records and retention: classification and retention rules key off standardized term values rather than inconsistent free text

Benefits

Consistent, governed values: users pick from the Term Store, so the same vocabulary stays identical across every list and site that uses it
Type-ahead and browse: the picker suggests matching terms and synonyms as users type, or they can browse the full term tree
Central renaming: rename a term once in the Term Store and every item already tagged with it updates automatically
Synonyms catch shorthand: a term can carry alternate labels, so typing HR resolves to the official Human Resources term
Single or multiple values: tag an item with one term or several, depending on how the column is configured
Reuse across the tenant: the same term set powers columns on many sites, instead of rebuilding a choice list in each place

Details

Feature Category: Columns & Views

How It Works

Points at one term set: each column maps to a single term set, or to one branch within it, that supplies the available values
Term Store backed: values come from the Term Store in the SharePoint admin center, not from the list itself
Single or multi-value: choose whether the column accepts one term or several when you create it
Fill-in needs two switches: users can add a new term only if the term set is open and the column allows fill-in values
Default value optional: you can set a default term that pre-fills for new items, typed or chosen with the term picker
Stores label plus ID: the field keeps both the visible label and the term’s underlying ID, which is why central renaming flows through to tagged items

Limits and Nuances

Counts toward the lookup limit: a Managed Metadata column counts against the 12-column List View Lookup Threshold alongside Lookup and Person columns, so budget view columns accordingly
No sorting on multi-value columns: a column that allows multiple values cannot be sorted in views; use a single-value column where sorting matters
Closed term sets block fill-in: if the term set is closed, the Allow fill-in option is unavailable and users cannot add new terms
Not usable in calculated columns: formulas cannot reference a Managed Metadata column
Needs a maintained taxonomy: the column is only as good as the term set behind it, so someone has to own and curate the Term Store
Large term sets slow the picker: keep the set users browse to a manageable size and use hierarchy to organize it
Hidden companion field: each Managed Metadata column creates a hidden text field that stores the value for sorting, filtering, and search, which can surface in exports or integrations
Choice is simpler when local: for a short, stable value list used on a single site, a Choice column is the easier out-of-the-box option

Common Questions About the Managed Metadata Column

What is a Managed Metadata column in SharePoint?

A Managed Metadata column lets users tag a list or library item by choosing from a term set in the Term Store instead of typing free text. As they type, it suggests matching terms and synonyms, and they can browse the full term tree. Because the values are centrally managed and reused across sites, the same vocabulary stays consistent everywhere the column is used.

What is the difference between a Managed Metadata column and a Choice column?

A Choice column stores its options inside one list, so the same values retyped on another site can drift apart. A Managed Metadata column pulls from the Term Store, a central dictionary shared across the whole tenant, and adds synonyms, hierarchy, multilingual labels, and central renaming. For a short, stable list on one site, Choice is simpler; for a shared vocabulary, Managed Metadata scales.

Can a Managed Metadata column allow multiple values?

Yes. When you create the column you decide whether it accepts a single term or several. Multi-value is useful for items that belong to more than one category, but it carries a trade-off: a multi-value Managed Metadata column cannot be sorted in views. If sorting on that field matters, use a single-value column instead.

Can users add their own terms to a Managed Metadata column?

Only when two settings line up. The term set it points to must have an open submission policy in the Term Store, and the column itself must have Allow fill-in enabled. If the term set is closed, which is the common governance choice, the fill-in option is unavailable and users can only pick from existing terms.

Why does a Managed Metadata column count against the 12-column lookup limit?

Because it resolves its value from the Term Store rather than storing it inline, SharePoint treats it like a lookup. The List View Lookup Threshold blocks any view that uses more than 12 lookup-type columns, and Managed Metadata, Lookup, and Person columns all count, including built-in ones. Plan how many of these columns a single view needs.

When should I use a Managed Metadata column instead of a Choice column?

Reach for Managed Metadata when the same vocabulary must stay consistent across many sites, needs synonyms or hierarchy, or supports multiple languages; choose Choice for a short, stable list that lives in one place. Greg Zelfond, the consultant behind LookBook 365, treats that as an information-architecture decision made up front, not a column setting changed later, because a managed taxonomy only pays off when someone owns the Term Store behind it.