Apply to sites
One site design on many sites
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.
What it does
- 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
- Choose a design. From the tenant (or Microsoft's).
- Choose sites. Tick the sites; the count is read back before you continue.
- Options. Queue it (any size) or apply and wait (30 actions or fewer), subsites, skip if already run, how many at once.
- Run. One row per site, read back from SharePoint. Cancel offers Finish current sites, Stop now or Keep running.
- Report. Save the workbook from the finished dialog; History keeps it too.
How it works
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 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.
| Column | Example |
|---|---|
| Site | Project Alpha |
| URL | https://contoso.sharepoint.com/sites/alpha |
| Status | Succeeded |
| Detail | 10 of 10 actions succeeded. |
| Design version | 3 |
| Run id | 6f1c2d3e-… |
| Read back from SharePoint | Yes |
| Actions succeeded | 10 |
| Actions | 10 |
Actions sheet
Every action of every site's run, with SharePoint's outcome.
| Column | Example |
|---|---|
| Site | Project Alpha |
| URL | https://contoso.sharepoint.com/sites/alpha |
| Script | Project lists |
| Action | Create or update list Projects |
| Outcome code | 0 |
| Outcome | Succeeded |
About sheet
The design, method, options, tenant and sign-in.
What you need
- Owner rights on every site. A design limited to named people also needs this account to be one of them.
What it will 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.