You have assigned a configuration from your management tool, but the Mac is not behaving as expected. An MDM policy on Mac that does not apply does not necessarily point to one cause: the issue could involve enrolment, communication, assignment scope or the requirements of the setting.
Rather than trying random changes, separate each stage: what was supposed to be applied, which device or user it was assigned to, what the management service reports and what actually happens on the Mac. This helps narrow down the issue without unnecessarily affecting other devices.
1. Define what you expected from the MDM policy on Mac
Record the policy name, the specific setting and the expected result. A profile that does not appear on the device is a different problem from an installed profile that produces unexpected behaviour. Note when the issue was detected and whether it affects one Mac, a group or other users of the same device.
If possible, compare it with a similar working Mac: macOS version, enrolment method, user and assigned group. A difference is a lead to investigate, not automatic proof of the cause. Also record whether the issue began after a configuration change.
2. Check enrolment and communication
Confirm that the Mac is enrolled in the intended management service and that the console identifies the correct device. Review the latest available information and look for signs that the device has not communicated recently. Check the connectivity required for management too; being able to browse the web does not, by itself, prove that all management communications are working.
If you are looking for a Mac configuration profile, remember that its presence alone does not guarantee that the setting has the intended effect. On the Mac, System Settings > General > Device Management lets you view available management profiles. What appears depends on the macOS version and how the device is managed. Apple describes communication requirements and profiles in its device management guide.
If the MDM policy on Mac still does not apply, do not remove the enrolment profile or re-enrol the device as a first step: assess the impact and follow your organisation's authorised procedure.
3. Review the scope and requirements of the MDM policy on Mac
Check in the management tool that the policy is assigned to the correct device or user and that it meets the conditions for receiving it. Review recent group changes, exclusions and any conditions that could affect assignment. If the console shows a status or error, record the full text and when it was observed.
Next, check the specific macOS setting against the operating system version and enrolment method. Some settings require supervision or other conditions, and not every option is available in every management service. Apple's list of device management payloads for Mac helps you check the requirements for each case.
4. Look for configurations that may interfere
Check whether other profiles or policies affect the same setting as the MDM policy on Mac. Compare the settings of the Mac configuration profile with other assigned profiles. Not all conflicts are resolved in the same way: it depends on the configuration. For example, Apple says that when a Mac receives multiple PPPC privacy configurations, the more restrictive settings apply. Do not assume that rule applies to every policy.
Before changing or removing a profile, identify who else it affects and which security controls it could change. If the impact is unclear, document the possible interference and escalate it instead of disabling protections for a quick test.
5. Run a limited test and retain the evidence
Once you have a hypothesis about the MDM policy on Mac, agree on a test using a representative pilot device. Change one condition at a time, record the previous state and define how to check the result and return to the previous configuration if the change does not work. The available recovery options depend on the setting and tool.
- Identification: affected device, macOS version, enrolment method and user or group involved.
- Policy: expected setting, scope, conditions and recent changes.
- Result: time of the check, observed status, exact message and difference from the expected result.
- Test: hypothesis, authorised change, result and next person responsible.
Share only the information needed with authorised people. Avoid including passwords, recovery keys or unnecessary personal data in screenshots and logs.
When to escalate the issue
Escalate the case if it affects several devices, compromises a security configuration, you cannot safely identify the scope of a change or the pilot test does not clarify the problem. Give the evidence and the steps already taken to the responsible administrator or the management tool's support team. If you suspect a security incident, follow your organisation's response procedure.
For more context on managing Apple devices, read our article on managing macOS environments with Mosyle.
An organised diagnosis reduces unnecessary changes
When an MDM policy on Mac does not apply, check its assignment, the device's status and the requirements of the setting. Recording observations and testing limited changes helps guide the diagnosis without assuming that every Mac, profile or tool behaves the same way.
Discover our Apple for business service