
What you’ll accomplish
- Set up API access in Jamf Pro
- Configure the June integration
- Understand data synchronization
- Troubleshoot common issues
Prerequisites
Before starting the integration, ensure you have:- Jamf Pro administrator access
- API access enabled in Jamf Pro
- Network connectivity between June and Jamf Pro server
- June organization admin permissions
Setup Process
Step 1: Create API Account in Jamf Pro
1
Setting up API role
- Log into your Jamf Pro server
- Navigate to Settings > System > API roles and clients
- Go to the API roles tab and click the ”+” button to create a new API role
- Set the API role name to “June Integration”
- Assign the following permissions:
Read ComputersUpdate ComputersRead Mobile DevicesRead UsersRead DepartmentsRead BuildingsRead Mobile Device ApplicationsRead Mac Applications
- Click “Save”
2
Setting up API client
- Go to the API clients tab and click the ”+” button to create a new API client
- Set the API client name to “June Integration API Client”
- Select the API role you created in the previous step
- Set the access lifetime token to 60 (default value)
- Click on the “Enable API client” button
- Click “Save”
- Generate the API client secret by clicking on the “Generate” button
- Note the client ID and client secret for June configuration which we will use in the next step.
Step 2: Add Integration in June
1
Access Integrations
- Log into June
- Navigate to Integrations page
- Choose “Jamf Pro” from the available integrations
2
Configure Jamf Pro
- Enter the Jamf Pro server URL
- Provide the following information:
- Jamf Pro Server URL: Your Jamf Pro server URL (e.g.,
https://yourcompany.jamfcloud.com) - Client ID: Client ID from the API account created in Step 1
- Client Secret: Client Secret from the API account created in Step 1
- Sync Frequency: How often June should sync with Jamf Pro. Default is daily.
- Click “Save”
- You should see whether you are successfully connected to Jamf Pro.
3
Test Connection
- Click “Test Connection” to verify the setup from the dropdown option.
- June will attempt to connect and retrieve a sample of data
- Resolve any connection issues before proceeding
4
Kick off the sync
- Click “Sync Now” option from the dropdown to sync your data.
- June will start syncing your data.
- You should see the sync progress in the “Sync Status” column.
- You should start to see assets getting populated in June in a few minutes.
Step 4: Configure Sync Settings
1
Set Sync Frequency
Choose how often June should sync with Jamf Pro:
- Every day: Recommended for most environments
- Every other day: For larger environments or limited bandwidth
- Weekly: For environments with fewer changes
2
Choose Data to Sync
Select which device attributes to synchronize:
- Device Data (Always included)
- Employee Data
- Location Data (office location data)
- Installed Software applications
- Purchase Data
- Device Actions (Restart, Lock, Wipe, etc.)
Data Synchronization
What Gets Synced
| Data Type | Jamf Pro Source | June Destination | Notes |
|---|---|---|---|
| Device Identity | Computer Name, Serial Number | Device Name, Asset Tag | Primary device identification |
| Hardware Info | Model, Processor, Memory, Storage | Hardware Specifications | Complete hardware inventory |
| Software | Operating System, Software Applications | System Info, App Inventory | OS version and installed apps |
| User Assignment | User and Location fields | Employee Assignment | Links devices to users |
| Compliance | Last Inventory, Check-in Status | Health Status | Device connectivity and compliance |
| Department Data | Device assignment to departments | Department and Location | Organizational groupings |
| Purchase Data | Purchase Date, Warranty Info, Cost Center, Asset Tag | Asset Purchase Date, Warranty Expiration, Department Cost Center, Physical Asset Tag | Purchase data for assets |
Sync Process
- Initial Sync: Complete inventory sync on first connection
- Incremental Updates: We pull the latest data from Jamf Pro every day and also sync the data for individual devices that have been updated in the last 24 hours.
- Conflict Resolution: June handles data conflicts automatically
- Error Handling: Failed syncs are retried with exponential backoff
- Integration Health: We monitor the health of the integration and alert you if there are any issues.
Troubleshooting
Common Connection Issues
Authentication Failures
Authentication Failures
Symptoms: “Invalid credentials” or “Authentication failed” errorsSolutions:
- Verify API account username and password
- Ensure the account hasn’t been disabled
- Check if password has expired
- Confirm API access is enabled for the account
- Click on the “Test Connection” button to verify the connection.
Network Connectivity
Network Connectivity
Symptoms: Connection timeouts or “Unable to reach server” errorsSolutions:
- Verify Jamf Pro server URL is correct and accessible
- Check firewall rules allow June’s IP addresses
- Ensure SSL certificate is valid (for HTTPS connections)
- Test connectivity from June’s network to Jamf Pro
- Click on the “Test Connection” button to verify the connection.
Permission Errors
Permission Errors
Symptoms: “Access denied” or “Insufficient privileges” errorsSolutions:
- Review API account permissions in Jamf Pro
- Ensure all required object permissions are granted
- Check if permissions apply to the right scope (All Objects vs. specific categories)
- Verify the account has API access enabled
- Click on the “Test Connection” button to verify the connection.
Sync Issues
Missing Devices
Missing Devices
Possible Causes:
- Devices not enrolled in Jamf Pro
- Devices haven’t checked in recently
- Insufficient permissions to access certain devices
- Verify device enrollment status in Jamf Pro
- Check last inventory date for missing devices
- Confirm API permissions cover all required devices
Outdated Information
Outdated Information
Possible Causes:
- Devices not checking in regularly
- Sync frequency too low
- Network issues preventing updates
- Increase sync frequency if needed
- Force inventory update on devices by clicking on the “Sync Now” button in the integration page.
- Check device connectivity and management status
- Review sync logs for specific error messages
Performance Problems
Performance Problems
Symptoms: Slow syncs, timeouts, high resource usageSolutions:
- Reduce sync frequency during peak hours
- Monitor Jamf Pro server performance during sync windows
- You could be hitting the rate limit of the Jamf Pro API. You could try to increase the sync frequency to reduce the number of devices that are synced.
Best Practices
Security
- Regular API credentials rotation: Change API account credentials regularly
- Least Privilege: Grant only necessary permissions to the API account
- Monitor Access: Review API access logs regularly
- Secure Storage: June encrypts the API credentials before storing them in our database.
Performance
- Optimal Sync Frequency: Balance data freshness with server load
- Smart Filtering: Use device filters to reduce sync overhead
- Off-Hours Syncing: Schedule heavy syncs during low-usage periods
- Monitor Resources: Watch server performance during sync operations
Maintenance
- Regular Testing: Periodically test the integration connection
- Update Management: Keep Jamf Pro and June integrations updated
- Documentation: Maintain documentation of custom configurations
- Backup Configuration: Document integration settings for disaster recovery
Next Steps
Once your Jamf Pro integration is configured:Identity Provider Setup
Connect your identity provider for complete user correlation
Device Management
Start managing your synced Mac devices with June’s features
Custom Views
Create Mac-specific views and searches
Compliance Monitoring
Set up Mac-specific compliance monitoring
Support
Need help with your Jamf Pro integration?- Documentation: Review Jamf Pro API documentation
- Community: Join the June community forum
- Support: Contact June support with integration issues
- Professional Services: Consider professional setup assistance for complex environments
Jamf Pro integration typically syncs data within 15-30 minutes of initial setup. Large environments may take longer for the initial sync to complete.