Device wont be marked as compliant in AAD

%3CLINGO-SUB%20id%3D%22lingo-sub-1857979%22%20slang%3D%22en-US%22%3EDevice%20wont%20be%20marked%20as%20compliant%20in%20AAD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1857979%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22kvgmc6g5%20cxmmr5t8%20oygrvhab%20hcukyx3x%20c1et5uql%20ii04i59q%22%3E%3CDIV%3EHi!%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22o9v6fnle%20cxmmr5t8%20oygrvhab%20hcukyx3x%20c1et5uql%20ii04i59q%22%3E%3CDIV%3EI%20have%20a%20problem%20with%20a%20couple%20of%20devices.%20These%20devices%20was%20and%20are%20registered%20to%20Azure%20AD%20now%20and%20before%20we%20started%20with%20Intune.%20We%C2%B4ve%20asked%20some%20pilot%20users%20to%20manually%20register%20the%20devices%20in%20to%20intune%2C%20which%20they%20now%20are.%20So%20we%20have%20a%20couple%20of%20devices%20in%20Intune%20at%20the%20same%20time%20they%C2%B4re%20Azure%20AD%20Registered.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22o9v6fnle%20cxmmr5t8%20oygrvhab%20hcukyx3x%20c1et5uql%20ii04i59q%22%3E%3CDIV%3ENow%2C%20we%C2%B4re%20starting%20to%20work%20with%20conditional%20access%20and%20exception%20for%20compliant%20devices%20which%20works%20on%20some%20computers%2C%20however..%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EA%20couple%20of%20computers%20does%20not%20work%20with%20this%20policy%20since%20on%20one%20user%20the%20Intune-device%20are%20not%20assigned%20to%20the%20user%20in%20Azure%20AD%20and%20marked%20as%20compliant%20so%20conditional%20access%20won%C2%B4t%20let%20him%20in%20because%20it%20cant%20see%20the%20compliant%20device...%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22o9v6fnle%20cxmmr5t8%20oygrvhab%20hcukyx3x%20c1et5uql%20ii04i59q%22%3E%3CDIV%3EThey%20are%20added%20in%20the%20same%20way%20but%20here%C2%B4s%20one(Not%20compliant%20but%20that%C2%B4s%20not%20the%20issue%20here)%20but%20there%20i%20can%20see%20in%20Azure%20AD%20-%26gt%3B%20Devices%20on%20the%20user%20that%20it%C2%B4s%20compliant%20and%20a%20part%20of%20Intune%3A%3C%2FDIV%3E%3CDIV%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%221.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F231715iFB0E34E7854B607B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%221.PNG%22%20alt%3D%221.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22o9v6fnle%20cxmmr5t8%20oygrvhab%20hcukyx3x%20c1et5uql%20ii04i59q%22%3E%3CDIV%3EHere%20are%20the%20other%20one%20where%20we%20have%20issues...%3A%3C%2FDIV%3E%3CDIV%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%223.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F231717i305D90D5ED2241CC%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%223.PNG%22%20alt%3D%223.PNG%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F231716i73E72F5AC4EAA083%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%222.PNG%22%20alt%3D%222.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EIn%20intune%20the%20device%20are%20compliant.%20How%20can%20i%20get%20to%20be%20marked%20as%20compliant%20in%20Azure%20AD%20as%20well%3F%3F%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%2F%2FMartin%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1857979%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConditional%20access%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor
Hi!
 
I have a problem with a couple of devices. These devices was and are registered to Azure AD now and before we started with Intune. We´ve asked some pilot users to manually register the devices in to intune, which they now are. So we have a couple of devices in Intune at the same time they´re Azure AD Registered.
 
Now, we´re starting to work with conditional access and exception for compliant devices which works on some computers, however..
 
A couple of computers does not work with this policy since on one user the Intune-device are not assigned to the user in Azure AD and marked as compliant so conditional access won´t let him in because it cant see the compliant device...
 
They are added in the same way but here´s one(Not compliant but that´s not the issue here) but there i can see in Azure AD -> Devices on the user that it´s compliant and a part of Intune:
1.PNG
 
Here are the other one where we have issues...:
3.PNG2.PNG
 
In intune the device are compliant. How can i get to be marked as compliant in Azure AD as well??
 
//Martin
0 Replies