> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/endpoint/mem/list-policies.md).

# Configuration Policies

Lists the configuration policies on the selected tenant, showing what type each policy is and who it is assigned to. Selecting a row opens a flyout with the policy's settings, which is useful for reviewing a policy in detail or copying its configuration into another system or script.

## Action Buttons

<details>

<summary>Deploy Policy</summary>

Opens a drawer that applies a saved policy template to one or more tenants.

| Field                              | Description                                                                                                                                                                                                                                                      |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Select Tenants                     | The tenants to deploy to. Several can be selected, and the same template is applied to each.                                                                                                                                                                     |
| Please choose a template to apply. | The policy template to deploy, chosen from those saved in Policy Templates. **Refresh Templates** reloads the list if a template was added since the drawer was opened.                                                                                          |
| Assignment                         | Who the deployed policy is assigned to: Do Not Assign, Assign to All Users, Assign to All Devices, Assign to All Users and Devices, or Assign to Custom Group.                                                                                                   |
| Group(s)                           | Shown when Assign to Custom Group is chosen. With a single tenant selected this is a picker of that tenant's groups. With several tenants or All Tenants it is a text field taking group display names separated by commas, where `*` may be used as a wildcard. |
| Exclude group(s)                   | Shown for every option except Do Not Assign. The same picker or name field as above, for the groups to exclude.                                                                                                                                                  |
| Assignment Filter (Optional)       | An assignment filter from the tenant to narrow which devices the policy applies to.                                                                                                                                                                              |
| Assignment Filter Mode             | Whether the filter includes or excludes matching devices. Shown once a filter is chosen.                                                                                                                                                                         |

The template's configuration is displayed below the picker so it can be checked before deploying.

Group pickers are only offered for a single tenant because a group belongs to one tenant. Picking groups also removes the failure mode of the name field, where a mistyped or renamed exclude group silently matched nothing and the policy was assigned without the exclusion. Changing the tenant selection clears any picked groups.

{% hint style="info" %}
Where the template contains variables written as `%name%`, the drawer asks for a value for each one, per tenant, before it will deploy. `%tenantid%` and `%defaultdomain%` are filled in automatically for each selected tenant.
{% endhint %}

{% hint style="warning" %}
Deploying a template does not always create a new policy. CIPP first looks for a policy in the target tenant whose name exactly matches the template's, and where one is found it overwrites that policy in place. A new policy is only created where no match exists.

Because the match is on the name alone, a policy created by hand under the same name will be overwritten, and a deployed policy that has since been renamed in Intune will not be recognised, so the next deployment creates a duplicate alongside it. Where two policies share a name, the more recently modified one is the one overwritten.

The assignment chosen here is added to the policy's existing assignments rather than replacing them.
{% endhint %}

{% hint style="danger" %}
What an overwrite does to settings the template does not mention depends on the policy type.

For Settings Catalog and Administrative Templates this means any change made directly in the Microsoft Intune admin center since the template was captured is lost on the next deployment.
{% endhint %}

| Policy type              | Settings not present in the template                                                          |
| ------------------------ | --------------------------------------------------------------------------------------------- |
| Settings Catalog         | Removed. The policy's settings become exactly what the template holds.                        |
| Administrative Templates | Removed. Every configured setting on the policy is cleared before the template's are applied. |
| All other types          | Left as they are. The template's settings are merged over the existing ones.                  |

