Active Directory Integration (ADI) Release Notes 2025

Interested in previous years' release notes? See ADI Release Notes 2023 and ADI Release Notes 2024. Alternately, see JumpCloud's Feature Release Notes.

2025-06-24 ADI Release Notes

This release introduces an important enhancement for agent health status notifications and includes targeted bug fixes for the ADI service to improve stability and data consistency.

ADI Service

Enhancements

• Deactivated Agent Notifications: To prevent unintended service disruptions, JumpCloud will now automatically send an email notification to all administrators in your organization if the last active ADI import or sync agent becomes deactivated. This ensures you can take immediate action if the deactivation was not intentional.

Bug Fixes

• Improved Service Call Efficiency: Resolved an issue where the service would continuously retry failed user creation and user updates for errors that could not be fixed by a retry. The service is now more efficient and will not attempt redundant retries for these types of failures.
• Corrected Password Sync Behavior for New AD Users: Fixed a critical issue where the initial system-generated password for a new AD user was incorrectly syncing back to JumpCloud, overwriting that user's active JumpCloud password. The sync process now correctly handles these initial passwords without impacting the user's existing JumpCloud credentials.

Resolved Data Persistence for Staged Users: Corrected a bug that prevented user information for accounts in a "staged" user state from being saved correctly in the ADI service database. This fix ensures data integrity for all user states within the service.

2025-05-12 ADI Release Notes

ADI Service

Bug Fix

• Addressed a validation failure that occurred when the "Default External Password Authority" was configured as "Active Directory." The validation incorrectly triggered a "SystemUserModel validation error," preventing successful user imports from AD to JumpCloud.

2025-04-09 ADI Release Notes

Admin Portal

Bug Fix

• Addressed an issue that prevented import agents from appearing in the Domain Agents list within the Admin Portal when the DN was entered in uppercase in JumpCloud during the integration setup process.

2025-02-12 ADI Release Notes

AD Import Agent v3.26.0

Bug Fixes

• Addressed an issue preventing some users from being created in JumpCloud due to a username conflict and inability to obtain the required id. The username conflict is now logged as an error and the logic has been updated to utilize id rather than username once a new user is created. 

General Enhancements

• Updated the client configuration defaults to ensure that conflicting values are not defined
• Removed unnecessary values from the client configuration. The server_name is now only required if it differs from the target host
• Minor security and performance enhancements

2025-01-07 ADI Release Notes

AD Import Agent v3.20.0

New Functionality

• Suspended AD users are not created in JumpCloud
• JumpCloud_AD_Import.log includes the user information for failed events
• More of the logs are in JumpCloud_AD_Import_Grpc.log.
  • When troubleshooting review both JumpCloud_AD_Import.log and JumpCloud_AD_Import_Grpc.log
• Any exceptions that result in the JumpCloud AD Integration Import Agent (JCADImportAgent) service restarting will be logged as a windows event and viewable in the Event Viewer

Bug Fixes

• Duplicate users are no longer created in AD when multiple import agents are installed and active and all AD DCs are not yet in sync (replication has not completed)
• Users are no longer immediately deleted after being added to JumpCloud when multiple import agents are installed and active and all AD DCs are not yet in sync (replication has not completed)

ADI Service

• When multiple AD import agents are installed, one is designated as the primary agent by the ADI service for all user, group, and password related actions (directives) performed by the import agent, in addition to the delegated authentication actions. If the primary import agent becomes unavailable, another active import agent is automatically designated as the primary