Microsoft Intune Importer Versions

Starting from August 2025, we are introducing this page to inform our users bout major or important app changes.

Version	Type	Change

Version	Type	Change
6.15.0	MAJOR	New in Version 6.15.0 – Microsoft Endpoint Analytics Support Import Microsoft Endpoint Analytics data directly into JSM Assets. Each device now gets a dedicated Endpoint Analytics object type linked to its Managed Device, populated with scores and performance metrics from two Microsoft Graph endpoints. Scores (userExperienceAnalyticsDeviceScores) Endpoint Analytics Score Startup Performance Score App Reliability Score Battery Health Score Work From Anywhere Score Health Status Performance (userExperienceAnalyticsDevicePerformance) Startup Score Core Boot Score Core Sign-in Score Restart Count Blue Screen Count Disk Type How to enable: Go to Connection → Actions → Objects and toggle on Endpoint Analytics, then rebuild your schema and run an import. Note: Requires the `DeviceManagementManagedDevices.Read.All` permission in Azure AD and an Endpoint Analytics license in your Microsoft tenant.
6.13.0	MAJOR	New in Version 6.13.0 – Dashboard, Insights & Automation Enhancements Dashboard Landing Page New Dashboard tab replaces the static Introduction when connections exist – your first view is now actionable intelligence. Overview section with total connections, active count, sources, destinations, and import success/failure counts. Per-connection cards with Summary/Full view toggle for quick scanning or detailed analysis. Refresh button to reload all dashboard data on demand. Last Import Section Imported object counts moved above compliance data with a new "Last Import" heading. Duration card shows the time taken for the last completed import. Selectable metric cards – click Duration for a bar chart, OS Types for a donut chart, or any imported object to see its count trend over time as a line chart. Interactive Compliance & Security Trends Compliance & Risk metrics (Devices, Compliant, Non-Compliant, High/Medium/Low Risk) are now clickable – select any metric to see its trend over time. Security Posture metrics (Encrypted, Not Encrypted, AAD Registered, Jailbroken) also support trend graph selection. Trend data is built from the full summary history, giving you visibility into how your fleet health changes across imports. Auto-Create Jira Issues for Non-Compliant Devices Automatically create a Jira issue when non-compliant devices exceed a configurable threshold after each import. Smart deduplication: updates existing open issues with comments instead of creating duplicates. Configurable project, issue type, assignee, threshold, and cooldown period. Issues include compliance summary, top 10 risky devices with risk scores, issue breakdown, and direct links to JSM Assets.
6.12.0	MINOR	Enhanced Audit Log Security Improved the security of audit logging to prevent potential user impersonation. The system now ensures that all audit and debug log entries are authenticated using server-side verification, making the logs more reliable and trustworthy for compliance and troubleshooting purposes.
6.0.0	MAJOR	New in Version 6.0.0 Now we support local and external connections. Local connections doesn’t need email and Jira connection token anymore.
5.0.0	MAJOR	New in Version 5.0.0 – Azure Environment Support With this release, we’ve expanded compatibility to support multiple Azure environments, giving users greater flexibility and compliance options. What’s New Azure US Government – Now fully supported via http://graph.microsoft.us Azure Global Service – Standard support via http://graph.microsoft.com Why This Matters Many organizations operate in specialized Azure environments due to regulatory, compliance, or security requirements. By adding support for Azure US Government, customers in sensitive sectors (such as government, defense, and contractors) can securely integrate without workarounds. How to Use It When configuring your Azure connection: Choose the desired Azure environment (US Government or Global Service). The platform will automatically use the correct Graph endpoint. http://graph.microsoft.us for the US Government http://graph.microsoft.com for Global Service This ensures seamless authentication and data access across both environments.