Understanding the Jamf + ServiceNow CSD2.0 Integration Challenges
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2025 05:47 AM - edited 08-12-2025 05:50 AM
Over the past few days, while working on the JAMF and ServiceNow integration for CSD2.0, we encountered a significant blocker related to how application data is fetched and the APIs involved. I’m sharing our findings here so others can be aware of the pitfalls and plan their integrations accordingly.
1. The Expected Behaviour vs. Current Reality
Our goal was to have ServiceNow pull all installed applications from JAMF into the Applications(sn_jamf_spoke_application) table as part of the CSD2.0 flow.
However, upon investigation, we found that ServiceNow’s current OOB JAMF integration behaves differently:
What it actually does:
The integration only pulls in applications purchased from the App Store.What it misses:
Applications deployed via JAMF or installed manually on endpoints are not included in the imported data.
2. Why This Happens
We identified that the current ServiceNow JAMF integration design uses the Classic JAMF Pro API and specifically queries an endpoint that returns App Store application data only.
The Fix in Theory
To fetch the full list of installed applications (including those deployed via JAMF), you’d need to query:
JSSResource/computers
…and then iterate through the applications array for each device.
3. The Bigger Problem – API Deprecation
While this change sounds straightforward, there’s a catch:
JAMF has announced that the Classic API will be deprecated in March.
This means that any integration built on Classic API endpoints will soon be unsupported.
4. Why OOB Won’t Cut It
Given these limitations:
ServiceNow’s current OOB JAMF integration logic cannot fetch all installed apps.
Even if we try to extend it using Classic API calls, the solution is short-lived.
For now, the right way forward is a custom solution leveraging JAMF's Modern API.
5. Key Takeaways
Don’t assume OOB JAMF integration covers all application data — it’s App Store apps only.
Custom development is unavoidable if you need full software inventory in ServiceNow from JAMF.
Conclusion:
The JAMF–ServiceNow integration can be powerful, but its current OOB setup is too narrow for full software visibility. With the Classic API’s sunset around the corner, now is the time to re-architect for the Modern API to ensure a future-proof, complete solution.
If this article helps you avoid the same roadblocks, or if you’ve already solved this using the Modern API, I’d love to hear your approach. Let’s share knowledge so we can make these integrations smoother for everyone.
