Workplace join not working

Michael 1 Reputation point
2025-04-11T04:54:09.92+00:00

We discovered that after a fresh OSD, some machines aren't enrolled into Intune. The scheduled task isn't active and cannot therefor put the machine in the cloud.

Task Scheduler Library > Microsoft > Windows > Workplace Join

User's image

So the value AzureADJoined = YES (dsregcmd /status) is not set. The settings are good in CM in the Client Settings -> Cloud Services

User's image

We discovered that a setting in registry isn't set to 1:

HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin > autoWorkplaceJoin

So what we tried to do is to put an extra step in the TS in order to set the correct value:

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin /V autoWorkplaceJoin /T REG_DWORD /D 1 /F

Those things are helping a bit but in the end not a solution. Anybody has the same issue ?

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
1,065 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Rahul Jindal [MVP] 10,806 Reputation points MVP
    2025-04-11T09:41:51.9666667+00:00

    I have found that in conjunction to the ConfigMgr client settings, one needs to configure the Entra ID join policy in AD as well. This is of course if you are using targeted hybrid join.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.