Before
IT staff likely had to track new Jamf enrollments, search for each device in CrowdStrike, and revisit devices that were not immediately visible. They also had to manually post enrollment, success, or failure updates to the team, creating repeated checks and delayed handoffs.
How it works
- A Jamf enrollment starts the workflow, which announces the new device in the designated Slack channel.
- The workflow checks CrowdStrike repeatedly at one-minute intervals and evaluates whether the device has been recognized, while tracking whether the team has already been notified.
- It posts a success update when the device is found or sends an unresolved-installation alert to IT when the device remains undetected for the configured monitoring period.
Workflow details
- Enrollment notification: When a new device is registered in Jamf, the workflow captures its device identifier and posts an enrollment notification to a designated Slack channel.
- Recognition monitoring: The automation checks whether the device appears in CrowdStrike, repeating the check once per minute while preventing duplicate team notifications.
- Successful verification: When CrowdStrike recognizes the device, the workflow marks the notification state and posts a success update for the device.
- Unresolved enrollment: If the device is still not detected after the monitoring period described in the workflow, the automation posts a failure message notifying the IT team that CrowdStrike has not been installed or recognized.
- Operational handoff: The result is delivered through Slack so the team can distinguish a completed security enrollment from a device requiring follow-up.
What changed
Device enrollment status is now announced immediately, CrowdStrike recognition checks run automatically, and the team receives a Slack update based on the result. Human staff only need to follow up when the automated monitoring reports that the device remains unrecognized.
Work removed
Manually reviewing new Jamf enrollments, searching CrowdStrike for each device, repeating checks every minute, tracking whether the team was already notified, and composing separate Slack success or failure messages.
Expected outcome
Up to approximately 60 recurring device checks can be automated during a one-hour monitoring window, with enrollment status and exceptions communicated to IT through Slack.
