Hi everyone,
We’re currently using Jamf School to manage our Apple devices and are running into issues with Microsoft’s enforcement of strong certificate mapping as outlined in KB5014754.
Our environment relies on certificate-based authentication with Active Directory. While we’ve configured UPN mapping using the RFC 822 SAN field, our domain controllers (now in Full Enforcement mode) are rejecting certificates that don’t meet the new strong mapping requirements.
Unfortunately, Jamf School doesn’t appear to support:
- Inclusion of SAN URIs with SID
- Custom certificate templates
- Scripting or automation for explicit mapping via
altSecurityIdentities
We’ve temporarily enabled Compatibility Mode on our domain controllers, but this is only viable until 10 September 2025, when Microsoft will enforce Full Enforcement by default.
Questions for the community and Jamf staff:
- Are there any confirmed plans for Jamf School to support strong certificate mapping before the enforcement deadline?
- Has anyone found a reliable workaround using Jamf School?
- If not, what’s the best path forward—migrating to Jamf Pro, or using an external certificate issuance workflow?
Any insights or official guidance would be hugely appreciated!