Intune Connector

The following is not supported in Tenable FedRAMP Moderate environments. For more information, see the Tenable FedRAMP Product Offering.

Microsoft Intune is a cloud-based unified endpoint management platform that empowers IT to manage, assess, and protect apps and devices.

Tip: For more information on how third-party integrations work, see Connectors.

Connector Details

Details Description

Supported products

Microsoft Intune

Category

Asset Inventory, Endpoint Security

Ingested data Assets

Ingested Asset Classes

Device

Integration type

UNI directional (data is transferred from the connector to Tenable Exposure Management in one direction)

Supported version and type

SaaS (latest)

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

    1. In the Microsoft Azure portal, navigate to App registrations.

    2. Click New Registration.

      The Register an application page appears.

    3. Configure the following application settings:

      • Name — Type a descriptive name for your application (e.g., "Intune-Integration").

      • Supported account types — Choose Accounts in this organizational directory only.

    4. Click Register to create the application.

    1. Navigate to the Application Overview page for the application you created and registered in Microsoft Azure.

    2. Copy and save the Application (Client) ID and Directory (Tenant) ID values for use within Tenable Exposure Management.

    1. In the Microsoft Azure portal, navigate to Certificates & Secrets.

    2. In the Client secrets section, click New Client Secret.

    3. In the Description text box, type a brief description of the client secret.

    4. In the Expires section, select the period after which you want the secret to expire.

    5. Click Add.

    6. Copy and save the client secret value for use within Tenable Exposure Management.

  • To access Intune device data, your application requires specific permissions.

    1. In the Microsoft Azure portal, navigate to API Permissions.

    2. Click Add a permission > Microsoft Graph.

      The Request API Permissions window appears.

    3. Click Application permissions.

    4. Configure the following group permissions:

      • DeviceManagementManagedDevices.Read.All

      • DeviceManagementConfiguration.Read.All

      • DeviceManagementApps.Read.All

    5. Click Grant admin consent for [Your Organization].

      A confirmation window appears.

    6. Click Confirm.

      Note: If you do not have admin privileges, your administrator must grant consent.

Add a Connector

To add a new connector:

  1. In the left navigation menu, click Connectors.

    The Connectors page appears.

  2. In the upper-right corner, click Add new connector.

    The Connector Library appears.

  3. In the search box, type the name of the connector.

  4. On the tile for the connector, click Connect.

    The connector configuration options appear.

Configure the Connector

To configure the connector:

  1. (Optional) In the Connector's Name text box, type a descriptive name for the connector.

  2. (Optional) To use a preconfigured on-prem connector to connect to this connector, from the Gateway drop-down, select the on-prem connector you want to use for the connector. Otherwise, select Don't use gateway.

    Note: For information about configuring a gateway, see Tenable On-Prem Connector.

  3. Enter the credentials you generated earlier (FQDN, API Key, and API ID).

  4. Data pulling configuration: This configuration has dynamic settings tailored to the specific connector and integration type. Below are the configurations relevant to this connector.

    • In the Asset Retention text box, type the number of days after which you want assets to be removed from Tenable Exposure Management. If an asset has not been detected or updated within the specified number of days, it is automatically removed from the application, ensuring your asset inventory is current and relevant.

      Tip: For more information, see Asset Retention.

  1. Click the Test Connectivity button to verify that VTenable Exposure Management can connect to your connector instance.

    • In the Test connectivity section, click the Test Connectivity button to verify that Tenable Exposure Management can connect to your connector instance.

      • A successful connectivity test confirms that the platform can connect to the connector instance. It does not, however, guarantee that the synchronization process will succeed, as additional syncing or processing issues may arise.

      • If the connectivity test fails, an error message with details about the issue appears. Click Show tests for more information about the exact error.

  2. In the Connector scheduling section, configure the time and day(s) on which you want connector syncs to occur.

    Tip: For more information, see Connector Scheduling.

  3. Click Create. Tenable Exposure Management begins syncing the connector. The sync can take some time to complete.

  4. To confirm the sync is complete, do the following:

