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.
This also happens from time to time without bulk enrolling after single clean installs, autopilot resets etc.
Ciarán Ainsworth commented
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.
Tore johnny Blomhaug commented
any update on this issue?
still the same issue on windows 10 1803,Conditional access is not supported either.
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
Also, Teamviewer integration will not work. Company Portal App is pretty useless when your device is bulk enrolled.