Windows 10: Does an Entra ID joined device with Windows 11 Home Operating System allowed to login with...

Hi,This device with Windows 11 Home edition has joined Entra ID domain, but it is unable to login with Work or School account instead of a Local account. Can the experts confirm if it is the limitation of this particular edition of Windows or if there is any work around to achieve the same.ThanksThirthaprasad S G

:)

 

Some windows 11 devices shows as Entra ID registered in Intune

Some devices onboarded to Intune with self deploying Autopilot mode, and now they shows as Entra ID registered in Intune and not Entra ID joined. Why these shows Entra ID registered and how to make them appear Entra ID joined.

 

How to get non-domain joined in use systems to be entra joined without having to touch the system?

Hello, this is Emily.

What do you mean exactly by without having to touch each one??

To joine the device to entra AD, first of all, you need to make sure your computer is running Windows Pro edition, If it is Home edition, then you won't be able to add a work account.

If you have Pro, to do so, go to Settings > Accounts > Access Work or School, click on Connect.

Don't sign into your work email yet. Instead, click on "Join this device to Microsoft Entra ID". On the next step, you will be prompted to sign in, then you can sign in.

Once done, restart the computer and you can use "switch user" to sign in using the company email.

 

Issue with Primary DNS Suffix Not Applying in User Driven Entra Join Deployment Profile

Hello,

1. I have an on-premises AD setup.
   
2. Intune Connector and Azure AD Connectors are configured and functioning correctly.
   
3. My requirement is to configure auto-pilot with an Entra Join Profile, enabling users to log in via Entra AD. After-login, users should be able to ping "server1" once connected to the VPN.
   
4. Currently, everything operates as expected, except users cannot ping "server1" directly. Instead, they must use the full domain name "server.mydomain.com" because the Primary DNS Suffix is not applied to the client machines.
   

To address my auto-pilot, I configured a User Driven Entra Join Deployment Profile under Devices -> Enrollment in Intune. The setup seemed to go through without any hitches. However, after a successful enrollment, the local machine did not pick up the Primary DNS Suffix. This is puzzling because I have ensured that the Domain Join configuration within Intune is correctly set up. Additionally, Entra Join shows as "Not Applicable" in the configuration profile.



Has anyone encountered a similar problem or can offer insights into what might be missing or misconfigured? I'm particularly interested in ensuring that users can access "server1" without having to specify the full domain name, implying that the Primary DNS Suffix needs to be applied automatically upon device enrollment.



Any guidance, solutions, or troubleshooting tips would be greatly appreciated.