{% hint style="info" %}
An Administrative Templates policy built on an imported ADMX file (for example a browser vendor's templates) can be deployed to any tenant where the same ADMX and ADML files have been imported. Intune gives an imported setting a different identifier in every tenant, so CIPP matches each setting by its name, category and class rather than by identifier. Where the ADMX has not been imported into a target tenant, the deployment stops and names the settings it could not find; import the files under Devices > Configuration > Import ADMX in that tenant, wait until they show as Available, and deploy again.
{% endhint %}

</details>

## Table Details

| Column                  | Description                                                                                                                                     |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Display Name            | The name of the policy.                                                                                                                         |
| Policy Type Name        | The kind of policy, for example Device Configuration, Administrative Templates, Compliance Policy or Endpoint Security.                         |
| Policy Assignment       | The groups and broad targets the policy is assigned to. All Devices, All Users and All Licenced Users appear here where those targets are used. |
| Policy Exclude          | The groups and broad targets excluded from the policy.                                                                                          |
| Description             | The description recorded against the policy.                                                                                                    |
| Last Modified Date Time | When the policy was last changed.                                                                                                               |

{% hint style="info" %}
The flyout for a Settings Catalog or Administrative Templates policy fetches the policy's settings along with Microsoft's own descriptions for each one, so the settings read as names rather than identifiers. This takes a moment to load, and other policy types show their stored details without the extra lookup.
{% endhint %}

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th width="250" data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Create template based on policy</td><td>Creates a policy template based on the selected policy(ies)</td><td>true</td></tr><tr><td>Edit Name &#x26; Description</td><td>Allows you to edit the name and description of the selected policy(ies)</td><td>true</td></tr><tr><td>Clone Policy</td><td>Creates a clone of the selected policy(ies) with the ability to set a new name and description</td><td>true</td></tr><tr><td>Assign to All Users</td><td>Assigns the policy(ies) to all users, with optional exclusion groups and an optional assignment filter</td><td>true</td></tr><tr><td>Assign to All Devices</td><td>Assigns the policy(ies) to all devices, with optional exclusion groups and an optional assignment filter</td><td>true</td></tr><tr><td>Assign Globally (All Users / All Devices)</td><td>Assigns the policy(ies) to all users and all devices, with optional exclusion groups and an optional assignment filter</td><td>true</td></tr><tr><td>Assign to Custom Group</td><td>Assigns the policy(ies) to a custom group from the tenant. Options are to include or exclude the group and replace or append to existing assignments. You can also apply an existing assignment filter to further restrict assignment.</td><td>true</td></tr><tr><td>Delete Policy</td><td>Deletes the selected policy(ies)</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout</td><td>false</td></tr></tbody></table>

## Deployment Status

The **More Info** flyout begins with a **Deployment Status** section, showing how the policy has deployed in the same way as the Device status and User status pages in the Microsoft Intune admin center. The section has a **Devices** tab and a **Users** tab, each labelled with its number of rows, and above the table a chip for each status counts how many rows are in it. The policy's own settings follow below the section.

**Devices**

| Column              | Description                                                                                         |
| ------------------- | --------------------------------------------------------------------------------------------------- |
| Device Name         | The name of the device.                                                                             |
| User Principal Name | The user associated with the device's status.                                                       |
| Status              | The result of applying the policy on the device, for example succeeded, error, conflict or pending. |
| Status Detail       | Not used for configuration policies.                                                                |
| Platform            | The device's platform. For device configuration profiles, the device's model.                       |
| Last Reported       | When the device last reported its status.                                                           |

**Users**

| Column              | Description                                                                      |
| ------------------- | -------------------------------------------------------------------------------- |
| User Principal Name | The user's sign-in name.                                                         |
| User Name           | The user's display name.                                                         |
| Status              | The policy's status for the user.                                                |
| Status Detail       | Not used for configuration policies.                                             |
| Device Count        | The number of the user's devices the status covers.                              |
| Last Reported       | When the user's status was last reported. Empty where Intune does not report it. |

For settings catalog policies, administrative templates and endpoint security policies, Intune reports devices only, so the **Users** tab is built from the device rows: one row per user, carrying the worst status across that user's devices. Devices with no user are grouped into a single row named **No user**. For device configuration profiles, a user row with no user principal name is Intune's system account, which covers device-targeted check-ins.

{% hint style="info" %}
Windows feature, quality and driver update profiles and hardware configurations have no per-device status in Intune, so their flyout says that Intune has no deployment status for this type.
{% endhint %}

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cipp.app/user-documentation/endpoint/mem/list-policies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
