Templates
Set up one tenant the way you want it, capture that setup, and apply it to any other tenants in your account in one go. Build your standard apps, policies, custom fields, groups and scripts once, then stamp them onto every new customer.
In short
- A template is a snapshot of one kind of item from one tenant: apps, policies, custom fields, groups or scripts.
- Applying only ever creates. An item whose name (or key, for a custom field) already exists in a tenant is skipped and left as it was.
- When a new tenant needs custom fields, groups and scripts, apply them in that order.
- Scheduled scripts in a template start running in each tenant you apply it to.
How it works
Set up one tenant the way you want every tenant to look.
Many teams keep a dedicated reference tenant for this.Capture a template from it on the Templates page.
A template is a snapshot of one kind of item: apps, policies, custom fields, groups or scripts.Apply the template to the tenants you choose.
Each tenant gets the items it does not already have.
Templates belong to your account, not to a tenant, and they are for the people who work across it: the Account Owner, and MSP Technicians or MSP Read Only users granted all tenants now and in future, see the same list from every tenant.
A user who was given access to particular tenants, such as a customer's own administrator, does not see Templates at all, so a scripts template captured from one customer is never visible to another.
What each template captures
| Template | Included | Not included |
|---|---|---|
| Apps | Every app with its install and deployment settings, its Toast notifications setting, its pre- and post-install scripts, its catalog link and its Self-Service category | Assignments to groups, and app dependencies: add each app’s Install Before This App list again on its page |
| Policies | Every policy profile with all of its settings. A tenant with Policies turned off skips them when you apply | Assignments to groups |
| Custom Fields | Every field: key, name, description and type | The values collected from devices |
| Groups | Every group you created, with its rules | All Devices, Entra ID groups, and manually added members |
| Scripts | Every script with its content, shell, run context and collector settings, plus its first (oldest) schedule with target and excluded groups by name | Any later schedules, schedules that target individual devices, and past runs |
Capture a template
Switch to the tenant you want to copy from.
Go to Templates and click Capture from Tenant.
Pick the template type.
The dialog lists the tenant's items of that type that a template can hold, all ticked.Untick anything you want to leave out, or click Clear all and tick just the items you want.
Each item shows what it relies on in a tenant, such as the custom field a group's rule uses or the groups a script's schedule targets, so you can capture those in their own template too.Give the template a name and click Capture Template.
A template is a snapshot. Changing the tenant you captured from later does not change the template on its own; use Refresh from Tenant to bring it up to date. Apps and policies can also be saved as a template straight from their own pages.
Refresh a template
When you add to your reference tenant, you do not need to delete the template and capture it again.
Open the template and click Refresh from Tenant.
Pick the tenant to read from.
It starts on the tenant you are in, and it does not have to be the one the template was captured from.Choose how to update the template.
- Add new itemsThe usual choice
- Keeps everything in the template as it is and adds what the tenant has that the template does not.
- Update the template's items
- Takes the tenant’s current version of the items already in the template, and adds or removes nothing. Use it for a template you built from a hand-picked selection.
- Replace with the tenant's items
- Makes the template match the tenant exactly: new items are added, changed ones are updated and items the tenant no longer has are removed from the template.
Click Preview Changes.
The preview lists what will be added, and also what is different in the tenant or missing from it, so you can see what each choice would do. Nothing is saved yet.With Add new items, untick the new items you do not want.
Every new item starts ticked. Untick the ones you do not want, or click Clear all and pick.Click Update Template.
Items are matched the same way applying matches them: by name, or by key for a custom field.
A template holds at most 500 items. If a refresh would take it past that, the preview says so and the refresh is refused; pick fewer items, or split them across two templates.
Refreshing changes the template, never a tenant
Every refresh that changes the template is recorded in the audit log of the tenant it read from.
Apply a template to tenants
Open the template and click Apply to Tenants.
Tick the tenants to apply it to.
Select all picks every tenant you can change; tenants where you have read-only access are listed but cannot be selected.Click Apply Template, or Apply to N Tenants when you picked more than one.
The result shows what was created and skipped in each tenant, with any warnings.
Applying only ever creates. An item whose name already exists in a tenant (or key, for a custom field) is skipped and left exactly as it was, so you can apply the same template again safely to pick up items added since. Every apply is recorded in each tenant's audit log.
Apply in the right order
Custom fields, groups and scripts refer to each other by key and by name, so apply them in this order when a new tenant needs all three:
Custom Fields first.
A group rule such ascustom:edr_type equals Defenderneeds the field to exist, and a group whose rules use a missing field is skipped with a warning.Groups next.
Rule groups fill themselves from each tenant's devices straight away; groups with manual membership arrive empty.Scripts last.
A schedule is recreated against the groups of the same names in the target tenant. If none of its target groups exist there, the script is created without its schedule; if an excluded group is missing, the schedule is left out rather than run on devices you meant to exclude.
Apps and policies do not depend on the others, since their assignments are not part of a template.
Good to know
- Scheduled scripts start running
- A daily, weekly, or Days and time schedule keeps the enabled or paused state it had when captured, and an enabled one runs on its targets in each tenant on the next scheduler pass, exactly as if you had created it there. A run-once schedule that already ran in the tenant you captured from is applied enabled, so it runs once in each tenant. One you paused before it ever ran stays paused. Collector scripts run on every Windows device on their interval, as always.
- One schedule per script
- Only a script's first (oldest) schedule is captured. A Days and time schedule is applied only to PowerShell scripts; on any other script it is left out with a warning.
- Keep names consistent
- Because skipping goes by name, an item you created by hand in one tenant under a different name will be created a second time from the template.
- Tenant limits still apply
- If a tenant reaches its limit for apps, policies, groups, scripts or custom fields part-way through, the remaining items are skipped and the result says so.
- Who can apply
- The Account Owner and MSP Technicians with all tenants can apply a template to any tenant they can change; a tenant where they hold read-only access is listed but cannot be selected. MSP Read Only users see templates but cannot create, change or apply them. If a colleague who should be using templates cannot see them, grant them all tenants, now and in future, from the Users page instead of specific tenants.
- Apps keep their platform
- A macOS app in an app template is created as a macOS app, with its uninstall script from the catalog.
- Older app templates have no pre- or post-install scripts
- An app template saved before templates carried these scripts creates its apps without them. Refresh it from your reference tenant with Update the template’s items first. Applying again does not add scripts to apps a tenant already has, so add those on the app’s page.