Skip to content

Many organisations have now adopted a hybrid modern workplace environment with user identities in on-premises Active Directory (AD), synchronised to Entra ID using Microsoft Entra Connect (formally Azure AD Connect) or Connect cloud sync. Typically devices are hybrid joined, enabling them to sign in to both cloud and on-premises resources too. This gives your users the ability to single sign on (SSO) to your cloud applications.

However, Hybrid join has its issues and complexities. Microsoft now recommend using Entra joined devices where possible1, due to the simplicity of device deployment and management, but how do you achieve this?

A common misunderstanding is that in order to start using Entra joined devices, you need to have made all of your applications cloud-native, or deploy a cloud application proxy, but it might not be that difficult.

What is Microsoft Entra join?

Microsoft Entra join allows devices to be registered directly with Entra ID, providing a unified identity for accessing both cloud and on-premises resources. This approach is suitable for organisations of all sizes and can be used in both cloud-only and hybrid environments. Key benefits include:

Simplified device provisioning

Devices can be enrolled using self-service options like Windows Out of Box Experience (OOBE), bulk enrolment, or Windows Autopilot. Typically Entra join Autopilot provisioning is more simple than Hybrid join.

Enhanced security

Entra ID join supports passwordless authentication methods such as Windows Hello for Business and FIDO2 security keys.

Unified management

Devices can be managed using Mobile Device Management (MDM) tools like Microsoft Intune, ensuring consistent security policies and configurations.

Remove reliance on on-premises servers

As devices connect to Entra ID in the cloud, their configuration comes from an MDM platform such as Intune so you don’t need to rely on Group Policy configuration or other on-premises management tools.

Introducing Entra Connect SSO

Entra Connect SSO enables Entra joined devices to sign on to on-premises resources that rely on Active Directory, for example, printers, file shares, or applications. It does this by synchronising on-premises user and domain information to Entra ID. When the signed on user wants to access an on-premises resource the device:

  1. Sends domain information and user credentials to a discovered Domain Controller to authenticate the user.

  2. Receives a token used to authenticate to the on-premises resource.

Although there are some prerequisites such as ensuring line of sight communication with your domain controllers, functioning DNS, and certain attribute synchronisation, it’s possible that Entra join may just enable you to sign on to the resources your users need without much additional configuration. It really can be that straightforward.

Next steps

Explore the use of Entra join devices

boxxe is able to assist you in exploring the feasibility of using Entra join devices, starting with an assessment against the prerequisites, and the deployment of a Proof of Concept.

With an agreed number of devices for testing, you will be able to assess your current setup and see how Entra join devices can SSO to applications, printers and file shares, or where you may need to make changes to facilitate the use of cloud-native devices.

For further information, reach out to us now: