%3CLINGO-SUB%20id%3D%22lingo-sub-280154%22%20slang%3D%22en-US%22%3ESupport%20tip%3A%20Troubleshooting%20iOS%20or%20Android%20policies%20not%20applying%20to%20devices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280154%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EFirst%20published%20on%20TechNet%20on%20Aug%2029%2C%202018%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20We've%20seen%20customers%20have%20issues%20where%20they%20deploy%20an%20iOS%20or%20Android%20policy%20to%20a%20device%2C%20but%20it%20doesn%E2%80%99t%20get%20applied%20to%20the%20device.%20This%20could%20simply%20be%20because%20the%20policy%20is%20not%20compatible%20with%20the%20OS%20version%20and%20device%20type%20or%20that%20the%20policy%20is%20incorrectly%20targeted%20to%20the%20user%20or%20device.%20Another%20way%20you%20can%20resolve%20this%20is%20by%20following%20the%20troubleshooting%20steps%20we%E2%80%99ve%20listed%20below.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20In%20portal.azure.com%2C%20go%20to%20Intune%20%26gt%3B%20Troubleshoot%20and%20select%20the%20user%20to%20troubleshoot.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20906px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F58701iF9E8AF89E7EE1549%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EAfter%20the%20user%20is%20selected%2C%20make%20sure%20%3CSTRONG%3E%20Intune%20License%20%3C%2FSTRONG%3E%20and%20%3CSTRONG%3E%20Account%20Status%20%3C%2FSTRONG%3E%20appear%20with%20green%20checks.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EOn%20the%20same%20page%2C%20under%20%3CSTRONG%3E%20Devices%20%3C%2FSTRONG%3E%20%2C%20find%20the%20device%20to%20troubleshoot%20and%20check%20that%20the%20%3CSTRONG%3E%20Managed%20%3C%2FSTRONG%3E%20%3CSTRONG%3E%20By%20%3C%2FSTRONG%3E%20column%20shows%20%3CSTRONG%3E%20MDM%20%3C%2FSTRONG%3E%20or%20%3CSTRONG%3E%20EAS%2FMDM.%20%3C%2FSTRONG%3E%20If%20you%20do%20not%20see%20these%20values%2C%20the%20device%20is%20not%20enrolled.%20It%20will%20not%20receive%20compliance%20or%20configuration%20policies%20until%20it%E2%80%99s%20enrolled.%20App%20Protection%20Policies%20(also%20known%20as%20MAM%20policies)%20do%20not%20require%20enrollment.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ECheck%20that%20%3CSTRONG%3E%20Azure%20AD%20Join%20Type%20%3C%2FSTRONG%3E%20shows%20%3CSTRONG%3E%20Workplace%20%3C%2FSTRONG%3E%20.%20If%20you%20see%20%3CSTRONG%3E%20Not%20Registered%20%3C%2FSTRONG%3E%20%2C%20there%20might%20have%20been%20a%20problem%20during%20enrollment.%20Unenrolling%20and%20re-enrolling%20the%20device%20will%20resolve%20this%20problem.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ECheck%20that%20%3CSTRONG%3E%20Intune%20Compliant%20%3C%2FSTRONG%3E%20and%20%3CSTRONG%3E%20Azure%20AD%20Compliant%20%3C%2FSTRONG%3E%20show%20%3CSTRONG%3E%20Yes.%20%3C%2FSTRONG%3E%20A%20%3CSTRONG%3E%20No%20%3C%2FSTRONG%3E%20in%20either%20column%20might%20indicate%20one%20of%20the%20following%20problems%3A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EThe%20device%20does%20not%20meet%20the%20requirements%20defined%20in%20your%20organization%E2%80%99s%20compliance%20policies.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EThe%20device%20is%20not%20connected%20to%20the%20Intune%20service.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ECheck%20that%20%3CSTRONG%3E%20Last%20Check%20In%20%3C%2FSTRONG%3E%20shows%20a%20recent%20time%20and%20date.%20Devices%20check%20in%20with%20Intune%20at%20least%20every%208%20hours.%20If%20it%E2%80%99s%20been%20more%20that%2024%20since%20last%20check-in%2C%20there%20might%20be%20a%20problem%20with%20the%20device.%20A%20device%20that%20cannot%20check%20in%20cannot%20receive%20policies%20from%20Intune.%20To%20force%20a%20device%20to%20check%20in%2C%20follow%20the%20set%20of%20instructions%20below%20that%20matches%20the%20device%E2%80%99s%20OS.%20These%20steps%20can%20be%20done%20from%20any%20device.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3Ea)%20For%20Android%2C%20open%20the%20Company%20Portal%20app%20and%20select%20%3CSTRONG%3E%20Devices%20%3C%2FSTRONG%3E%20%26gt%3B%20problem%20device%20from%20list%20%26gt%3B%20%3CSTRONG%3E%20Check%20Device%20Settings%20%3C%2FSTRONG%3E%20.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%20b)%20For%20iOS%2C%20open%20the%20Company%20Portal%20app%20and%20select%20%3CSTRONG%3E%20Devices%20%3C%2FSTRONG%3E%20%26gt%3B%20problem%20device%20from%20list%20%26gt%3B%20%3CSTRONG%3E%20Check%20Settings%20%3C%2FSTRONG%3E%20.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20c)%20For%20Windows%2C%20open%20the%20device%20Settings%20and%20select%20%3CSTRONG%3E%20Accounts%20%3C%2FSTRONG%3E%20%26gt%3B%20%3CSTRONG%3E%20Access%20Work%20or%20School%20%3C%2FSTRONG%3E%20%26gt%3B%20applicable%20connection%20%26gt%3B%20%3CSTRONG%3E%20Info%20%3C%2FSTRONG%3E%20%26gt%3B%20%3CSTRONG%3E%20Sync%20%3C%2FSTRONG%3E%20.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3ESelect%20the%20device%20to%20view%20the%20device%E2%80%99s%20policy%20details.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3EUnder%20%3CSTRONG%3E%20Devices%20%26gt%3B%20Manage%20%3C%2FSTRONG%3E%20%2C%20go%20to%20both%20%3CSTRONG%3E%20Device%20compliance%20%3C%2FSTRONG%3E%20and%20%3CSTRONG%3E%20Device%20configuration%20%3C%2FSTRONG%3E%20and%20make%20sure%20the%20device%20policy%20you%E2%80%99re%20trying%20to%20assign%20is%20listed.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3COL%3E%0A%3CLI%3Ea)%20If%20the%20policy%20is%20listed%2C%20review%20its%20%3CSTRONG%3E%20State%20%3C%2FSTRONG%3E%20%3A%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FOL%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3ENot%20applicable%20-%20this%20policy%20is%20not%20supported%20on%20this%20platform.%20For%20example%2C%20iOS%20policies%20won%E2%80%99t%20work%20on%20Android%20devices%2C%20and%20Samsung%20KNOX%20policies%20won%E2%80%99t%20work%20on%20non-Samsung%20KNOX%20devices.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EConflict%20-%20There%20is%20an%20existing%20setting%20on%20the%20device%20that%20Intune%20cannot%20override.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EPending%20-%20The%20device%20has%20not%20checked%20in%20to%20Intune%20to%20retrieve%20the%20policy.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CUL%3E%0A%3CLI%3EErrors%20%E2%80%93%20Review%20a%20list%20of%20possible%20errors%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fna01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fintune%252Ftroubleshoot-company-resource-access-problems%26amp%3Bdata%3D04%257C01%257C%257C8e57e23bf2b14ee6b00708d60dd8ba77%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636711621813569425%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%253D%253D%257C-1%26amp%3Bsdata%3DGmWj3pSREQZ%252BBS8g4iovSoUF%252Fib5xdgxPAwQw%252BhR%252BC0%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Intune%20documentation%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%20b)%20If%20the%20policy%20is%20not%20listed%2C%20it%20has%20not%20been%20assigned%20correctly.%20Go%20back%20to%20policy%20creation%20and%20assign%20policy%20to%20the%20user%20device.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We%20hope%20this%20helps%20you%20narrow%20down%20the%20reason%20for%20iOS%20or%20Android%20policies%20not%20applying%20to%20devices.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-280154%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20published%20on%20TechNet%20on%20Aug%2029%2C%202018%20We've%20seen%20customers%20have%20issues%20where%20they%20deploy%20an%20iOS%20or%20Android%20policy%20to%20a%20device%2C%20but%20it%20doesn%E2%80%99t%20get%20applied%20to%20the%20device.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-280154%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAndroid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eintune%20on%20azure%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EiOS%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Epolicies%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Etroubleshooting%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281538%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20tip%3A%20Troubleshooting%20iOS%20or%20Android%20policies%20not%20applying%20to%20devices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281538%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20using%20free%20MDM%20option%20of%20Office%20365%20and%20i%20have%20seen%20a%20few%20cases%20when%20enrolling%20Android%20phones%20with%20standard%20Email%20app%20already%20setup%20before%20that%20and%20email%20still%20working%20fine.%20After%20removing%20email%20account%20and%20trying%20to%20add%20it%20again%2C%20then%20it%20showed%20a%20message%20that%20it%20must%20be%20enrolled%20first.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-785299%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20tip%3A%20Troubleshooting%20iOS%20or%20Android%20policies%20not%20applying%20to%20devices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-785299%22%20slang%3D%22en-US%22%3E%3CP%3Ehi%2C%20I%20have%20followed%20this%20procedure%20to%20the%20letter%20and%20am%20at%20device%20configuration%20policy%20is%20pending.%20However%20my%20devices%20has%20checked%20in%20numerous%20times%20(over%2024h)%20since%20the%20assignment%20of%20the%20policy%2C%20but%20the%20status%20remains%20pending.%20what's%20the%20next%20step%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20I%20figured%20it%20out...%3CBR%20%2F%3EHere's%20the%20use%20case%3A%20I%20have%20tablets%20and%20phones%20that%20are%20used%20as%20tools%20by%20employees.%20They%20are%20staged%20using%20Knox%20Enrollment%20and%20Intune%20(Android%20Enterprise)%20(so%20that%20we%20can%20push%20apps%20and%20not%20require%20a%20google%20account).%3C%2FP%3E%3CP%3ESome%20of%20these%20are%20used%20at%20sites%20where%20a%20camera%20is%20not%20allowed.%20I%20wanted%20to%20set%20up%20a%20device%20configuration%20to%20block%20the%20camera%20for%20these%20users.%20I%20can%20easily%20block%20it%20in%20the%20work%20profile%2C%20but%20of%20course%20I%20need%20it%20blocked%20completely.%20The%20device%20restriction%20(on%20device%20level)%20will%20not%20apply%20(it%20remains%20pending).%20Switching%20the%20device%20to%20Android%2C%20and%20setting%20a%20device%20restriction%20also%20works%2C%20but%20is%20pretty%20useless%20to%20me%2C%20especially%20since%20everyone%20is%20saying%20that%20as%20of%20Android%2010%2C%20Enterprise%20will%20be%20the%20only%20way%20forward.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConclusion%20(mine)%3A%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20though%20I%20am%20strongly%20in%20favor%20of%20the%20Android%20Enterprise%20solution%20(much%20tighter%20security)%2C%20it%20seems%20like%20Intune%20%2B%20Android%20(google%3F)%20still%20have%20a%20lot%20of%20work%20set%20out%20before%20the%20functional%20needs%20of%20the%20reel%20world%2C%20will%20combine%20with%20the%20technical%20limitations%20currently%20at%20hand%20(another%20example%20is%20contact%20integration%20between%20the%20work%20profile%20and%20the%20built%20in%20contact%20list%2C%20e.g.%20to%20be%20able%20to%20dial%20contacts%20from%20your%20car).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1170416%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20tip%3A%20Troubleshooting%20iOS%20or%20Android%20policies%20not%20applying%20to%20devices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1170416%22%20slang%3D%22en-US%22%3E%3CP%3ENeed%20an%20option%20to%20troubleshoot%20by%20device%2C%20we%20are%20starting%20to%20do%20enrollments%20via%20token.%3C%2FP%3E%3C%2FLINGO-BODY%3E

