Skip to main content

Limits and Constraints

This section describes the known limitations that come with the Microsoft Intune connector.

Due to current limitations in Microsoft Graph APIs, the following restrictions apply to the Microsoft Intune connector when retrieving data through the Microsoft Graph API.

Application discovery limitations on BYOD devices​

Microsoft Intune collects information about all managed and unmanaged applications on corporate-owned devices. However, for personally owned (BYOD) devices, Microsoft Intune does not provide data on unmanaged applications, as described in the Microsoft Intune documentation.

As a result, the Microsoft Intune connector for Snow Integration Manager may have limited visibility into installed applications on BYOD devices. This limitation can affect the completeness of inventory data and subsequent reporting.

Missing manufacturer information in application inventory data​

The MS Intune AppInvRawData report for exposing application inventory data https://learn.microsoft.com/en-us/intune/intune-service/fundamentals/reports-export-graph-available-reports does not provide the manufacturing details for mobile applications, limiting the connector to retrieve the application name and version information currently.

This missing data presents several challenges:

  • Manufacturer information is required for software classification and licensing compliance in the Data Intelligence Service (DIS) database.

  • Without manufacturer details, mapping records to the global catalog becomes more complex and may result in false positives, duplicate entries, or misclassification.

  • Accurate manufacturer data is essential for recognizing and mapping third-party software, which affects compliance and entitlement reporting.

Some workarounds to address this limitation:

  • If the manufacturer name is implied in the application name field and a valid version is present, the connector proactively maps the data to the appropriate software entry.

  • For well-known publishers, such as Microsoft, mapping can be confidently inferred even if the manufacturer field is missing.

    note

    These workarounds help improve application recognition accuracy, but do not fully replace the need for native manufacturer data from the source API.