question

DavidCrickenberger-9052 avatar image
0 Votes"
DavidCrickenberger-9052 asked JarvisSun-MSFT edited

Enroll already AAD attached windows 10 machine into intune

I have a windows 10 machine that has been connected to AAD, and now our company is going to rollout InTune. I would like to understand what steps can be taken to enroll existing AAD attached machines into inTune?

mem-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.

JarvisSun-MSFT avatar image
0 Votes"
JarvisSun-MSFT answered JarvisSun-MSFT edited

@DavidCrickenberger-9052 Sorry for not replying to your additional question in time.
Not evaluated usually refers to an initial state for newly enrolled devices. specific situation need to be confirmed.
Is the device status still Not Evaluated? Have you tried to sync the policies and sign in again? Also, please check whether it is the following possible reasons for this state include:

Devices that aren't assigned a compliance policy and don't have a trigger to check for compliance

Devices that haven't checked in since the compliance policy was last updated

Devices enrolled with a device enrollment manager (DEM) account

https://docs.microsoft.com/en-us/mem/intune/protect/compliance-policy-monitor#device-compliance-status

Best regards
Jarvis

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.

Jason-MSFT avatar image
0 Votes"
Jason-MSFT answered DavidCrickenberger-9052 commented

There is no automated path to do this (without some other automation in the mix). Users will need to download the Company Portal from the Microsoft Store and enroll using it (assuming they are local admins).

· 1
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.

Thanks that seems to have done the job. I now see the device in Endpoint portal. But compliance is not Not Evaluated, so need to fix that.

But thanks again,
crick

0 Votes 0 ·