ShareMaster is shaped by your feedback. Tell us what to build next →
Features All features overview
Migration Tools Overview Structure and content OneDrive ↔ SharePoint Content only Structure only Move / Copy Upload from this computer Download to this computer Dropbox to SharePoint Resume and incremental runs
Microsoft Teams Overview Copy a team Move channels Merge teams Inactive teams Ownerless teams Guests and external access Export a team Search everyone's chats
Recycling Bin Overview Browse a site's recycle bin Empty recycle bins in bulk Restore and purge history Deleted teams
Archive Overview Configure the tenant On Demand Archive Restore Archived Files Archive Savings Report Blob Viewer
Optimise Storage Tools Overview Delete all items in a list Delete all files and folders in a library Remove empty folders Remove duplicate files Reduce image sizes Delete sites and subsites
SharePoint Tools Overview Tenant Explorer SharePoint Explorer Easy Settings Fix renamed groups List Explorer Search the Preservation Hold Library
Search & Indexing Overview Search query Item search properties Reindex Crawl log
Replace Overview Replace in SharePoint Replace in local files Find password-protected files Remove PDF passwords
Shared Links Overview Report shared links Report unique permissions Remove a person from sharing links Remove shared links Remove unique permissions
Version History Overview Version trimming Version trimming report Reset file version
Reports Overview Inventory report Folder inventory Site and subsite storage Storage growth Security matrix Teams permissions Pre-migration analysis Compare items Dropbox to Microsoft 365 compare Duplicate file report Empty folder report Image size report Recycle bin report Unused licences Copilot readiness Inactive sites, OneDrives and groups Orphaned users Site settings Audit activity Groups Checked-out files report Report history
Developer Tools Overview Query Builder PnPjs Console Property Bags SPFx Customizers Webhooks Customisation audit
Pricing Services Demos Blog Guides Use cases Compare Tools Alerts FAQ Contact
  1. Home
  2. Documentation
  3. SharePoint tools

Apply to sites Coming soon

One site design on many sites

Coming soon. This tool is built and shows on its menu, but it does not open in a released build yet. This page describes it as it will ship.

Apply one site design to many sites in one run. Each site's own run history is read first so a site the design already ran on is skipped, each run is read back from SharePoint, and a workbook records every site and every action.

Makes changes. Changes every chosen site. SharePoint cannot undo a site design.

What does it do?

  • Which sites took the design, which were skipped because it already ran, and which failed and why.
  • For each site, how many of the design's actions succeeded - "9 of 10" is a failed site, not a done one.

How it runs

  1. Choose a design. From the tenant (or Microsoft's).
  2. Choose sites. Tick the sites; the count is read back before you continue.
  3. Options. Queue it (any size) or apply and wait (30 actions or fewer), subsites, skip if already run, how many at once.
  4. Run. One row per site, read back from SharePoint. Cancel offers Finish current sites, Stop now or Keep running.
  5. Report. Save the workbook from the finished dialog; History keeps it too.

How does it work?

Before the run, the design's scripts are read and their actions counted, and Apply and wait is offered only when the total is within Microsoft's limit for it. Subsites, when included, are found at the start of the run; a site whose subsites could not be listed is noted and its subsites are left out. Nothing is sent to a site outside the connected tenant.

With Skip if already run on, each site's own run history is read first. A site is skipped only if this design, at this version, already ran there with every action succeeding; an earlier run that failed is not a reason to skip, and if the history cannot be read nothing is applied to that site.

Queue hands the design to SharePoint to run in its own time; ShareMaster then waits for that task to leave the queue, finds the run SharePoint recorded for it, and reads the outcome of every action. Apply and wait gets the outcomes back directly. Either way a site counts as succeeded only when every action did: one failed action makes it a failed site, with the count and the failed actions named. Only one run of the design is in flight on a site at a time.

A queued run you chose not to wait for is reported as queued but not confirmed. One still running when the wait ends is reported that way, with a note to check the site's run history before applying again. Each site is logged before it starts and after it finishes, and the run is kept in History with its workbook. There is no undo: SharePoint cannot reverse a site design.

What do you get?

An Excel workbook, named like Site design apply 2026-10-07 14-22.xlsx, kept in Report History whether or not you save it.

Sites sheet

One row per site.

ColumnExample
SiteProject Alpha
URLhttps://contoso.sharepoint.com/sites/alpha
StatusSucceeded
Detail10 of 10 actions succeeded.
Design version3
Run id6f1c2d3e-…
Read back from SharePointYes
Actions succeeded10
Actions10

Actions sheet

Every action of every site's run, with SharePoint's outcome.

ColumnExample
SiteProject Alpha
URLhttps://contoso.sharepoint.com/sites/alpha
ScriptProject lists
ActionCreate or update list Projects
Outcome code0
OutcomeSucceeded

About sheet

The design, method, options, tenant and sign-in.

What do you need?

  • Owner rights on every site. A design limited to named people also needs this account to be one of them.

What will it not do?

  • SharePoint cannot undo a site design. The workbook and History record what ran, not a way back.
  • Only designs are applied in bulk: a bare script is run step by step on one site instead.
  • A queued run that is not waited for is reported as not confirmed, never as done.

See every feature