Differentiating imported assets for multiple clients / tenants

[Michael Fileti]

I work at an IT Managed Service Provider where we manage many instances of Jamf and Intune for many different external organizations. We can set up separate job executions to discover assets from these multiple instances of Jamf & Intune, however we need a way to identify which asset came from which job execution so we can tie the discovered assets to a specific organization.

Ultimately we would be looking to be able to run reports for each organization in Assets Data Manager and eventually import those assets into an object schema, but I don't know how we will be able to tell that an asset belongs to one specific organization or another when being viewed across reports/object imports.

Any suggestions on how that would be possible?

[Karyn Findlay]

Hi @Michael Fileti 

In addition to aggregating the jobs into one view of Jamf and one for InTune job, that @Hun Chan talks about below, I believe you're asking how to identify in the larger picture which devices come what which organization from the analysis screen.

If this is the case, you could create a local Computed Dictionary called Organization and potentially use an identifier from one of those sources. 

For example: Lets say you have Org 1, Org 2 and Org 3.  Data received from InTune could includes email address and you could map all the Org 1 users email addresses to the Org 1  Computed Dictionary group.  This will then allow you to filter by Computed Dictionary = Org 1 to see only their devices.  The problem here is that each user will need to be done manually.

Other alternate attributes from these sources like: 

• PONumber
• IP Addresses

You many have another data source where you have a device associated with a Location or Domain and you could use one of these fields to drive the organization.

Another option, which would need to be an on-going task would be to use Tagging.  Have a Saved Search where email address contains "@org1.com" and tag will the results as Org1 - you can then use this tag in searches.  The on-going piece, would be when new team members start, you'd need to tag new users to each Org.  

If we've missed the mark with your question, please let us know.

Regards,
Karyn
Product Manager | Jira Service Management | Assets

[Hun Chan]

Hi Michael,

Let's use an example here: You have four  "base" JAMF jobs and three Intune "base" jobs that you have setup and executed via the adapter client. Each of the Intune job and the JAMF job will have a data source name associated with it.

You will then configure one Data Source Aggregate adapter to combine the four JAMF jobs and configure a second Data Source Aggregate adapter to combine the three Intune jobs.

One thing to note when using the data source aggregate adapter to combine the jobs is that:

1. the number of attributes in the "base" jobs must be equal.

2. It must be in the same order and

3. It must be of the same data type. 

That is because the data source aggregate adapter uses UNION SQL statement.

Once you have successfully executed the data source aggregate job(s), in the Data Manager mapping process for the aggregate jobs, you will need to ensure that the source table name column is mapped to a destination attribute. This will tell you which data source or instance the asset/record originates from when analysing the data.

Below is a brief set of information on the data source aggregate adapter.

https://support.atlassian.com/jira-service-management-cloud/docs/data-manager-data-source-aggregate-adapter/ 

Regards,

Hun

[Mark Edwards]

Hi @Mich

Just to check, are you using the "Data Source Aggregation" job?

https://support.atlassian.com/jira-service-management-cloud/docs/data-manager-data-source-aggregate-adapter/ 

I am checking with the team to when you use this job if there is an indicator of where the data came from.

Thanks

Mark