Support Tip: Enrolled Windows 10 devices not able to use the CP app to install available apps

This post has been republished via RSS; it originally appeared at: Intune Customer Success articles.

By Scott Duffey | Intune Sr. PM


Update to the post as of March 5, 2019: 

We’ve been working on a solution and are pleased to share we’ll be rolling out some changes to resolve this known issue in the March (1903) Intune service release.

The cause for the Company Portal enrollment message was due to the affected devices not having an Intune Primary User assigned. We’ve ensured that Primary User will be correctly added for devices that enrolled through Auto MDM Enrollment with AAD Token, Autopilot Hybrid Azure AD Join, and ConfigMgr co-management enrollment types. We expect to back-fill those devices already enrolled without this Primary User so they now have this information.


In addition, we will be introducing a new capability specifically for shared devices that were bulk Azure AD Joined and automatically enrolled into Intune (this includes devices that were bulk provisioned with “Setup School PC” or “Windows Configuration Designer”). Since these devices are used by multiple Windows Users and not a Primary User, we’ve made a few changes to the way the Company Portal detects the enrollment state. The end result to these changes is that end users of bulk-enrolled devices will be able to use the Company Portal to acquire available apps.
 We thank you for your patience while we engineered a solution. Again, we expect these changes to occur during the March Intune release.  


Original post: 

We have received a few cases and are aware of an issue where some enrolled Windows 10 devices are not able to use the Company Portal app to install available apps. The end user experience is that there are no available apps in the Company Portal.


Here's the details of this known issue. Note there's more than one workflow.

  • Devices are enrolled into Intune through the Group Policy autoenrollment. The workflow is - Computer Configuration > Administrative Templates > Windows Components > MDM > Auto MDM Enrolment with AAD Token
  • The second workflow is when enrolled using an AutoPilot profile with Hybrid Azure AD Join (Preview)


End users may see the following message when launching the company portal app “This device hasn’t been set up for corporate use yet. Select this message to begin setup.”


my devices.png


We are investigating these scenarios further and working on solution(s) depending on configuration. There's an immediate workaround regardless of your path to get here. You can make the apps required.


Post Updated:

  • March 5, 2019 to including details on a resolution/solution coming in an upcoming release. 

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.