Automations

The Microsoft Intune Importer for JSM Assets provides three powerful automation features to help you stay on top of your device fleet health without manual effort.

Automatically import your Intune device data into JSM Assets on a recurring schedule — no manual action needed.

• The app runs a hourly scheduled trigger that checks all configured connections

• Each connection can have one or more scheduled hours configured

• When the current hour matches a connection's schedule, the import runs automatically

• Import results (success or failure) are logged and available in the app

1. Navigate to the Import Settings tab for your connection

2. Select the hours you want the import to run (e.g., every 6 hours: 00:00, 06:00, 12:00, 18:00)

3. Save your settings

4. The next matching hour will trigger an automatic import

• The app fetches the latest device data from Microsoft Intune

• Data is synchronized into your JSM Assets object schema

• Compliance summaries, risk scores, and anomaly detection run automatically

• If Automation Notifications are configured, errors trigger a webhook notification

• If Auto-Issue Creation is enabled, compliance thresholds are checked

Get notified automatically when scheduled imports encounter errors by connecting a Jira Cloud Automation rule with a webhook trigger.

• You create a Jira Cloud Automation rule with an Incoming Webhook trigger

• You provide the webhook URL and secret in the app settings

• When a scheduled import fails, the app sends a notification to your webhook

• Your automation rule can then create issues, send emails, post to Slack, or any other Jira Automation action

1. Create a Jira Automation Rule:

   • Go to Project Settings → Automation (or global automation)

   • Create a new rule with the trigger Incoming Webhook

   • Copy the webhook URL and note the secret

2. Configure in the App:

   • Navigate to the Automations section in the app

   • Click Set Automation Notification

   • Enter the Automation URL (the webhook URL from your Jira rule)

   • Enter the Secret (must match the secret configured in your Jira rule)

   • Click Save & Test — a test message will be sent to verify the connection

3. Test the Connection:

   • The app sends a test message when you save

   • If successful, you'll see a confirmation message

   • If the URL is invalid, an error will be displayed (the URL is still saved so you can fix it)

The webhook sends a JSON payload with the following structure:

• Create a Jira issue when an import fails

• Send a Slack notification to your IT team

• Send an email to the admin team

• Trigger a remediation workflow in another system

For detailed instructions on creating Automation Rules, see the Notifications documentation page.

Automatically create Jira issues when the number of non-compliant devices exceeds a configured threshold after each import. This helps your team stay on top of compliance issues and take action quickly.

• After each import, the app checks the number of non-compliant devices

• If the count exceeds your configured threshold, a Jira issue is automatically created

• The issue includes a comprehensive compliance report with device details, risk scores, and recommended actions

• Smart deduplication prevents duplicate issues from flooding your project

Each auto-created Jira issue contains:

• Compliance Summary — Total devices, compliant count, non-compliant count, unknown status

• Top 10 Highest Risk Devices — Device name (linked to Assets if available), risk score, risk level, and specific issues detected

• Issue Breakdown — Count of each issue type (Not Encrypted, Not AAD Registered, Jailbroken, etc.)

• Risk Distribution — Number of devices at High, Medium, and Low risk levels

• Risk Score Calculation — Explanation of how risk scores are computed

• Recommended Actions — Steps to investigate and remediate compliance issues

• Links to JSM Assets — Direct links to your Assets schema and import history

Each device is assigned a risk score based on the following weighted factors:

Risk Levels: High (≥40 points) · Medium (15–39 points) · Low (<15 points)

1. Navigate to the Automations section in the app

2. Click Configure Auto-Issue Creation

3. Toggle Enable Auto-Issue Creation on

4. Set your Non-Compliant Device Threshold (e.g., 10)

5. Select a Target Jira Project from the dropdown

6. Select an Issue Type (e.g., Task, Bug)

7. Optionally select an Assignee

8. Choose your preferred Duplicate Handling mode

9. Click Save Settings

When using Smart mode (recommended):

1. First breach: A new Jira issue is created with full compliance details

2. Subsequent imports (issue still open): A comment is added to the existing issue with updated compliance data and timestamp

3. Issue resolved by team: The next threshold breach creates a fresh new issue

4. If assignee is unavailable: The issue is created without an assignee (no failure)

1. Start with scheduled imports — Set up at least one daily import to keep your data current

2. Enable notifications — Connect a webhook to get alerted about import failures

3. Set realistic thresholds — Start with a higher threshold for auto-issues and lower it as your compliance improves

4. Use Smart deduplication — Prevents issue fatigue while keeping your team informed

5. Assign a team member — Having a default assignee ensures issues don't get lost

6. Review the Dashboard — Use the Dashboard tab to monitor trends and catch issues early