Integration with Microsoft Intune for Windows 10 Devices

With this release, we have support for deploying software to Windows 10 devices using Microsoft Intune. There is support added to make use of the co-management capability from Microsoft that enables the ability to concurrently manage Windows 10 devices by using both Configuration Manager and Microsoft Intune.

For Windows 10 devices that have Configuration Manager client and are also enrolled to Intune, the Client Apps workload in Configuration Manager can be set to either Configuration Manager, Pilot Intune, or Intune. Depending on the option it is set to and the priority set in order for detecting client deployment technology available under Site Management > Settings > Deployment > Common tab, App Portal will pick either Configuration Manager or Intune for deployment.

Service Integration capabilities that exist in the product are supported for Intune also.

Microsoft Intune has a limitation of not being able to provide the domain value of the device. Due to this, if Intune is chosen as the source of device data sync, App Portal does not currently have support for license governance capabilities like license reservation and license reclamation. This is because device domain is an important value while getting license position and usage details from FlexNet Manager Suite. Due to this limitation, for customers who have a comanaged setup where they are using both Configuration Manager and Intune, for now, the recommendation would be to use Configuration Manager as the source of data sync until Intune provides the capability to fetch domain name. However, if Intune is chosen as the source for data sync, a workaround is provided to fetch the device domain data which is mentioned in the Intune Domain Name Limitation and Workaround section of the Administration Guide.

Environment Requirements for Intune

Before beginning App Portal / App Broker installation, make sure that your environment meets the following requirements:

Requirement	Description
Azure Active Directory	Microsoft Azure Active Directory is required for App Portal / App Broker.
Integration of on-premises Active Directory with Azure Active Directory	App Portal / App Broker requires Azure Active Directory to be integrated and in sync with on-premises Active Directory. Azure AD Connect can be used to sync data.

Scope

The following are the App Portal client requirements:

Requirement	Description
Desktop Operating Systems	Windows 10
App Types	Microsoft Store for Business Apps Windows Line of Business Apps (.msi and .msix)
Deployment Method	Device Based (Group intent supported is Required) Note:User based deployment is not supported. Group intent Available is not supported.