Forum Discussion
Add custom attributes to users (or devices) to map hardware peripherals
Hello everyone,
I am seeking some help, guidance or suggestions with the following situation.
We are looking for a solution that could map peripherals (such as monitors) to a user or a device. Once we have that info, we will utilize an additional tool to extend our visibility over the assets & assignments.
I reviewed a few documentations and videos about potential solutions, and I just want to know if that's possible or I should not invest time on it any longer.
The scope is the following:
1. We've collected information about connected monitors using Intune Script detection. That's perfect. It already maps devices with monitor's serial numbers and other details.
2. Export in CSV is fine (although, the data is not a 100% accurate, we have an internal data base that we can compare).
3. Now, how can we properly map that data to the cloud objects? What the best approach is? Logically, the monitors should be added to the devices, but Intune Custom Attributes are not easily populated/managed (?). On the other hand, Entra AD is capable of managing such expressions and overall has better capabilities (or am I wrong?) when it comes to operating with cloud objects.
I am really looking for a human response; more of a knowledge share. I'd appreciate if someone shares their experience with similar scenarios. :)
I apologise in advance if my question is not in the right section.
Docs:
https://learn.microsoft.com/en-us/graph/extensibility-overview?tabs=http
https://www.reddit.com/r/AZURE/comments/1e5z3kv/add_customextension_attribute_in_entra_id/
https://www.reddit.com/r/AZURE/comments/1dz4cru/comment/lcdf2ev/?context=3&share_id=UqZR0m9s-9SWiHOiVwwAM&utm_content=1&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=1
https://www.youtube.com/watch?v=kBm-fjqg0PU
https://www.youtube.com/watch?v=LHXfFoygiOA
Thanks :)
1 Reply
Yes, this is possible, and I would recommend Microsoft Graph schema extensions or open extensions rather than trying to force everything into Intune custom attributes.
Recommended approach
Keep Intune as your data collection layer. Continue collecting monitor serial numbers, manufacturers, models, and associated device IDs.
Use Microsoft Graph API to update cloud objects with the collected information.
Use Entra ID schema extensions if you want custom attributes attached to device objects.
Consider an external asset database if you need to manage multiple monitors per device, historical assignments, and user-to-peripheral relationships.
Important consideration
Entra ID is not a complete hardware asset management system. A device can have multiple monitors, docking stations, and other peripherals. Storing all this information in a single custom attribute can become difficult to maintain.
My recommendation:
Intune: Hardware discovery.
Microsoft Graph: Automation and synchronization.
External database: Peripheral inventory and assignments.
Entra ID: Store only the relevant reference or summary information.
Documentation: Microsoft Graph extensibility overview .
Bottom line: You don't need to abandon the idea. Graph extensions provide a viable way to associate custom information with Entra objects, but I'd keep the detailed peripheral inventory outside Entra ID.
