Forum Discussion
Conditional Access Hybrid Azure AD Joined
The things I would check.
1.) Check the user's Sign-ins log
- to confirm where the issue is at.
2.) On the PC run this command:
DSREGCMD /status
- That will tell you about the state of the PC.
3.) Check for multiple entries in AAD.
Get-AzureADDevice -SearchString <PC name> | Format-List DisplayName, DeviceTrustType, DevicePhysicalIds, DeviceId
- The one that has "ServerAd" for the DeviceTrustType is the object for the Hybrid Join.
- There can be others, like AzureAD, which are the PC being joined more than once.
- If the Hybrid join has completed the DevicePhysicalIds will be populated.
That's where I would start looking.
Steve Mahoney This is for multiple users.
Already performed the steps you've mentioned but all results seems good. I have no clue why it's blocked the status of the PC says that it's Hybrid Azure AD joined. The PC's are all Hybrid Azure AD Joined in Azure AD.
The funny part is that when I review the sign-in logs of Exclaimer cloud, we see sometimes conditional access policy failures because device is not Hybrid Azure AD joined. But we've currently excluded the Exclaimer Cloud application from the policy's.
Jordy Blommaert Maybe not a case for you but I see strange behaviors if the computer for some reason is both Azure AD registered and Hybrid Azure AD Join. This was a problem before a certain version of Windows 10 (I think version 1809). I've also seen problems if the computer was recently domain joined (I guess it needs time to sync etc).
In either case, Microsoft seems to be doing a lot of changes on Windows 10 to make Hybrid Azure AD Join more reliable and functional so maybe you can see there are certain versions which have this problem?
JonasBack Thanks for the tip. I will review this with our customer.
There are indeed some devices that are Hybrid Azure AD Joined and Registered.
