Skip to main content
Solved

Compliance: "Management settings deployment failed"

  • January 22, 2026
  • 6 replies
  • 70 views

Forum|alt.badge.img+4

Hi,

I am experimenting with Compliance in Jamf Pro. I setup CIS lvl 1 monitoring as a start and without any Azure connection. But somehow it keeps giving the error: “Management settings deployment failed”. We run 43 Macbooks, all rolled-out with DEP and correct registered in Jamf (and Protect). Any idea?

Best answer by florent_bailly

Hello there ! 

I had the same issue this week and I may have an answer for you. I worked with the support on this one.
On my side the fail was caused by my scope : 

  • To this day, compliance benchmarks aren’t compatible with smart or static groups that are linked to a Site
  • Make sure your targeted group isn’t linked to any Site. 

Hope this helps. 
Cheers

6 replies

h1431532403240
Forum|alt.badge.img+6

The "Management settings deployment failed" error with Compliance Benchmarks is most likely caused by one of the following requirements not being met:

SSO Authentication Required You must be logged into Jamf Pro using Jamf Account SSO (OIDC authentication) - either with a Jamf ID or your IdP credentials configured in Jamf Account. This is separate from Azure/Intune integration and is mandatory for Compliance Benchmarks to function.

Reference: Compliance Benchmarks Requirements


Forum|alt.badge.img+4
  • Author
  • Contributor
  • January 23, 2026

Hi,

 

thank you for the reply. I was, unfortunately, already aware of that. I had setup SSO a while ago, before setting op Compliance. It did not solve it.


h1431532403240
Forum|alt.badge.img+6

Since you've confirmed SSO is configured and your Jamf Pro + Protect integration is working, but you're still getting "Management settings deployment failed", this is likely a backend service issue that requires Jamf Support investigation.


florent_bailly
Forum|alt.badge.img+4
  • New Contributor
  • Answer
  • January 29, 2026

Hello there ! 

I had the same issue this week and I may have an answer for you. I worked with the support on this one.
On my side the fail was caused by my scope : 

  • To this day, compliance benchmarks aren’t compatible with smart or static groups that are linked to a Site
  • Make sure your targeted group isn’t linked to any Site. 

Hope this helps. 
Cheers


Forum|alt.badge.img+4
  • Author
  • Contributor
  • January 29, 2026

Hi,

it sounded illogical, but it was indeed the solution. Created a new and dedicated static group for it, did not select the site, selected that as target and it worked!

 


florent_bailly
Forum|alt.badge.img+4
  • New Contributor
  • January 29, 2026

Glad I could help :)