Intune provides an interface to easily deploy apps from the Microsoft Store to your registered users and devices, but even if you have SCCM (Config Manager) Co-Mangement enabled with the default workloads shifted to Intune in Co-Management properties, there is more to be done.  If you don’t follow these steps, you will receive the status of Not applicable in the Intune client apps user and device install status pages.

00.-Not-Applicable-in-Intune

Prerequisite: This only works with SCCM 1806+.

1. In the ConfigMgr console, browse to Administration, then Hierarchy Settings, and check the box to enable Pre-Release features.

01.-Enable-Pre-Release-Features

2. Stay in Administration, choose Updates and Services, then Features and right click Mobile apps for co-managed devices, choosing Turn on.

02.-Turn-On-Mobile-Apps

3. You are advised this can take a few minutes to apply within the console and to restart it.  Give it a few minutes, and close then reopen the console.

4. Back in Administration, find Cloud Services, expand it to enter Co-management, and go into CoMgmtSettingsPro properties.

03.-CoMgmtSettingsPro-Workloads-Client-apps-now-available

5. As can be seen in the above screenshot, there is a new workload in the Workloads tab called Client apps.  Use the slider to choose if SCCM or Intune should control these.  You can also, like all workloads, use Intune only for a pilot group.

6. When your co-managed devices (that is, those with the ConfigMgr agent and are Intune enrolled) next do a machine policy retrieval, they will collect the app assignment from Intune and enter the Install Pending state, followed by Installed when the app has been added to their Windows 10 device.

04.-Install-Pending-and-Installed