question

51468505 avatar image
0 Votes"
51468505 asked saldana-msft edited

MEM/Intune - Autopilot Device shows up on Autopilot section and Azure AD Devices as joined, but not showing up in All Devices

I have Autopilot added a device in my tenant and have assigned a user to it.
It is showing up as an Autopilot device and it is also showing up in Azure AD under Devices, also shows the user assigned to the device.

However it is not showing up in All Devices within the MEM/Intune portal, which means it is not getting MEM/Intune policies.
It has now been 3 days and it's still not updated.

I've seen reports of people having to wait for a couple of days but this is now taking too long.

There's only 3 users so far as it is a fairly new tenant, so no load there. Tenant has P2 licensing as well and all the correct licensing to do Autopilot.
Windows 10 Enterprise device is running 20H2 version.

I've also tried to add it using the Company Portal but I get an error saying that the Device has already an assignment. (Pretty obvious as it is registered in the tenant)

mem-cm-generalmem-intune-generalmem-intune-enrollment
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LuDaiMSFT-0289 avatar image
0 Votes"
LuDaiMSFT-0289 answered

@WildashIT-5577 Thanks for posting in our Q&A. From your description, I know that the autopilot device is showing in Azure AD but isn't showing in intune. If there is anything misunderstanding, feel free to let us know.

To clarify this issue, we appreciate your help to collect some information:
1.Please check if the MDM of this device is "Microsoft Intune" in Azure AD portal.
72268-image.png
2.Please check if the MDM user scope is set to "All"
72245-image.png

If there is any update, feel free to let us know.


If the response is helpful, please click "Accept Answer" and upvote it.
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.



image.png (12.5 KiB)
image.png (49.8 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

51468505 avatar image
0 Votes"
51468505 answered 51468505 edited

Hi @LuDaiMSFT-0289 thank you for getting back regarding this.
I've just changed the MDM scope to be All instead of None.

The device in AzureAD indeed shows up with None on the MDM column
72803-image.png



How long does it take for this to change, now that the MDM scope has been updated to All?

Do I need to do an Autopilot Reset?

Thanks again


image.png (12.1 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@51468505 Thanks for your update.

Yes, it is needed to do a reset. After reset successfully, please check if the device is showing both in Azure portal and intune portal.

Thanks.

0 Votes 0 ·

Awesome, I deleted the device HWID from Autopilot discovery and then deleted it from Azure AD.
Fully formatted and re-installed Windows on the laptop, going through White Glove now, I can see the Device in MEM.

Thank you so much for your help, such a small setting, easy to overlook, definitely will keep that in mind next time :)

Thanks again

72891-image.png


0 Votes 0 ·
image.png (13.2 KiB)

@51468505 You're welcome. If there is any problem in the future, welcome to post in our Q&A.

Thanks and have a nice day.

1 Vote 1 ·