Change log for the Intune Data Warehouse API

Keep current on updates to the Intune Data Warehouse.

1903 (Part 2)

Released April 2019

Beta changes

The following table lists the recent removed collections and the replacements collections in the Intune Data Warehouse.

Collection Change Additional information
mobileAppDeviceUserInstallStatus Removed Use mobileAppInstallStatusCounts instead.
enrollmentTypes Removed Use deviceEnrollmentTypes instead.
mdmStatuses Removed Use complianceStates instead.
workPlaceJoinStateTypes Removed Use the azureAdRegistered property in the devices and devicePropertyHistories collections instead.
clientRegistrationStateTypes Removed Use deviceRegistrationStates instead.
currentUser Removed Use the users collection instead.
mdmDeviceInventoryHistories Removed Many of the properties were redundant or can now be found in the devicePropertyHistories or devices collections. Any mdmDeviceInventoryHistories properties not already listed with these two collections are no longer available. See details below.

The following table lists the old properties formerly found in the mdmDeviceInventoryHistories collection and the change/replacement. Any properties that were in mdmDeviceInventoryHistories but not listed below have been removed.

Old property Change/replacement
cellularTechnology cellularTechnology in devices collection
deviceClientId deviceId in devices collection
deviceManufacturer manufacturer in devices collection
deviceModel model in devices collection
deviceName deviceName in devices collection
deviceOsPlatform deviceTypeKey in devices collection
deviceOsVersion osVersion in devicePropertyHistories collection
deviceType deviceTypeKey in devices collection, referencing deviceTypes collection
encryptionState encryptionState property in the devices collection
exchangeActiveSyncId easDeviceId property in the devices collection
exchangeDeviceId easDeviceId in devices collection
imei imei in devices collection
isSupervised isSupervised property in the devices collection
jailBroken jailBroken in devicePropertyHistories collection
meid meid property in the devices collection
oem manufacturer in devices collection
osName deviceTypeKey in devices collection, referencing deviceTypes collection
phoneNumber phoneNumber in devices collection
platformType model in devices collection
product deviceTypeKey in devices collection
productVersion osVersion in devicePropertyHistories collection
serialNumber serialNumber in devices collection
storageFree freeStorageSpaceInBytes property in the devices collection
storageTotal totalStorageSpaceInBytes property in the devices collection
subscriberCarrierNetwork subscriberCarrier property in the devices collection
wifimac wiFiMacAddress in devices collection

The following table lists changes to properties found in the devicePropertyHistories collection:

Old property Change/replacement
categoryId deviceCategoryKey, referencing deviceCategories collection
certExpirationDate Removed
clientRegistrationStateKey deviceRegistrationStateKey
createdDate enrolledDateTime in devices collection
deviceTypeKey deviceTypeKey in devices collection
easID easDeviceId in devices collection
enrolledByUser userId in devices collection
enrollmentTypeKey deviceEnrollmentTypeKey in devices collection
graphDeviceIsCompliant Removed
graphDeviceIsManaged Removed
lastContact lastSyncDateTime in devices collection
lastContactNotification Removed
lastContactWorkplaceJoin Removed
lastExchangeStatusUtc Removed
lastModifiedDateTimeUTC Removed
lastPolicyUpdateUtc Removed
managementAgentKey managementStateKey
manufacturer manufacturer in devices collection
mdmStatusKey complianceStateKey, referencing complianceStates collection
model model in devices collection
osFamily operatingSystem in devices collection
osRevisionNumber osVersion in devices collection
processorArchitecture Removed
referenceId azureAdDeviceId in devices collection
serialNumber serialNumber in devices collection
workplaceJoinStateKey azureAdRegistered

The following table lists changes to properties found in the devices collection:

Old property Change/replacement
categoryId deviceCategoryKey, referencing deviceCategories collection
certExpirationDate Removed
clientRegistrationStateKey deviceRegistrationStateKey
createdDate enrolledDateTime
easId easDeviceId
enrolledByUser userId
enrollmentTypeKey deviceEnrollmentTypeKey
graphDeviceIsCompliant Removed
graphDeviceIsManaged Removed
lastContact lastSyncDateTime
lastContactNotification Removed
lastContactWorkplaceJoin Removed
lastExchangeStatusUtc Removed
lastPolicyUpdateUtc Removed
mdmStatusKey complianceStateKey, referencing complianceStates collection
osFamily operatingSystem
processorArchitecture Removed
referenceId azureAdDeviceId
workplaceJoinStateKey azureAdRegistered

The following table lists changes to properties found in the enrollmentActivities collection:

Old property Change/replacement
enrollmentTypeKey deviceEnrollmentTypeKey

The following table lists changes to properties found in the mamApplications collection:

Old property Change/replacement
applicationKey mamApplicationKey
applicationName mamApplicationName
applicationId mamApplicationId

