Skip to main content

Document ID Service

The Document ID Service assigns every file in a site collection a unique, permanent identifier that stays with the document no matter where it moves. Turn the feature on and SharePoint stamps each item with an ID built from a configurable prefix of four to twelve characters, then exposes a static link of the form /_layouts/15/DocIdRedir.aspx that always resolves to the current location of that document. Because the link points to the ID rather than a folder path, references in emails, other documents, or pages keep working even after the file is renamed or moved to another library. The ID is also searchable through the DlcDocId managed property. Document IDs are unique within a site collection, not across the whole tenant, and the service is a site collection feature you activate. It is the out-of-the-box answer to broken links when content gets reorganized.
Related
Content Type, Document Library, Managed Properties, Metadata, Move and Copy, Version History

Common Use Cases

  • Stable references: cite a document by an ID that survives moves
  • Cross-document links: reference files from other files reliably
  • Records and contracts: a permanent handle for auditable documents
  • Reorganizing libraries: restructure content without breaking links
  • Help desk lookups: find a file by quoting its short ID
  • Policy citations: reference standards by a fixed identifier

How It Works

  • Site collection feature: activated once per site collection
  • Automatic stamping: every uploaded file receives an ID
  • DocIdRedir link: the /_layouts/15/DocIdRedir.aspx URL resolves to the file
  • Follows the file: the ID persists through rename and move
  • Searchable property: findable through the DlcDocId managed property
  • ID column: a Document ID column can be added to library views

Settings

  • Custom prefix: set a four to twelve character starting string
  • Assign to existing: apply IDs to content already in the site
  • Reset option: regenerate IDs after configuration changes
  • Per site collection: each collection configures its own prefix
  • Column display: surface the linked Document ID in views
  • Activation control: site collection admins enable the feature

Benefits

  • Links that do not break: references survive reorganization
  • Portable identifiers: a handle independent of folder structure
  • Findable: IDs work as search terms across the site collection
  • Low effort: automatic once the feature is on
  • Audit friendly: a consistent reference for governance and records
  • Out-of-the-box: no code or third-party tool required

Details

  • Feature Category: Metadata & Taxonomy

Limits and Nuances

  • Site collection scope: IDs are unique within a collection, not the tenant
  • Not instant: a timer job assigns IDs, so there can be a delay
  • Cross-collection moves: moving between collections can reassign the ID
  • Prefix planned early: changing it later affects only new items
  • Not version control: IDs identify the file, not its versions
  • Activation required: it is off until a site collection admin enables it

Common Questions About the Document ID Service

What is the Document ID Service in SharePoint?

It is a site collection feature that gives every document a unique, permanent identifier that stays with the file wherever it moves. Once enabled, SharePoint stamps each item with an ID and provides a static link that always resolves to the document’s current location. That means references by ID keep working even after the file is renamed or moved, solving the classic problem of broken SharePoint links.

How does the static Document ID link work?

When the service is on, each document gets a redirect URL in the form /_layouts/15/DocIdRedir.aspx with the ID appended. Opening that link sends SharePoint to look up the ID and forward you to wherever the file currently lives. Because the link references the ID rather than a folder path, it survives moves and renames, which is why it is reliable to paste into emails, pages, or other documents.

Are Document IDs unique across the whole tenant?

No. Document IDs are unique only within a single site collection, not across your entire SharePoint environment. Each site collection has its own prefix and its own ID sequence, so the same ID could in theory exist in two different collections. If you move a document between site collections, it can be assigned a new ID rather than keeping its original one.

Can I customize the Document ID prefix?

Yes. When you configure the service you can set a custom prefix of four to twelve characters that begins every ID in that site collection, which many organizations use to signal the source or content type. SharePoint generates a default prefix if you do not set one. The prefix applies going forward, so plan it before relying on IDs across a lot of content.

Why do my Document IDs not appear immediately?

Assigning IDs relies on a background timer job rather than happening the instant a file is uploaded, so newly added documents can go a short while before their ID appears. This is normal, especially right after you first enable the feature on a site collection with existing content, where it processes items in the background. The IDs do appear once the job runs.

When is the Document ID Service worth setting up?

Document IDs are most valuable when they are part of a deliberate information architecture rather than switched on as an afterthought. Greg Zelfond, the consultant behind LookBook 365, plans prefixes, library structure, and metadata together so identifiers are meaningful and links stay stable as content grows. If your organization is wrestling with broken links and shifting libraries, that structured setup is the kind of work he handles.