Error enrolling devices into Intune & Configuration Manager 1602

Enrolling devices into Intune and & ConfigMgr is normally straight forward until you run into issues. Below is an example where I received an enrollment error (picture 1), clicking Continue leads me to picture 2. As you can see in picture two the Enrollment Update turns from Warning to Checkmark, but only for about 5 seconds then it goes back to a warning.

image  image


Troubleshooting mobile devices is slightly different than traditional desktop troubleshooting. The troubleshooting options depends on the device (Android, iOS or Windows). In this example my device was an Android. You can email the log files from the Company Portal’s Settings page.

  • In Settings, tap SEND DATA. This launches the device email application and attaches all the log files.

You will receive multiple files from the device

  • CompanyPortalX.log. This log file contains a lot of information about the communication between the device and Microsoft Intune.
  • Omadmlog.log. OMA-DM is an open mobile standard for managing mobile devices.
  • For each managed application, you have a log file with the name of the managed application.

In my case I was having issues enrolling the device and looked at the companyportal.log file from the device.


Notice the error where it says DeviceCapReached.


xmlns:s="" xmlns:a=""><s:Header><a:Action s:mustUnderstand="1">DeviceCapReached</a:Action><a:RelatesTo>urn:uuid:0d5a1441-5891-453b-becf-a2e5f6ea3749</a:RelatesTo><ActivityId CorrelationId="86bcba8d-713d-4268-8e67-71d2d1edfb3f" xmlns="">24adefb9-3a96-4f66-8dbb-ec57a7052cea</ActivityId></s:Header><s:Body><s:Fault><s:Code><s:Value>s:Receiver</s:Value><s:Subcode><s:Value>s:DeviceCapReached</s:Value>

</s:Subcode></s:Code><s:Reason><s:Text xml:lang="en-US">WindowsEnrollmentServiceError</s:Text></s:Reason><s:Detail><WindowsDeviceEnrollmentServiceError xmlns="" xmlns:xsd="" xmlns:xsi=""><ErrorType>AuthorizationError</ErrorType><Message>DeviceCapReached</Message><TraceId>30525159-cff1-4ab0-bf2f-024faffaf3e6</TraceId></WindowsDeviceEnrollmentServiceError></s:Detail></s:Fault></s:Body></s:Envelope>, failureType: DRS WPJ v1.4.0, WorkplaceJoinFailure: null


My problem is that the Azure Active Directory registration device cap has been reached.  The default limit is 20 devices (and as I was testing i passed that number). To fix the issue open and delete the devices that are no longer needed. After that your can enroll new devices.



About the Author:

Kent Agerlund
Microsoft Regional Director, Enterprise Mobility MVP. Microsoft Certified Trainer and Principal consultant. I have been working with Enterprise client management since 1992. Co-founder of System Center User Group Denmark in 2009. Certified MCITP: Enterprise Administrator, MCSA+Messaing, and much more. Member of: Microsoft Denmark System Center Partner Expert Team The Danish Technet Influencers program System Center Influencers Program.


  1. The elimination of such faults is dependent on your default settings. The traditional search for solutions to the problem may lead to an unexpected result.

  2. Jobeth April 26, 2017 at 5:42 - Reply

    38mm white and rose gold -> has been my little pleasure to gawk at for the past months!Been followong your blog since you opened it, and is my fav. Keep up the style!lovJessica xxto.ail:liberatorepheoographe@gmailmcom

  3. It is so good for me to know some interesting things that are very important for developing my thone business.

  4. Kazzan June 22, 2018 at 12:18 - Reply

    Hi, the linked site currently throw ASP.NET error. Does the link change in time?

  5. heikkuri July 20, 2018 at 17:38 - Reply

    Hi, same message like Kazzan. The does not work any more.

Leave A Comment