# Intune: Mobile devices connector

The Intune Connector for Mobile Devices allows you to collect additional compliance data from all devices, as well as data from devices on which you cannot install Nexthink Mobile, such as certain bring your own (BYO) devices.

This connector is specifically designed for Android and iOS mobile operating systems. The system uses the operating system's device identifier to match the device imported from Intune with an existing device.

* If a match is found, the existing device is enriched with data from Intune.
* If no match is found, the system imports the device as a new entry.

## Device fields <a href="#connectorforcitrixdaas-devicefields" id="connectorforcitrixdaas-devicefields"></a>

The connector for Intune: Mobile devices imports the following device fields.

| Nexthink Field                             | Description                                                                                                                                                      |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `mobile_devices`                           | Contains information about mobile devices, including hardware specifications, operating system details, and Nexthink application data.                           |
| `device_performance.mobile_battery_events` | Stores battery-related metrics and attributes for mobile devices, such as battery level, battery health, and power consumption metrics.                          |
| `device_performance.mobile_events`         | Captures performance metrics and attributes related to mobile devices, including disk storage usage and RAM capacity.                                            |
| `connectivity.mobile_events`               | Stores connectivity-related metrics and attributes for mobile devices, such as network type, signal strength, and data usage over Wi-Fi or cellular connections. |

Additionally, the connector populates the following fields in the `mobile_devices.governance` grouping, even for devices that have Nexthink Mobile installed:

|                    |                                                                                                                         |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| `compliance_state` | The current compliance status of the device compared to the organization's compliance policies, as reported by the UEM. |
| `is_encrypted`     | True if device storage is encrypted, as reported by the UEM.                                                            |
| `enrollment_type`  | The enrollment method used when the device was registered in UEM.                                                       |
| `last_synced`      | The last time the UEM successfully synced data with the device.                                                         |
| `name`             | The device name as assigned in the UEM system.                                                                          |
| `ownership_type`   | Indicates the ownership category defined by the UEM.                                                                    |
| `is_supervised`    | Indicates if the device is supervised by the UEM, allowing deeper management capabilities.                              |

For Android devices, the connector also populates the following fields in the `connectivity.events` table:

| Field        | Description                                                                               |
| ------------ | ----------------------------------------------------------------------------------------- |
| `wifi.bssid` | The physical address of the access point or wireless router used to connect to the Wi-Fi. |
| `wifi.ssid`  | The Wi-Fi network name (SSID).                                                            |

## Prerequisite <a href="#configuring-the-connector-credentials" id="configuring-the-connector-credentials"></a>

The connector requires the following permission to be granted in Intune:

* `DeviceManagementManagedDevices.Read.All`

## Configuring the Connector <a href="#configuring-the-connector-credentials" id="configuring-the-connector-credentials"></a>

Navigate to the **Administration** module and select **Connector credentials** from the **Integrations** section. Create new Connector Credentials for Intune. See the [connector-credentials](https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/connector-credentials "mention") documentation for more information.

{% hint style="warning" %}
Nexthink retrieves Intune data through the Microsoft Graph API. Ensure to fill the following input fields accordingly:

* **URL address**: `https://graph.microsoft.com`
* **Access token URL**: `https://login.microsoftonline.com/<TENANT_ID>/oauth2/v2.0/token`
* **Scope**: `https://graph.microsoft.com/.default`
  {% endhint %}

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FWcZ6Omcn3Cr4pNTTXbSV%2Fimage.png?alt=media&#x26;token=c727cd18-9289-42fb-86fd-3662e5999852" alt="" width="441"><figcaption></figcaption></figure>

## Configuring the connector for Intune: Mobile devices

{% stepper %}
{% step %}
Go to **Administration** > **Inbound connectors**.
{% endstep %}

{% step %}
Select **New connector** button in the top-right corner of the page.
{% endstep %}

{% step %}
Select **Intune: Mobile devices** from the list of connectors.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-57e6b16fb79d352b5afdf12fe4237cfdb422e6ff%2Finbound-connectors.png?alt=media" alt="Creating a new inbound connector" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
On the **General** tab:

* Provide a **name** and **description** for your Intune connector. The **NQL ID** is generated automatically.
* In the **Schedule** section, set how often the connector will fetch data from Intune.
* In the **Connection** section, select the Intune credentials you have configured in a previous step.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FqBsTGFNWPvZH8XEdrqsb%2Fimage.png?alt=media&#x26;token=eda61d24-a340-409b-9ca2-3ad070da612a" alt="General tab" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
On the **Parameters** tab:

* Select the **Start date** to determine which devices to include. Only devices synced on or after this date will be imported.
* Optionally, select the **Device category** from Intune to define which devices to import.
* Specify **Device ownership type** to include company-owned, personally-owned or both device types.
* Specify the **Operating system** (iOS, Android, or both) of devices you want to import.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2F1pY8Mw1UOVDftQucZtwK%2Fimage.png?alt=media&#x26;token=4a2bb63a-5a85-4d63-8d91-af6a03cd7969" alt="Parameters tab" width="563"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

Once you save the connector settings, the system immediately synchronizes with Intune and continues to synchronize based on the schedule defined in the **General** tab.

## Test results panel

{% hint style="info" %}
The **Test results** panel is available only for supported connectors. Connector availability also depends on your license.
{% endhint %}

Use the **Test results** panel on the right side to run the connector with real data on demand, and inspect responses and errors. The test panel helps with faster debugging and validation during setup, and also with more reliable mappings with less trial and error.

Select the **Run test** button to call the API, and validate the credentials and check connectivity to the targeted endpoint.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FeBPC3oyWxuog3Xw2SK8M%2F7eRFKKyolDohcdKm.png?alt=media&#x26;token=a4134835-480b-4a03-a4a5-27e4c3c9cf18" alt=""><figcaption></figcaption></figure>

Besides basic information, such as the response status code and time, the panel also shows a sample record of the response at the bottom.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FI4IxueEsH60Pl3NQpjF0%2FHwklwWjD3Ud5ZXPC.png?alt=media&#x26;token=85b6123d-b40e-4085-871e-bc17232c8a15" alt="" width="316"><figcaption></figcaption></figure>

In the event of an error, the system displays the API response to aid in diagnosing the issue.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FKwqz92TxPeBl3QWqbKNt%2F9kAwIQi3M5gG7Y0H.png?alt=media&#x26;token=eeb306f0-d2b8-441b-a105-1bcd708a2d7c" alt="" width="309"><figcaption></figcaption></figure>