Three realistic options exist for managing SharePoint Online content types at scale. Which one fits depends on team skills, tenant size, and how frequently the task needs to run.
| Capability | Content Type Hub (admin UI) | PowerShell / PnP | ShareMaster |
|---|---|---|---|
| Edit a single content type definition | Yes | Yes | Yes |
| Push schema changes to all subscribed sites | Yes (automatic) | Yes (scripted) | Hub types only via hub |
| Bulk-update local (non-hub) content types | No | Yes | Yes |
| Bulk-assign a content type to many libraries | No (one library at a time) | Yes | Yes |
| Tenant-wide content type usage report | No | Yes (scripted) | Yes (browser view) |
| No-code / no-script option | Yes | No | Yes |
| Unattended / scheduled automation | No | Yes | No (manual) |
| Visual review before applying changes | Partial | No (script output) | Yes (tree selection) |
| Excel export of content type usage | No | Custom script required | Yes (Report Master) |
What Is a SharePoint Content Type Hub?
The SharePoint Content Type Hub is a single site collection designated as the authoritative source for organisation-wide content type definitions. Admins define content types there, publish them, and SharePoint propagates the definitions to all subscriber sites automatically. The hub is the correct tool for schema changes to organisation-wide content types shared across many site collections, with no scripting required.
Content types created at the individual site level, outside the hub, are called local types. They exist only within their host site. The hub cannot manage them, and changes to hub-published types do not affect local variants of the same name.
Option 1: Content Type Hub (SharePoint Admin UI)
The Content Type Hub is the right place to start for any content type that is intentionally shared across the tenant. Make the change in the hub, save, and republish. SharePoint processes the update as a background job and pushes the new definition to all subscribing site collections.
When the hub works well
If your content type estate is centralised and all sites subscribe to hub-published types, schema updates are straightforward. Adding a new metadata column to a "Contract Document" type in the hub applies it everywhere simultaneously, with no admin visits to individual sites. For large tenants where the alternative is touching hundreds of sites, the hub's propagation model is genuinely powerful.
Where the hub falls short
The hub cannot help with three common situations:
- Local types. Any content type created directly in a site's content type gallery is outside the hub entirely. Updating it on one site does not affect any other site.
- Assignment changes. Adding or removing a content type from a library is not a hub operation. Bulk-assigning a new content type to 50 libraries requires a different approach regardless of whether the type itself comes from the hub.
- Visibility. The hub shows you what types exist and their definitions. It does not show you which libraries across the tenant are actually using each type, or where a type has drifted from the hub definition because a local override was applied.
Propagation is also asynchronous, with no native progress indicator. On a large tenant it can take several hours before all sites reflect a hub change. If you need to confirm propagation has completed, you have to check sites manually or via PowerShell.
Option 2: PowerShell and PnP PowerShell
PowerShell handles what the hub cannot: bulk changes to local content types, bulk library assignment changes, and tenant-wide reporting on content type usage. The relevant PnP PowerShell cmdlets are well-documented:
Get-PnPContentTyperetrieves content type definitions from a site or list.Add-PnPContentTypeToListassigns a content type to a specific library.Remove-PnPContentTypeFromListremoves an assignment.Set-PnPFieldupdates field (column) properties within a content type.Get-PnPTenantSitewith a loop overGet-PnPList -Includes ContentTypesbuilds a tenant-wide usage report.
A standard bulk-assignment workflow uses a CSV list of target sites, loops through each with Connect-PnPOnline, and applies the required change per library. For a one-time operation across 100 sites, a tested script runs unattended overnight and is often the fastest available option.
For teams with PowerShell skills in-house and a need for scheduled or automated execution, this is the right choice. For teams that lack the skills, or where a one-off GUI-based operation is preferable, the maintenance burden of a script often outweighs its flexibility.
Option 3: ShareMaster Explore Master
ShareMaster's Explore Master includes a bulk content type update feature for the scenario where local types or library assignment changes need to be applied across multiple sites without scripting.
The workflow is three steps: connect to the tenant, select the target libraries in the tree view, and apply the change in a single operation. Before anything is committed, the tree view shows exactly which libraries are in scope - useful for catching scope errors that a too-broad or too-narrow script would miss.
For content type assignment changes specifically, this is often the least-friction path available to an admin who does not maintain PowerShell scripts. For schema changes to hub-published types, the Content Type Hub remains the authoritative tool, and Explore Master is complementary rather than a replacement.
See the step-by-step guide to bulk content type updates
Decision Matrix: Which Approach Fits Your Situation?
| Scenario | Best approach | Why |
|---|---|---|
| Update a hub-published type across all subscribing sites | Content Type Hub | Propagation is automatic; no scripting or tool required |
| Bulk-assign a content type to 30+ libraries, no scripting | ShareMaster (Explore Master) | Visual library selection; one-pass apply without PowerShell |
| Update local types across 100+ sites, unattended overnight | PowerShell / PnP | Loop-based scripts are fastest for high-volume one-time changes |
| Report on which libraries use which content types (tenant-wide) | PowerShell or ShareMaster | Admin center has no cross-site content type usage report |
| Non-technical admin, repeatable process without script ownership | ShareMaster (Explore Master) | GUI-based, no PowerShell knowledge required, runs on demand |
| Single library, one-off content type change | Admin UI (site settings) | Fastest for a single target; no extra tooling needed |
| Scheduled monthly content type governance run | PowerShell | Scriptable; integrates with Task Scheduler or Azure Automation |
For most tenants the practical answer involves two tools working in combination: the Content Type Hub for organisation-wide hub-published types, and either PowerShell or ShareMaster for local-type changes and assignment updates. The choice between PowerShell and ShareMaster comes down to whether scripting skills are available and whether an unattended run is needed.
Frequently Asked Questions
Can you bulk-update content types across multiple SharePoint libraries without PowerShell?
Yes. ShareMaster's Explore Master includes a bulk content type update feature that applies changes to multiple libraries in a single GUI-based operation. No PowerShell required.
What happens to existing list items when you update a SharePoint content type?
Updating a content type definition and republishing it changes the column schema on subscribed libraries. Existing items retain their current column values. If you add a required column, existing items without a value fail validation until you supply one.
How do I find all SharePoint libraries that use a specific content type?
The SharePoint admin center has no tenant-wide content type usage report. PnP PowerShell can enumerate all libraries and return their content type assignments using Get-PnPList -Includes ContentTypes in a loop across sites. ShareMaster's Explore Master surfaces the same information in its library browser view without scripting.
Does the SharePoint Content Type Hub update all sites automatically?
It updates all site collections that have subscribed to the published type. Propagation is asynchronous and can take hours on large tenants. Sites using local variants of the same content type are unaffected by hub changes.