> For the complete documentation index, see [llms.txt](https://docs.intunemacadmins.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intunemacadmins.com/complete-guide-macos-deployment/custom-compliance-settings.md).

# Custom Compliance Settings for macOS

Define custom compliance checks for macOS in Intune using scripts and JSON rules.

Microsoft Intune supports custom compliance settings for macOS. As an admin, you can define compliance checks using scripts and JSON rules, similar to the existing support for Windows and Linux.

## What custom compliance enables

This capability lets you evaluate device configuration, security posture, and other custom attributes that are not covered by the built-in compliance settings. You author a discovery script that returns values from the Mac, then define JSON rules that specify the expected values used to determine compliance.

## Reporting

Results from custom compliance checks appear alongside standard compliance reporting in the Intune admin center, so administrators can monitor them together with built-in compliance settings.

Learn more: [Microsoft Intune release notes](https://learn.microsoft.com/en-us/intune/whats-new/#custom-compliance-settings-for-macos)


---

# 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.intunemacadmins.com/complete-guide-macos-deployment/custom-compliance-settings.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.