Locate Connector Assets in Tenable Exposure Management

As the connector discovers assets, Tenable Exposure Management ingests those devices for reporting.

To view assets by connector:

  1. In Tenable Exposure Management, navigate to the Assets page.

  2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view assets.

    The asset list updates to show only assets from the selected connector.

  3. Click on any asset to view Asset Details.

Data Mapping

Exposure Management integrates with the connector via API to retrieve relevant weakness and asset data, which is then mapped into the Exposure Management system. The following tables outline how fields and their values are mapped from the connector to Exposure Management.

Device Mapping

Tenable Exposure Management UI Field

Intune Field
Unique Identifier id

Asset - External Identifier or

Asset - Provider Identifier

 azureADDeviceId
Asset - Name deviceName
Asset - Operating Systems operatingSystem
Asset - MAC Addresses ethernetMacAddress or wiFiMacAddress
Asset - First Observation Date enrolledDateTime
Asset - Last Observed At lastSyncDateTime

Asset - External Tags

  • deviceCategoryDisplayName

  • complianceState

  • deviceRegistrationState

  • managedDeviceOwnerType
Asset Custom Attributes

osVersion

Status Update Mechanisms

Every day, Tenable Exposure Management syncs with the vendor's platform to receive updates on existing findings and assets and to retrieve new ones (if any were added).

The table below describes how the status update mechanism works in the connector for findings and assets ingested into Tenable Exposure Management.

Update Type in Exposure Management

Mechanism (When?)

Archiving Assets

  • Asset that appears in Tenable Exposure Management and isn't returned on the next connector's sync.

  • Asset not seen for X days according to "Last Seen". See Asset Retention
Note: Updates on the vendor side are reflected in Tenable Exposure Management only when the next scheduled connector sync time is complete (once a day).

Uniqueness Criteria

Tenable Exposure Management uses defined uniqueness criteria to determine whether an ingested asset or finding should be recognized as a distinct record. These criteria help define how assets and findings are identified and counted from each connector.

Tip:  Read all about Third-Party Data Deduplication in Tenable Exposure Management .

The uniqueness criteria for this connector are as follows:

Data

Uniqueness Criteria

Asset

asset - id

API Endpoints in Use

Base URL: https://management.azure.com

API

Use in Tenable Exposure Management

 Requested Permissions

POST - https://login.microsoftonline.com/{{tenant_id}}/oauth2/v2.0/token

Authentication

 Read
GET - https://graph.microsoft.com/v1.0/deviceManagement/managedDevices

Managed Devices - Devices

 Read

Support Limitations and Expected Behavior

This section outlines any irregularities, expected behaviors, or limitations related to integration of the connector and Exposure Management. It also highlights details about ingested and non-ingested data to clarify data handling and functionality within this integration.

Microsoft Intune may include assets sourced from Tenable via its own Tenable adapter. To prevent sync loops—where assets originating from Tenable are re-ingested back into Tenable — the connector filters out any device whose only associated adapters are Tenable-related.

Data Validation

This section shows how to validate and compare data between Tenable Exposure Management and the Microsoft Intune.

Asset Data Validation

For each unique asset - id in Microsoft Intune, the Intune connector creates an asset in Exposure Management.

Objective: Ensure the number of assets (devices) in Microsoft Intune aligns with the number of devices displayed in Tenable Exposure Management.

In the Microsoft Azure portal:

  1. Navigate to the All Devices tab.

  2. Apply filters to exclude archived devices (based on your configuration in Asset Retention).

In Tenable Exposure Management:

  1. Locate your connector assets.

  2. Compare the total number of assets between Microsoft Intune and Tenable Exposure Management.

Expected outcome: The total numbers returned in Microsoft Intune and Exposure Management should match.

If an asset is not visible in Exposure Management, check the following conditions:

If an asset meets any of the following conditions, it will not appear in Exposure Management.

  • Archived based on the last observed date (field last_seen).

  • Asset isn’t expected to be fetched because it is already part of Tenable-Adapters.

    Tip: To learn more on how assets are archived, see Status Update Mechanisms.