First published on TechNet on Aug 29, 2018
We've seen customers have issues where they deploy an iOS or Android policy to a device, but it doesn’t get applied to the device. This could simply be because the policy is not compatible with the OS version and device type or that the policy is incorrectly targeted to the user or device. Another way you can resolve this is by following the troubleshooting steps we’ve listed below.

In portal.azure.com, go to Intune > Troubleshoot and select the user to troubleshoot.





    1. After the user is selected, make sure Intune License and Account Status appear with green checks.

 

    1. On the same page, under Devices , find the device to troubleshoot and check that the Managed By column shows MDM or EAS/MDM. If you do not see these values, the device is not enrolled. It will not receive compliance or configuration policies until it’s enrolled. App Protection Policies (also known as MAM policies) do not require enrollment.

 

    1. Check that Azure AD Join Type shows Workplace . If you see Not Registered , there might have been a problem during enrollment. Unenrolling and re-enrolling the device will resolve this problem.

 

    1. Check that Intune Compliant and Azure AD Compliant show Yes. A No in either column might indicate one of the following problems:




    • The device does not meet the requirements defined in your organization’s compliance policies.

 

    • The device is not connected to the Intune service.




    1. Check that Last Check In shows a recent time and date. Devices check in with Intune at least every 8 hours. If it’s been more that 24 since last check-in, there might be a problem with the device. A device that cannot check in cannot receive policies from Intune. To force a device to check in, follow the set of instructions below that matches the device’s OS. These steps can be done from any device.

 

    1. a) For Android, open the Company Portal app and select Devices > problem device from list > Check Device Settings .



