Paste the policy.
Know what it does.
Look up a Windows Policy CSP path, setting name, or Intune task. Get the correct OMA-URI, scope, format, values, checks, and Microsoft reference.
Verified CSP records
Loading CSP records…
Validate the full OMA-URI contract
A Windows CSP setting is more than a path. Successful Intune deployment depends on the policy area, node name, device or user scope, expected data type, allowed values, Windows edition, and release applicability. A syntactically valid custom profile can still be ignored or rejected when any one of those boundaries is wrong.
Use this lookup to identify the canonical OMA-URI and the deployment facts that must travel with it. Compare the result with the current Microsoft Policy CSP documentation, because settings can gain or lose applicability as Windows and Intune evolve.
Evidence for a failed setting
- The complete OMA-URI, value, and data type configured in Intune
- Assignment scope, filters, exclusions, and the affected user or device
- Windows edition, version, build, join state, and management authority
- Intune per-setting status plus the matching MDM diagnostic event
Do not repeatedly redeploy an unverified setting. First confirm scope and format, then check PolicyManager and DeviceManagement-Enterprise-Diagnostics-Provider evidence. A conflict between Settings Catalog, security baseline, custom CSP, and local policy should be resolved at the source rather than masked with a broader assignment.