Why is the enrolment through Company Portal unavailable? Don't go down the rabbit hole..

-

Credits: Adobe Stock

While working on a MDM migration project, I came across an interesting issue in Intune that almost had me heading down a rabbit hole. As part of the migration, the existing mobile devices were to be un-enrolled from a non Microsoft MDM solution and then enrolled into Intune using the Company Portal method. Nothing fancy, but when this process didn't work, I obviously got into an investigation mode and started looking at some of the obvious things.

The obvious items that I looked at -

1. Network requirements for Intune, Android and Apple services. I must state that in this customer's tenant they had ADFS setup, so that added to the complexity. However, since the enrolment was taking place outside the customer's network, none of the network requirements really played a factor.
2. Intune device platform restrictions. Normally when a device is not allowed to enrol in Intune, more often than not it is due to device platform restriction policies. Especially when it comes to enrolling personal, work profile devices. However, this was not an issue when I checked. Also, this was a new tenant so didn't expect much of a configuration. Or so I thought..

So what was the issue? Drum roll please.. It was none other than the Intune customization policy. Not expecting for this to be configured for a new tenant, to my surprise, the default customization policy was configured to block company portal enrolment. Rather than getting into the why this was done, I will focus on the setting in question.

Under Tenant Administration > Customization, you will come across the Configuration section of the default policy. Under this section, there is a setting for Device enrolment. As of writing this blog post, the following values are available -

Available, with prompts (Default) - The default experience with prompts to enroll in all possible locations.
Available, no prompts - User can enroll via the status in device details for their current device or from apps that require enrollment.
Unavailable - There is no way for users to enroll. Apps requiring enrollment will be hidden.

You can probably see where I am going with this. The device enrolment was set to 'Unavailable'. Once I changed it to the default value of 'Available, with prompts', the Company Portal enrolment was working again. That simple and definitely not so obvious in my honest opinion. Especially when there are no specific errors or Entra events that one can work with. If the device enrolment is 'Unavailable', then at best the user will only see the following in the Company Portal application where it says that the device settings status is 'Unknown'.

A couple of things -

1. The device enrolment setting does not apply to iOS/iPadOS devices configured to enrol with Automated Device Enrollment.

2. If a device has been configured for KME and device enrollment is set to Unavailable, the device will not be able to enroll during the out of box flow.

3. For the Android Company Portal app, if Intune detects that the user's device is set up for app protection policies without enrollment, the user will not get prompted to enroll in the Company Portal, even if the device enrollment setting is configured to prompt enrollment. This applies to all Android device types except Surface Duo devices.

Until next time..

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){              ...
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from st...
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $P...
Read more