Connecting Multiple Object Schemas
You may be using multiple applications of Pio, or you may already have object schemas and now you need to relate them with the new data imported by our apps. Then the question “Is it possible to link/relate/connect different object schemas?” arises. One example use case could be as follows:
Use Case:
As a Jira Admin like to show the Entra ID (Azure AD) user and the owned devices from Intune in a custom field so that the helpdeks agents can analyze/respond to the ticket faster.
On this page, we will provide an example answer to the question “How to connect 2 object schemas?”
This document doesn’t cover the scenario for Intune and Okta mapping. We recommend the following setup for Intune and Okta:
Instructions for Intune and Entra ID
Install Azure AD (Microsoft Entra ID) Importer for JSM Assets from the marketplace.
Watch the demo.
Configure and import your organizational data (i.e. Users and Managers)
Make sure that you enabled Object Schema Sharing at the time of the schema creation step.
Set the scheduling for automated replication.
Install Microsoft Intune Importer for JSM Assets from the marketplace.
Watch the demo.
Configure your source, destination.
Build the new object schema structure. (how to)
Reminder: don’t import the Intune data yet.
Select the Assets menu and the Object Schema that you used for Intune.
Select the “Managed Devices” object type from the Schema Tree on the left side.
 |
|---|
Select the “Attributes” tab for the object type.
|
|---|
Make sure that you don’t have any data imported. If you have, delete the objects for “Managed Devices”. Since you will change the mapping in the following steps, Assets expects the attribute to be empty.
Click on the “Type Value” and write “Users”. You will find all the object types called “Users” from other object schemas. Select the one from your Azure AD object schema. And click “Update”.
|
|---|
Now, new imports will create a relation automatically between Managed Devices in Intune schema and Users in Azure AD schema.
Please note that the Users object type in Intune object schema will not be updated after the change. For that reason, you can remove the object type.
Import your Intune data (i.e. Managed Devices, Models, etc.)
Set the scheduling for automated replication.
We hope this was helpful. Like, comment, and share with your colleagues …
Instructions for Jamf and Entra ID
Intune and Jamf have different object schemas. They use different unique identifiers. For that reason, while connecting Jamf to Entra ID, the following controls should be done.
Currently, the mapping AQL from Jamf Computers to Jamf Users is set to:
"Username" = ${username}
since it is designed to map only to Jamf Users.
You can find the AQL on the following path:
> Assets
> Your schema
> Schema settings
> Import tab
> Jamf import configuration
> Edit mapping
> Edit attribute mapping (for Computers object type)
> User attribute (of Computer object type)
> AQL mapping
On the other hand, Entra ID (Azure AD) doesn’t have an attribute called Username; this mapping will not be able to find any record to match.
Now, please check your Username values in Jamf. If the Jamf Username is an email address, then the AQL query needs to be updated as:
"E-mail Address" = ${username}
because the attribute name of Entra ID Users is "E-mail Address". If the Username attribute is not an email address, then it needs to be updated to an email address. Please ask the Jamf Admin to update the values in Jamf. Otherwise, mapping is not possible.