OMA-URI Policy Builder

What OMA-URI Policy Builder helps you do

Arrive knowing the Windows setting you want—not the OMA-URI. The Intune CSP Policy Workbench searches a local Microsoft Policy CSP catalog, confirms scope and access, configures documented values, and produces aligned portal, Graph, SyncML, and diagnostic artifacts without uploading policy content.

This workflow is designed for browser-first processing, so you can complete the task quickly without sending files off to another dashboard or waiting for an account workflow.

How to use OMA-URI Policy Builder

1. Search for the Windows setting by name or description, or paste an OMA-URI you already have, then select the matching Policy CSP node from the local catalog.
2. Confirm scope, Intune data type, and access operations, configure a documented value, and resolve every readiness finding before export.
3. Copy the portal or Graph artifact, use the operation-aware SyncML and diagnostics outputs for troubleshooting, and test on a representative Windows device.

What you can do with OMA-URI Policy Builder

• Search thousands of Policy CSP nodes by name, area, description, or OMA-URI fragment.
• Show confirmed, structurally valid, or invalid confidence based on the local Microsoft Learn catalog snapshot.
• Auto-detect Device/User scope, Intune data type, and Add/Replace SyncML operations from CSP metadata.
• Configure enum, Boolean, XML/ADMX, and Base64 values with local file-to-Base64 conversion.
• Export portal fields, Graph custom-configuration JSON, operation-aware SyncML, and PowerShell diagnostics.

Example: build AllowTelemetry without hunting documentation first

Search for AllowTelemetry (or paste an OMA-URI), select the confirmed Policy CSP node, and choose a documented diagnostic-data value. Review the readiness findings for scope, format, and access compatibility.

Export the portal or Graph artifact into a narrow test assignment, keep the SyncML and diagnostics outputs for troubleshooting, and confirm device Result behavior before broader rollout.

What to know before you start

• The catalog is a Policy CSP snapshot generated from Microsoft Learn (CC-BY), not a live Microsoft API. Refresh with npm run generate:csp-catalog.
• Non-Policy CSPs and brand-new nodes may validate structurally without a confirmed catalog match.
• Policy/Config paths apply settings; Policy/Result and Get-only nodes cannot be used for configuration deployment.
• Custom policies can expose secrets or security posture in exported artifacts; review before sharing.