Microsoft

Microsoft Intune Feedback

Suggestion box powered by UserVoice

How can we improve Microsoft Intune

Unable to install apps from Company portal when Win10 device is Azure bulked enrolled

When a Windows 10 device is bulked enrolled via provisioning package it is not possible to install applications where the portal states the following: "This device hasn't been set up for corporate use yet. Select this message to begin setup".

I can confirm that the devices is enrolled into Azure and managed by Intune. This is how the Company Portal gets installed in the first place.

43 votes
Vote
Sign in
(thinking…)
Sign in with: sso facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Marius A. Skovli shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

We are happy to announce this is planned to ship with the March 2019 release
https://docs.microsoft.com/en-au/intune/in-development#install-available-apps-using-the-company-portal-app-after-windows-bulk-enrollment-

Watch your Message Center for the announcement that the March update is complete. We’ll wait and flip this to complete when that’s done, but in the meantime we’ll give you your votes back to use for something else.
Thanks for the feedback, and thanks for using Microsoft Intune!

7 comments

Sign in
(thinking…)
Sign in with: sso facebook google
Signed in as (Sign out)
Submitting...
  • Al commented  ·   ·  Flag as inappropriate

    Is this update completed ? It's been almost 3 months in release status.

  • Peter commented  ·   ·  Flag as inappropriate

    This is a major issue and defeats the concept of having a company portal app to provide user-context application self-service whilst enroling devices en bulk.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This also happens from time to time without bulk enrolling after single clean installs, autopilot resets etc.

  • Ciarán Ainsworth commented  ·   ·  Flag as inappropriate

    We're currently hitting this issue. Our setup is that we deploy hundreds of devices which are imaged through SCCM and then bulk joined to Azure AD -> Intune management with scripts to wipe SCCM clients off. Policies and deployments work fine, but one of the most important things we want to push for is self-service of LOB apps as well as store apps. Joining these devices manually is not tenable as we are a very small team with a large customer-base, and the idea that bulk joining somehow restricts functionality is patently nonsensical.

    The way I saw this working was more in line with SCCM's application store. Simple MSI installers could be installed and uninstalled by users at will provided access was granted. But now we find that simply because we've bulk enrolled the devices (by necessity) this cannot be achieved. This desperately needs to be addressed.

  • Azim commented  ·   ·  Flag as inappropriate

    This kills the whole purpose of intune! Add functionality, remove functionality. That bug is a feature. Its always one step forward, 3 steps backward with intune

  • Anonymous commented  ·   ·  Flag as inappropriate

    Also, Teamviewer integration will not work. Company Portal App is pretty useless when your device is bulk enrolled.

Feedback and Knowledge Base