Working with Intune in Microsoft Graph
APIs under the
/beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.
Note: The Microsoft Graph API for Intune requires an active Intune license for the tenant.
The Microsoft Graph API for Intune enables programmatic access to Intune information for your tenant; the API performs the same Intune operations as those available through the Azure Portal.
For mobile device management (MDM) scenarios, the Microsoft Graph API for Intune supports standalone deployments; Intune hybrid deployments are not supported.
All Microsoft Graph beta APIs for Intune are tested and validated by the Intune team before they're deployed. For the latest API changes, see the changelog.
Using the Microsoft Graph API for Intune
Intune provides data into Microsoft Graph in the same way that other cloud services do, with rich entity information and relationship navigation. Use Microsoft Graph to combine information from other services and Intune to build rich cross-service applications for IT professionals or end users.
The following example shows how you can determine whether an application is installed on a user's device:
Get from Azure Active Directory a list of devices registered to a user:
Then view the list of applications for your tenant:
Take the ID from the application and determine the installation state for the application (and therefore user):
Using Microsoft Graph permissions
Microsoft Graph controls access to resources via permissions. As a developer, you must specify the permissions you need to access Intune resources. Typically, you specify the permissions in the Azure Active Directory portal. For more information, see Microsoft Graph permissions reference.
Interaction between Microsoft Graph APIs for Windows updates
Microsoft Graph includes two sets of APIs that you can use to manage Windows updates:
You can use either API to manage Windows updates; however, these two APIs are not compatible with each other. Each can overwrite the configurations made by the other without providing visibility into that action. Use of both APIs to manage updates can result in unexpected behaviors, including what appears to be temporary configurations for update deployments that are canceled or modified without an identified cause.
Find out about the latest new features and updates for this API set.