Content type syndication is one of the more opaque mechanisms in SharePoint Online administration. This reference covers what propagates, what does not, timing expectations, permissions, and what to check when updates fail to appear on subscriber sites.
What is the content type hub propagation?
The SharePoint content type hub is a designated site collection that acts as the source of truth for shared content types across the tenant. Admins define content types there - columns, metadata fields, document templates - then publish them. SharePoint's syndication timer job picks up published changes and pushes them to every site collection that has subscribed to those content types.
"Subscribed" sites are those that already use the hub content type in at least one list or library. They receive updates automatically without requiring any per-site configuration on each update cycle.
Propagation timing reference
| Stage | Typical timing | Notes |
|---|---|---|
| Hub publish to timer job pickup | Up to 1 hour | The syndication timer job runs approximately every 60 minutes. Publishing at 09:05 may not trigger until the 10:00 run. |
| Timer job to subscriber site update | 1 to 4 hours (small-medium tenants) | Larger tenants with thousands of site collections take longer. Microsoft does not publish a guaranteed SLA. |
| Total end-to-end (publish to visible on sites) | Typically 1 to 6 hours | For urgent rollouts, plan the publish at least half a day before you need it to appear everywhere. |
| New column added to existing content type | Same as above | New columns propagate with the next cycle. Existing list items do not gain the column's value retroactively; only new and edited items will use it. |
| Content type deleted from hub | Not automatically removed from sites | Deleting a published content type from the hub does not remove it from subscriber sites. Sites retain the local copy even after hub deletion. |
What propagates vs. what does not
| Change made in the hub | Propagates to subscriber sites? | Detail |
|---|---|---|
| Add a new site column to the content type | Yes | Column is added to the content type on subscriber sites. Existing items in lists that use this content type will not automatically have a value for the new column. |
| Change a site column's display name | Yes | The updated display name appears on subscriber sites after propagation. |
| Change a site column's required/optional setting | Yes | Required state is pushed to subscriber sites and takes effect on the next form render. |
| Change a site column's default value | Yes | New default applies to new items after propagation. Existing items are not updated. |
| Update the document template (default .docx/.xlsx) | Yes | New template file propagates to subscriber sites and replaces the local copy. |
| Remove a site column from the content type | Partial | The column is removed from the content type definition but data in existing list items using that column is not deleted. The column itself may remain in the site's column gallery. |
| Change the content type name | Partial | The internal content type ID does not change. The display name updates on subscriber sites, but local customisations or workflows referencing the old name by string may break. |
| Delete the content type from the hub | No | Subscriber sites retain a local copy of the content type indefinitely. Sites do not lose the content type when it is deleted from the hub. |
| Permission level changes on the hub site | No | Hub site permissions are scoped to the hub site collection only. They do not propagate to subscriber sites. |
| Workflow or Power Automate flow attached to a content type | No | Flows and workflows are site-scoped. They do not travel with the content type during syndication. |
| View customisations on lists using the content type | No | List views are local to each site collection and are not part of the content type syndication payload. |
Permissions required
| Task | Permission needed | Where to assign |
|---|---|---|
| Create and edit content types in the hub | Site collection administrator or member of the Hub Designers group | Hub site collection permissions or SharePoint admin centre |
| Publish a content type from the hub | Site collection administrator on the hub site | Hub site collection permissions |
| Access the Content type gallery in the admin centre | SharePoint Administrator or Global Administrator in Entra ID | Microsoft 365 admin centre > Roles |
| Force-subscribe a site to a hub content type | Site collection administrator on the subscriber site | Subscriber site settings > Site content types > Add from hub |
| View syndication status and errors | SharePoint Administrator or Global Administrator | SharePoint admin centre > Content services > Content type gallery |
Common propagation failures and causes
| Symptom | Likely cause | Remedy |
|---|---|---|
| Update visible on one site but not another after 6+ hours | The second site has a local (sealed) copy of the content type, breaking the hub subscription | Check the site content type page; if it does not show "obtained from a content type hub", re-add the hub version |
| New column visible in content type settings but not appearing in list forms | The list form is using a custom form (SPFx, InfoPath legacy) that does not reflect dynamic content type changes | Update the list's default content type form or rebuild the custom form to include the new column |
| Content type appears in the hub gallery but not available to add to sites | Content type is saved but not yet published; "Published" status must be explicitly set | In the Content type gallery, open the content type and select Publish |
| Column removed from hub content type still visible on subscriber sites | Partial propagation: column removed from content type schema but remains in the site's column gallery | Manually remove the orphaned column from site columns on each subscriber site if needed |
Bulk content type updates across many sites
The hub syndication mechanism works well when sites are properly subscribed. However, if you need to push content type changes to sites that have broken their hub link, or to apply bulk updates beyond what the hub propagates (such as retiring an old content type from 80 site collections), manual site-by-site work becomes impractical.
PnP PowerShell can automate content type operations across multiple sites, though it requires scripting for each site collection in sequence. For bulk-updating the content type assigned to items within a library, ShareMaster's Explore Master provides a desktop interface for that operation without PowerShell scripting.
Frequently Asked Questions
How long does SharePoint content type hub propagation take?
Typically one to four hours for small-to-medium tenants. The syndication timer job runs approximately every hour, and larger tenants may queue behind a higher volume of sites. Microsoft does not publish a guaranteed SLA for content type syndication. Plan hub publishes well before any deadline.
What is the SharePoint content type hub URL?
The modern entry point is the SharePoint admin centre under Content services > Content type gallery. The underlying hub site collection typically lives at https://yourtenant.sharepoint.com/sites/contenttypehub, but the exact URL depends on your tenant setup. The admin centre view is the recommended interface for SharePoint Online.
Does publishing a content type from the hub automatically update all subscriber sites?
Yes, for sites that have already subscribed by adding the hub content type to a list or library. Updates propagate on the next syndication cycle (roughly every hour). Sites that have never added the hub content type do not receive the update until they explicitly add it from the hub.
Learn more about Explore Master for bulk content type management