For the complete documentation index, see llms.txt. This page is also available as Markdown.

Policy Templates

Lists the Intune policy templates saved in CIPP, which are the templates the Deploy Policy button on the policy pages draws from. Templates can be imported from a community repository, captured from an existing tenant, or created by saving a policy from one of the policy list pages. Filter buttons narrow the list to Synced Templates or Custom Templates.

Action Buttons

Browse Catalog

Opens a drawer for adding templates to CIPP, with two sources to choose between.

Community Catalog is the template catalog described in Catalog, narrowed to Intune templates. Templates can be previewed and imported the same way as on that page.

From a Tenant captures an existing policy from one of your tenants as a template. Select a tenant, then search its policies by name or description and import the one you want.

spinner

Filters

Filter
Shows

Synced Templates

Templates that are still linked to a community repository.

Custom Templates

Templates that are not linked to a community repository.

Table Details

Column
Description

Display Name

The name of the template.

Is Synced

Whether the template came from a community repository and is still linked to it. A template that has been edited or cloned is no longer linked and shows as not synced.

Package

The package the template has been tagged with, where one has been assigned. Packages let a standards template pull in a set of templates by tag rather than by naming each one.

Description

The description recorded against the template.

Type

The template type, for example Catalog, Device, Admin, AppProtection or deviceCompliancePolicies. This determines how the policy is written when deployed.

Usage

The standards templates that use this template, and whether each one references it directly or picks it up through its package tag.

Selecting a row opens a flyout listing the standards templates the template is used in, each linking through to that template, followed by the template's own configuration. This is worth checking before deleting a template, since a template in use by a standard will stop that standard applying.

Packages are viewed, renamed and deleted from Template Package Manager.

Table Actions

Action
Description
Bulk Action Available

Edit Template

Opens the template for editing in Edit Template. Only offered for templates that are not synced to a community repository.

Edit Template Name and Description

Changes the template's name and description. Applying this disconnects the template from the community repository it came from, so it will no longer receive updates.

Clone Template

Creates a copy of the template in CIPP. The copy is not linked to a community repository, so it can be edited freely.

Add to package

Tags the template with a package name, so that standards templates referencing that package pick it up. Pick an existing package from the dropdown, or type a new package name.

Remove from package

Removes the package tag from the template.

Save to GitHub

Uploads the template to one of your GitHub repositories, prompting for the repository and a commit message. Only repositories you have write access to are offered. Hidden unless the GitHub integration is enabled.

Delete Template

Deletes the template from CIPP. Policies already deployed from it are unaffected.

More Info

Opens the Extended Info flyout with the full details for the selected row.


Feature Requests / Ideas

We value your feedback and ideas. Please raise any feature requests on GitHub.

Last updated

Was this helpful?