> 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/tenant/manage/policies-deployed.md). # Policies and Settings Deployed This page shows what a single standards template contains and how each item currently stands against the selected tenant. It is a read-only view built by comparing the template's contents with the tenant's live configuration, broken into Security Standards, Intune Policies and Conditional Access Policies. Two things determine what is shown: the template chosen in the **Template** picker at the top of the page, and the tenant currently selected in CIPP. Each section header carries a count of the items in it, and sections can be collapsed. {% hint style="info" %} Until a template is selected, all three sections are empty. Arriving from a standards template carries the selection through, otherwise choose one from the **Template** picker. {% endhint %} ## Page Actions | Action | Description | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Refresh Data | Re-reads the template, the comparison against the tenant, and the recorded deviations. | | Edit Template | Opens the standards template for editing. | | Run Standard Now | Forces a run of the template outside its normal schedule. You choose which tenant to run against from the tenants the template applies to, with any excluded tenants left out. | ## Status Values The Status column in each section describes how the item stands against the tenant at the time of the last comparison. | Status | Description | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | Deployed | The tenant matches the template, either because the comparison reports the item as compliant or because the expected and current values are identical. | | Not Deployed | The comparison reports the item as not applied to the tenant. | | Deviation - New | A difference has been found that has not yet been reviewed. | | Deviation - \ | A difference recorded against the tenant, shown with its current review status. Deviations are reviewed on drift.md. | | Not Configured | No comparison data exists for the item, usually because the template has not yet run against this tenant. | ## Security Standards Every item in the template other than Intune and Conditional Access templates. | Column | Description | | ------------- | -------------------------------------------------------------------------------------------- | | Name | The standard's display name, taken from the standards list. | | Category | Always Security Standard in this section. | | Status | How the standard stands against the tenant. See Status Values above. | | Last Modified | The date the comparison data for this standard was last refreshed, or N/A where none exists. | ## Intune Policies The Intune templates included in the standards template. A template brought in through a tag has the tag's name appended to it, shown as the template name followed by the tag in brackets. | Column | Description | | --------------- | ----------------------------------------------------------------------------------------------------------- | | Name | The Intune template's display name. Where the template came from a tag, the tag name is shown alongside it. | | Category | Always Intune Template in this section. | | Platform | Always Multi-Platform in this section. | | Status | How the template stands against the tenant. See Status Values above. | | Last Modified | The date the comparison data for this template was last refreshed, or N/A where none exists. | | Assigned Groups | The assignment configured on the template in the standard, or N/A where none is set. | ## Conditional Access Policies The Conditional Access templates included in the standards template, with the same tag handling as Intune templates. | Column | Description | | ------------- | ------------------------------------------------------------------------------------------------------------------------------- | | Name | The Conditional Access template's display name. Where the template came from a tag, the tag name is shown alongside it. | | State | The state configured on the template, for example enabled or report-only. Shows Unknown where the template does not record one. | | Status | How the template stands against the tenant. See Status Values above. | | Conditions | Always Conditional Access Policy in this section. | | Controls | Always Access Control in this section. | | Last Modified | The date the comparison data for this template was last refreshed, or N/A where none exists. | *** ## 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cipp.app/user-documentation/tenant/manage/policies-deployed.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.