How to block creation of personal devices in CMDB coming from InTune integration

Mark Tuffey · ‎09-07-2022

We have our Service Graph Connector for Microsoft InTune set up successfully. However, we have devices in InTune that are not corporate assets that are being bought over during our InTune imports and created as a CI. In the InTune import table sets here are two identifications, "Company" and "Personal" under the field ManagedDeviceOwnerType. Is there way to stop any device with a manageddeviceownertype of "personal" from being created as a CI in our CMDB?

Cheers

Mark

Report Inappropriate Content · ‎09-07-2022

Yes there is. The easiest way would be to install the IntegrationHub ETL application and then modify the conditional mapping to the computer class as below:

This is in step 3 Map Data to CMDB and Add Relationships and can be access via the Edit Class button on the Computer class.

This will prevent any devices that have u_manageddeviceownertype != Company from being inserted or updated in the CMDB.

View solution in original post

Sandeep Dhungan · ‎08-03-2023

Hi Mark ,

If you or anyone is still looking for a solution, please see below instruction that i implemented when we first started intune sync . Please note for some reason this got overwritten somehow during our last upgrade.

This is what i did to make it work again.

1. go to flow designer
2. go to actions

3. select application type as Service graph Connector for Microsoft intune

4. open mobileDevices or computers (whichever or both if you want to only sync corporate devices)

5. On the Inputs, there is nextlink which can be edited. Click the below to close the Data

6. Click the down arrow

7. Update below at the end of default value:

and managedDeviceOwnerType eq 'company'

The default value will look like this

8. Hit save and publish

9. remove all the junk data from handheld computing or computer table.
10. Run the Intune schedule

Thanks,

SD

aliceal · ‎07-14-2025

This worked for me, however, it was in Data Streams and not Actions for me. (Step 2). I don't know if that's just a change in the past 2 years or not.