{"id":75088,"date":"2023-06-05T13:09:04","date_gmt":"2023-06-05T17:09:04","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=support&p=75088"},"modified":"2024-03-26T14:00:07","modified_gmt":"2024-03-26T18:00:07","slug":"jumpcloud-agent-support-for-on-premise-active-directory-and-azure-active-directory-joined-windows-devices","status":"publish","type":"support","link":"https:\/\/jumpcloud.com\/support\/jumpcloud-agent-support-for-on-premise-active-directory-and-azure-active-directory-joined-windows-devices","title":{"rendered":"Agent Support for On-Premise Active Directory and Entra ID Joined Windows Devices"},"content":{"rendered":"\n
If your organization has on-premise Active Directory (AD) or Entra ID joined Windows devices, you can install the JumpCloud agent on those devices and bring them into your JumpCloud org. Doing so enables the administrator to remotely and securely manage the device as well as take advantage of JumpCloud\u2019s System Insights feature. <\/p>\n\n\n\n
Currently, if you bind users to an on-premise Active Directory domain joined device, the device will ignore the binding and you will be unable to verify your identity on the device. However, if the device leaves the domain, the JumpCloud agent will automatically bind the user to the device. <\/p>\n\n\n\n
<\/p><\/div>
If a JumpCloud-managed device with JumpCloud users bound to it joins an on-premise AD domain, those user accounts will be suspended. This is expected behavior as user management is not supported on on-premise AD domain-joined devices. <\/p>\n\n\n\n
<\/p>\n\n\n\n
If you attempt to bind an Entra ID imported user to an Entra ID joined device, this may result in unexpected behavior.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
The table below shows the features that are supported on JumpCloud devices, Active Directory devices, and Entra ID devices:<\/p>\n\n\n\n