OMA-URI policies in Intune
Custom configuration profiles let you set configuration service provider (CSP) paths that the Intune UI doesn't expose. Most failures come down to the URI, the data type or the value format.
Anatomy of an OMA-URI setting
An OMA-URI is a path into a device management tree, for example:
./Vendor/MSFT/Policy/Config/ApplicationManagement/RequirePrivateStoreOnly
Each segment descends the CSP tree. The path must match a node the platform actually exposes; an unknown node is silently ignored or rejected at apply time.
Data types
| Type | Use for |
|---|---|
| String | Text values, including XML payloads. |
| Integer | Whole numbers, often enums such as 0/1. |
| Boolean | True/false toggles. |
| Base64 | Binary or encoded content. |
Sending a string where the CSP expects an integer is one of the most common causes of a profile that reports success but has no effect.
Common mistakes
- Using the wrong data type for a CSP node.
- Setting an integer enum with a value outside the documented range.
- Referencing a CSP that requires a different Windows edition or build.
- Wrapping an XML value as Base64 when the node expects a plain string.
Related tool
The OMA-URI Policy Builder validates URI structure, data type and value format before you assign a policy. It is on the roadmap.