The following table lists changes to properties found in the mamApplicationInstances collection:

Old property Change/replacement
applicationId mamApplicationId
deviceId mamDeviceId
deviceType mamDeviceType
deviceName mamDeviceName

The following table lists changes to properties found in the mamCheckins collection:

Old property Change/replacement
applicationKey mamApplicationKey

The following table lists changes to properties found in the users collection:

Old property Change/replacement
startDateInclusiveUtc Removed
endDateInclusiveUtc Removed
isCurrent Removed

1903

Released March 2019

V1.0 changes reflecting back to beta

When V1.0 was first introduced in 1808, it differed in some significant ways from the beta API. In 1903 those changes will be reflected back into the beta API version. If you have important reports that use the beta API version, we strongly recommend switching those reports to V1.0 to avoid breaking changes. Please refer to API version information for more information on Data Warehouse API versions and backwards compatibility.

1902

Released February 2019

Power BI Compliance app

Access your Intune Data Warehouse in Power BI Online using the Intune Compliance (Data Warehouse) app. With this Power BI app, you can now access and share pre-created reports without any setup and without leaving your web browser.

Note

There are two additional filters you can apply to the Intune Compliance app.

Add additional filters to the Intune Compliance app

  1. Open the Intune Compliance (Data Warehouse) app in your web browsers.
  2. Click Non-Compliant Devices and select Non-Compliant in the complianceStatus filter.
  3. Click on Unknown Devices and select Not Yet Available in the complianceStatus filter.

1812

Released December 2018

Enrollment Activities Collection Released to v1.0

The Enrollment Activities collection is now available in v1.0. You can use this collection to understand enrollment failure volume and trends in your environment. For more information, see enrollmentActivities, enrollmentEventStatuses, enrollmentFailureCategories, and enrollmentFailureReasons.

1808

Released August 2018

v1.0 Collections

You can now use the v1.0 version of the Intune Data Warehouse by setting the query parameter api-version=v1.0. Updates to collections in the Data Warehouse are additive in nature and do not break existing scenarios.

Enrollment Activities Collection Released to Beta

The new Enrollment Activities collection is released to beta. You can use this collection to understand how your enrollment is proceeding by viewing the most common failures.

1805

Released May 2018

Correction to device count in Devices collection

A fix has been made to the Devices collection which may lower total device counts that filter by the attribute isDeleted. This drop is a result of the correction and is not an error. For more information regarding the Devices collection, see Reference for device entities.

1801

Released January 2018

Intune Data Warehouse application-only authentication

You can set up an application using Azure Active Directory (Azure AD) and authenticate to the Intune Data Warehouse. For more information see, Intune Data Warehouse application-only authentication.

Azure AD and Intune credential requirements

  • An Intune license is no longer required to be assigned to the user when accessing the Intune Data Warehouse (including the API).

  • The Intune role name has been changed from Reports to Intune data warehouse.

    For more information, see Azure AD and Intune credential requirements.

OData query options

You can use $select as an OData query parameter. The current version supports the following OData query parameters: $filter, $orderby, $select, $skip, and $top. For more information, see OData query options.

New entities in the in Data Warehouse data model

  • The entity, MobileAppDeviceuserInstallStatus, has been added. The MobileAppDeviceUserInstallStatus represents a mobile app install status for a given device and user.
  • The entity, MobileAppInstallStates, has been added. The MobileAppInstallState entity represents the install state for a mobile application after it has been assigned to a group containing devices, users, or both.

1710

Released November 2017

A new entity collection named Current User is limited to currently active user data

The Users entity collection contains all the Azure Active Directory (Azure AD) users with assigned licenses in your enterprise. These records include user states during the data collection period, even if the user has been removed. For example, a user may be added to Intune and then removed during the course of the last month. While this user is not present at the time of the report, the user and state are present in the data. You could create a report that would show the duration of the user's historic presence in your data.

In contrast, the new Current User entity collection only contains users who have not been removed. The Current User entity collection only contains currently active users. For information about the current user entity collection, see Reference for current user entity.

1709

Released October 2017

User device association entity collection added to Intune Data Warehouse data model

You can now build reports and data visualizations using the user device association information that associates user and device entity collections. The data model can be accessed through the Power BI file (PBIX) retrieved from the Data Warehouse Intune page, through the OData endpoint, or by developing a custom client. For more information, see the User Device Association.

New entities in the in Data Warehouse data model

  • The entity, UserDeviceAssociation, added. UserDeviceAssociation contains user device associations in your organization. You can now build reports and data visualizations using the user device association information that associates user and device entity collections.
  • The entity, IntuneManagementExtension, added. IntuneManagementExtension contains entities for mobile devices that track information such as version and installation status.

Next steps