Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
In Microsoft Intune, use the properties catalog to collect device properties—including hardware details, configuration data, and application signals—from managed Windows devices.
For example, you can:
- Discover local AI agents, like OpenClaw, running on your Windows devices.
- Collect selected Windows registry key values from managed Windows devices, such as configuration settings, application state, or security posture signals.
- Get the BIOS version and TPM status to identify devices that might need firmware updates or aren't compliant with security policies.
- Identify devices that lack encryption, which might violate security policies.
- Identify devices that need to be replaced based on hardware properties, like disk size or memory.
- Detect outdated firmware or hardware that could expose vulnerabilities.
- Collect battery health information to help monitor device performance and lifespan.
- Retrieve network adapter configurations to troubleshoot connectivity issues.
This visibility helps you make informed decisions about device compliance, lifecycle management, and troubleshooting.
In this article, you'll learn how to create a properties catalog policy, view the collected data, and explore the available hardware properties. After creating a profile, you can assign it to your Windows devices.
Prerequisites
Device platform requirements
This feature supports Windows devices only.
On Android and Apple devices, device properties are collected automatically.
Device configuration requirements
This feature supports devices that are:
- Managed by Intune
- Co-managed (Intune + Configuration Manager)
- Microsoft Entra joined
- Microsoft Entra hybrid joined
Roles requirements
Role requirements vary based on the tasks being performed.
To configure the properties catalog policy, use an account with at least one of the following Intune roles:
- Policy and Profile Manager
- A custom role that includes the permissions:
- Organization/Read and Managed Devices/Read — Required for device visibility.
- Device configurations/Create, Read, Assign — Required to create and assign the data collection policy.
To view the collected data, use an account with the permission Managed Devices/Read.
Available and required properties
You can collect the following properties. To learn more about the different properties, see Intune Data Platform Schema.
When you create the policy, select any of the following property categories to collect. The required properties are automatically collected when you collect any property in that category.
| Category | Required properties |
|---|---|
| Application Properties | App Name App Version Architectures Install Scope Install Scope Platform User ID Install Scope User ID Publisher |
| Battery | Instance Name |
| Bios Info | Bios Name Software Element ID Software Element State Target Operating System |
| CPU | Processor ID |
| Disk Drive | Drive ID |
| Encryptable Volume | Volume ID |
| Local AI Agent | Agent Name Install Location Install Scope Microsoft recommends collecting Host process, as OpenClaw can run in different process names, like node.exe, wsl.exe, etc. |
| Logical Drive | Drive Identifier |
| Memory Info | — |
| Network Adapter | Identifier |
| OS Version | — |
| Sim Info | Windows eSIM ID |
| Registry | Registry keys |
| System Enclosure | Serial Number |
| System Info | — |
| Time | — |
| TPM | — |
| Video Controller | Identifier |
| Windows QFE | Hot Fix ID |
Create the collection policy
Use the following steps to create a properties catalog profile and assign it to your Windows devices.
In the Microsoft Intune admin center, select Devices > Windows.
Under Manage devices, select Configuration > Create > New Policy.
Select the following properties and select Create:
- Platform: Select Windows 10 and later.
- Profile type: Select Properties catalog.
In Basics, enter the following properties and select Next:
- Name: Enter a descriptive name for the new profile.
- Description: Enter a description for the profile. This setting is optional, but recommended.
Select Add properties and select the properties you want to collect. You can select multiple properties from multiple categories.
Some required properties are automatically added. For a list, see Required properties.
Select Next.
Optional. In Scope (Tags), select any scope tags you want to assign to the profile. To learn more about scope tags, see Use scope tags for distributed IT.
Select Next.
In Assignments, select the groups that receive this profile. For more information on assigning profiles, see Assign policies in Microsoft Intune.
Select Next.
In Review + create, review your settings, and select Create.
When you select Create, the profile is assigned to the groups you specified. The profile is also created and shown in the list. The next time each device checks in with the Intune service, the policy applies.
Note
It can take up to 24 hours for the initial collection of inventory data.
View collected data
Use the following steps to view the collected device inventory information:
- In the Microsoft Intune admin center, select Devices > Windows.
- From the devices list, select a device.
- Under Tools, select Device Inventory.
- Select a category to view the collected information.
Feature details and usage
Local AI agent
Helps you discover OpenClaw running on your Windows devices. After you deploy the properties catalog policy and start collecting data, the next steps are:
- Use Device Query to view devices with a Local AI Agent.
- Use the Local AI Agent Baseline - OpenClaw to block users from using OpenClaw.
Registry key inventory
Lets you collect selected Windows registry data through the properties catalog for configuration visibility and troubleshooting. Here are some important details about this feature:
- Supported collection methods include a single value, all values directly under a key (non-recursive), and the same value across immediate subkeys.
- Registry key inventory isn't intended to collect sensitive or confidential values and includes detection logic to help prevent potentially sensitive values from being ingested. If a value is flagged as potentially sensitive, it isn't collected.
- To view collected registry data, use Device Inventory.
- Initial release limitations include HKLM-only collection and enforced value (6KB) and per-device (100 registry keys) collection limits.
Stop collecting properties
You can stop (delete) the collection of properties only at the category level. To stop collecting properties, go to the properties catalog profile, and remove the collection for every property in the category.
Note
If you delete a properties catalog policy, you can see the last-collected data in Device Inventory for up to 28 days.
Troubleshooting
To troubleshoot issues with the properties catalog, review the client logs at C:\Program Files\Microsoft Device Inventory Agent\Logs. You can also collect the logs by using the Device Action: Collect Diagnostics.