Intune connector
Connects to an Intune application and collects inventory and usage data. For information on the type of data collected by the Intune connector, please refer to the Intune column of the table on Management groups rules page.
The below configuration procedure assumes you already have an Intune subscription, and are able to populate the connector with information available in an Enterprise Application in your Azure Active Directory (AAD) Console.
Prerequisites
Before adding a new Intune connector, you will need the following information from an Enterprise Application created in your AAD console:
Azure cloud instance URL (optional) if this is not supplied then AzurePublic is used as a default
Azure Tenant ID, available in the Overview node of your AAD console (see opposite)
The registered application clientID (a string representing a GUID)
A client secret value that has been created for your chosen Enterprise Application.
Prepare an AAD application
In your Azure Active Directory console, go to the Enterprise applications node and click New application.
You need to create a non-gallery application, in the version of AAD we're using this is done by clicking the Create your own application button.
Provide a name for the application. The application name is not important but should suggest the application relates to platform connector. For example Tachyon Intune Connector, click Add in the bottom left of the screen.
In the Overviewtab, copy theObject ID (called Client Id in Tachyon) and the Application ID (called Tenant Id in Tachyon) values as these will be required for the connector.
Click the App registrations node of AAD. Click on the application name for the application(s) listed, you will need to navigate back to the AAD blade.
Note
You may need to change the tab to All Applications to see the new application.
Add permissions
Click on the API permissions node under the Manage node, then click Add a permission.
Click on the Microsoft Graph tile and then click on Application permissions.
A long list of API permissions will be shown, scroll through them and check as appropriate using the following table, then, click Add permissions.
Group | Permission |
|---|---|
DeviceManagementApps | Read.All |
DeviceManagementManagedDevices | Read.All |
User | Read.All |
Click Grant admin consent for <organization>, where <organization> is the Organization you set when you created your Intune instance.
This means that as an administrator for your organization, you're consenting that the users of the application would want to use these permissions.
Add a client secret
Click on the Certificates & secrets node and then click on the New client secret button.
The Add a client secret form will open, add a Description and select an expiry from the Expires radio buttons and then click Add.
Copy the new client secret value and save it, as you won't be able to retrieve it after you perform another operation or leave this blade.
Warning
If you do not copy the Value at this point, when you navigate away from the Certificates & secrets screen you will be unable to copy it again. This means that you will have to delete the Secret and recreate it.
Configuring the Intune connector
These instructions show how to create an Intune connector in the Settings application.
Adding, testing and running an Intune connector
These are the steps to add, test and run an Intune connector.
Adding an Intune connector
In the Tachyon portal portal, navigate to Settings→Configuration→Connectors.
Click on the Add button.
In the Add connector popup, select the Intune type.
In Connector name, enter a logical name for this connector. In our example we choose the name Intune Inventory.
Azure Cloud Instance can be set to the URL for your Intune implementation. If you leave this field blank AzurePublic is used as a default, for the AzureCloudInstance reference see https://learn.microsoft.com/en-us/dotnet/api/microsoft.identity.client.azurecloudinstance?view=msal-dotnet-latest
In Azure Tenant Id, enter your Azure tenant ID, available in the Overviewnode of your AAD console.
Client Id this should be set to your registered application clientID.
Client Secret this should be set to the specific client secret value that has been created for your chosen Enterprise Application
Run Consolidation Reports - check this checkbox if you want the consolidation reports running automatically after this connector has been synchronized.
Click Add.
The new connector has now been added and a new action that can be used to run the connector has been created in the background, called Sync Data - Intune Inventory.
Testing an Intune connector
Select the Intune connector by checking the box at the left-hand end of its entry in the Connectors table.
Click the Test button.
The Test status column for the connector will display a clock icon
indicating that the test has been queued for executing.
If the test succeeds, Test status will display a check icon
and the Last tested column will display the date and time the test succeeded.
If the test fails, the Test status will display a failed icon
and you'll need to check the details you entered for the connector.
If the test succeeds, you can proceed to run the connector to populate an inventory repository.
Running an Intune connector
Click the Execute button.
In the Execute action popup subsequently displayed, use the Repository menu to select the inventory repository you want to populate.
Once the repository has been selected, you can then select the action to run. In the case of inventory repositories, the actions will be restricted to inventory related actions. For a connector, you will be looking for an action with the form Sync Data - <connector name>.
Select whether you want to clear any existing data in the repository by checking the Clean sync checkbox.
Click Execute button in the Execute action popup to start the sync.
When the sync starts, a number of actions are queued to be performed on the selected repository. To check the progress of the sync actions:
Navigate to the Monitoring→Process log page.
Here, you can see the sequence of actions that have been queued for the selected repository related to the Sync Data action selected.
When each action has finished running, you'll see a check icon
appear in the Status column if it succeeds or a failed icon
if it fails.
Once all the actions have succeeded, you can check the results. To do this:
Navigate to the Monitoring→Sync log page.
This displays the items that have been added to the selected repository as a result of running the sync.
The Intune connector parameters
The following fields are available in the Add connector and Edit connector popups when the Intune Connector type is selected, as shown in the picture opposite:
Field | Description |
|---|---|
Connector type | Shows the connector type: Intune. |
Repository type | Shows which type of repository the connector works with. For the Intune Connector type this is always Inventory. |
Connector name | Here you set the logical name for the connector. TipYou should use a naming convention for connector names: <connector type> <scope> <RCR> Scope describes where data is coming from or what it's being used for. For example Demo, Test, Lab, Q2 Audit. Include RCR in the name if you have enabled Run Consolidation Reports. |
Azure Cloud Instance | Azure cloud instance URL (optional) if this is not supplied the AzurePublic is used as a default. |
Tenant Id | Azure tenant ID, available in the Overview node of your AAD console. |
Client Id | The registered application clientID. |
Client Secret | A client secret value that has been created for your chosen Enterprise Application. |
Run Consolidation Reports | Check the Run Consolidation Reports checkbox if you want consolidation actions to be processed each time the Sync Data action is executed for the connector. This can lead to unnecessary processing if you enable this on more than one connector. The recommended method of processing consolidation actions is to schedule the action Generate Report - Basic Inventory Consolidation to execute after the Sync Data actions have run for all connectors. This will execute the remaining consolidation actions. Alternatively check the Run Consolidation Reports checkbox on one of your connectors. You can view action processes in Settings→Process log. |
