Microsoft Entra ID Importer Versions

Microsoft Entra ID 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.0.0

Major

Simplified Setup with Optional Configurations

We’ve made it easier than ever to get started!

  • No user email required when the connection is not external.

  • No Jira access token needed for non-external connections.

  • Enjoy a smoother onboarding flow and quicker access to core functionality.

Enhanced Import History Visualization

The Import History view now includes new interactive graph features for clearer insights:

  • Toggle between Full and Test Import data for comparison.

  • Show or hide specific metrics dynamically in the graph.

  • Improved data filtering and display options for a cleaner, more flexible analysis experience.

Improved Status Indicators

Visual clarity at a glance in import history:

  • Green checkmark for completed imports.

  • Red cross for failed imports.

  • Orange indicator for imports in progress.

5.7.0

Major

Device Import from Entra ID

You can now import devices directly from Entra ID.
(Note: You’ll need to upgrade your schema and grant permission to read devices in Entra ID.)

Enterprise Applications Import

Added support for importing Enterprise Applications, enabling richer visibility into your organization’s identity landscape.

Expanded Attribute Mapping

Most objects — such as Departments, Cities, and others — now include corresponding attributes, improving data consistency and query capabilities.

Bug Fix: Extension Attributes

Fixed an issue with extension attributes. The importer now supports up to 999 applications without error.

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

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:

  1. Choose the desired Azure environment (US Government or Global Service).

  2. The platform will automatically use the correct Graph endpoint.

This ensures seamless authentication and data access across both environments.