Is there any impact on users (maybe user profile, apps, etc) if I configure the laptops to be Entra Hybrid Joined.

Yes—there can be user impact, but it is usually limited and depends on the current device state and Windows version.

In the current scenario, the laptops are domain-joined and already show as Microsoft Entra registered. After enabling Microsoft Entra hybrid join, the same device can temporarily appear in two states:

• Microsoft Entra registered
• Microsoft Entra hybrid joined

This dual state is expected when users previously added their work account on a domain-joined device. In most cases, Microsoft Entra hybrid join takes precedence for authentication and Conditional Access.

Possible user impact:

1. Access or sign-in evaluation issues can occur during dual state
   • Microsoft documents that this can sometimes cause nondeterministic device evaluation and access issues.
   • On Windows 10 version 1803 and later, Windows automatically cleans up the Microsoft Entra registered state.
2. Cleanup is user-by-user
   • The old Microsoft Entra registered state is automatically removed only after the device is hybrid joined and that same user signs in.
   • If multiple users use the same laptop, cleanup happens separately for each user.
3. MDM/Intune enrollment can be affected if it came from the registered state
   • If an admin manually removes the Microsoft Entra registered state, Windows 10 will unenroll the device from Intune or other MDM if that enrollment happened through the original Microsoft Entra registration via autoenrollment.
   • This is the main area where app/policy impact can happen, because device management and delivered apps/policies may depend on that enrollment.
4. Windows Hello for Business may need reconfiguration in a specific case
   • On Windows 10 1803, if Windows Hello for Business is configured, users need to reconfigure Windows Hello for Business after dual state cleanup. This issue is addressed with KB4512509.
5. Network dependency remains for hybrid joined devices
   • Hybrid joined devices require periodic network line of sight to on-premises domain controllers.
   • They also require line of sight to domain controllers for initial sign-in and device management. If they cannot connect, users might be prevented from signing in and may not receive policy updates.

What usually does not happen based on the provided information:

• No documented indication that simply moving from registered to hybrid joined automatically deletes the user profile.
• No documented indication that local AD domain join is removed by enabling hybrid join.

Practical expectation for the described environment:

• For most users, the transition should be low impact.
• The main risks are:
  • temporary duplicate device records
  • Conditional Access or SSO issues during dual state
  • possible MDM/Intune unenrollment if the registered state is manually removed
  • Windows Hello for Business reconfiguration in the specific Windows 10 1803 case

If minimizing user impact is the goal, the safest approach is to let Windows perform the automatic cleanup on supported versions instead of manually removing the registered state unless there is a specific reason to do so.

• Microsoft Entra device management FAQ
• Microsoft Entra hybrid joined devices
• Microsoft Entra joined vs. Hybrid Microsoft Entra joined in cloud-native endpoints
• Plan your Microsoft Entra hybrid join implementation