b) For iOS, open the Company Portal app and select Devices > problem device from list > Check Settings .

c) For Windows, open the device Settings and select Accounts > Access Work or School > applicable connection > Info > Sync .

    1. Select the device to view the device’s policy details.

 

    1. Under Devices > Manage , go to both Device compliance and Device configuration and make sure the device policy you’re trying to assign is listed.

 

    1. a) If the policy is listed, review its State :




    • Not applicable - this policy is not supported on this platform. For example, iOS policies won’t work on Android devices, and Samsung KNOX policies won’t work on non-Samsung KNOX devices.

 

    • Conflict - There is an existing setting on the device that Intune cannot override.

 

    • Pending - The device has not checked in to Intune to retrieve the policy.

 



b) If the policy is not listed, it has not been assigned correctly. Go back to policy creation and assign policy to the user device.

We hope this helps you narrow down the reason for iOS or Android policies not applying to devices.

3 Comments
Super Contributor

We are using free MDM option of Office 365 and i have seen a few cases when enrolling Android phones with standard Email app already setup before that and email still working fine. After removing email account and trying to add it again, then it showed a message that it must be enrolled first.

Frequent Visitor

hi, I have followed this procedure to the letter and am at device configuration policy is pending. However my devices has checked in numerous times (over 24h) since the assignment of the policy, but the status remains pending. what's the next step?

 

I think I figured it out...
Here's the use case: I have tablets and phones that are used as tools by employees. They are staged using Knox Enrollment and Intune (Android Enterprise) (so that we can push apps and not require a google account).

Some of these are used at sites where a camera is not allowed. I wanted to set up a device configuration to block the camera for these users. I can easily block it in the work profile, but of course I need it blocked completely. The device restriction (on device level) will not apply (it remains pending). Switching the device to Android, and setting a device restriction also works, but is pretty useless to me, especially since everyone is saying that as of Android 10, Enterprise will be the only way forward.

 

Conclusion (mine): 

All though I am strongly in favor of the Android Enterprise solution (much tighter security), it seems like Intune + Android (google?) still have a lot of work set out before the functional needs of the reel world, will combine with the technical limitations currently at hand (another example is contact integration between the work profile and the built in contact list, e.g. to be able to dial contacts from your car).

Contributor

Need an option to troubleshoot by device, we are starting to do enrollments via token.