Intune co-managed device object ID instead of device name

Question

I'm running a pilot trying to get domain joined Windows devices that are registered in SCCM, Azure AD joined and managed by InTune.

So far I've managed to get my first Windows 11 device to be AAD joined after setting up the SCCM/Azure AD co-management piece.
When the device is registered in Intune however it is displayed with the GUID of the device rather than the machine name.
It doesn't look to me that the device has been registered properly with Intune, yet the device in AAD looks to be as it should.

InTune

AAD

Anyone advise on how to troubleshoot/rectify this issue further?
TIA

Answer 1

Co-managed devices can sometime take time to show up correctly in Intune. Are you sure you don't have more than 1 record for the devices in question?

Answer 2

@Matt Pollock , From your description, it seems we use Path 1 to enroll the existing Configuration Manager-managed devices which is Hybrid Azure AD join into Intune
https://learn.microsoft.com/en-us/mem/configmgr/comanage/quickstart-paths

On Intune portal, it shows device id instead of the name. And In Azure AD, it shows the device name. For your issue, I suggest go to the affected device side, Settings->Accounts->Access work or school, find the account, click info and then click Sync to do a manual sync, wait some time and see if it will change into device name.

Please try the above suggestion and if there's any update, feel free to let us know.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

I ended up running dsregcmd /leave and waited until the following day until my device disappeared in Intune and AAD.
I then ran dsregcmd /join and waited again until the device was added back to AAD via AAD Connect.
The following day the device appeared in Intune -with the correct display name, not the ObjectID.

No idea why it worked the second time around.