trio.so
Explained

What Is OMA-URI? How It Works, Examples, and When to Use It

What OMA-URI is, how the path reaches a Windows CSP setting, data types and examples, when to use it over the Settings Catalog, and how to fix errors.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

OMA-URI (Open Mobile Alliance Uniform Resource Identifier) is the path an MDM uses to reach one specific setting on a Windows device, for example ./Device/Vendor/MSFT/Policy/Config/Defender/EnableNetworkProtection. The MDM sends the path, a data type and a value to the device, and the matching Configuration Service Provider (CSP) in Windows applies the setting. In Microsoft Intune you enter OMA-URI settings in a custom profile, and you use them only for settings that the Settings Catalog and the built-in templates do not offer. The paths are case-sensitive, the data type has to match what the CSP expects, and the CSP reference on Microsoft Learn tells you which Windows versions support each setting.

If you have met OMA-URI in an Intune custom profile and need to read a path, build one or work out why one fails, the examples table and the troubleshooting section below are the parts to use.

TL;DR

  • OMA-URI is a string path that points to one setting in a Windows Configuration Service Provider (CSP).
  • The MDM puts the path, a data type and a value in a custom profile and sends it to the device over the OMA-DM protocol; the CSP on the device applies it.
  • Use OMA-URI only when the Settings Catalog has no option for the setting you need. If the Catalog covers it, use the Catalog; it is easier to get right and to audit.
  • Paths are case-sensitive. A typo, a trailing space or a wrong data type is the most common reason a custom setting fails.
  • Check the CSP reference for the Windows versions each setting supports before you build a path. A setting that does not exist on the device's build reports "Not applicable".

What OMA-URI Actually Is (and the Stack It Sits In)

If you have already built and deployed a custom OMA-URI setting, skip ahead to the examples table. This section gives the model first.

OMA stands for the Open Mobile Alliance, the industry body that defined the device management standard Windows uses, called OMA Device Management (OMA-DM). It was written for mobile phones, and Microsoft built Windows MDM on it. An OMA-URI is an address in that standard: give the MDM the address, a data type and a value, and Windows applies the setting at that address.

Every Windows OMA-URI path follows the same pattern:

./[Scope]/Vendor/MSFT/[CSP name]/[setting path]
  • ./Device/ or ./User/ is the scope. Device scope applies to the computer whoever signs in; user scope applies to the signed-in user.
  • Vendor/MSFT/ is Microsoft's namespace.
  • The CSP name is the Configuration Service Provider that handles the setting, such as Policy, BitLocker or Defender.
  • The setting path is the exact node inside that CSP.

A Configuration Service Provider is the part of Windows that receives an MDM instruction and turns it into a change on the device. Each CSP covers one area, such as BitLocker, Defender or the Policy CSP that holds most Group Policy equivalents. The OMA-URI is the address; the CSP is what acts on it.

The transport is OMA-DM: the MDM server sends SyncML messages over HTTPS, and the device replies with the result of each command. The full chain runs in this order:

  1. OMA-URI: the address and value.
  2. Custom profile: the container that holds one or more OMA-URI settings.
  3. MDM: packages the profile and sends it.
  4. OMA-DM: carries it to the device over HTTPS.
  5. CSP: applies the setting on the device and reports back.

Before you write a path, check the "Applicability" or supported versions section of the setting's page in the CSP reference. A path for a setting that does not exist on the device's Windows build fails quietly with "Not applicable".

Custom OMA-URI Settings: A Working Reference Table and Real Examples

Finding the right path is the hardest part. Microsoft's CSP reference on Microsoft Learn is the authoritative source: search for the setting followed by "CSP", and the setting's page lists the path, the format, the allowed values and the supported Windows versions. Every custom OMA-URI setting needs the same five fields: a name, a description, the OMA-URI path, the data type and the value.

Data Types You'll Encounter

The data type must match the "Format" the CSP reference lists for the setting. Intune offers these types for Windows custom settings:

  • Integer: numeric values, usually flags such as 0 (off), 1 (on) or 2 (audit).
  • String: text values such as lists, URLs or page IDs.
  • String (XML file): structured data, used for example for AppLocker rules and ADMX ingestion.
  • Boolean: true or false; less common than Integer on Windows.
  • Base64 (file): encoded binary content.
  • Date and time, and Floating point: for the few settings that use them.

Paths copied from web pages or PDFs often carry invisible characters. Paste them into a plain-text editor first, or type them by hand.

ADMX-Backed Policies: Managing Third-Party Apps via Custom OMA URI

Apps that ship ADMX templates, such as Chrome, Firefox or Microsoft Office, can be configured through OMA-URI in two steps. First, ingest the app's ADMX file with an OMA-URI under the Policy CSP's ADMXInstall node, using the String (XML file) type. Then set each policy with a path that points to the ingested template. If you send the policy setting before the ADMX file has been ingested, the setting fails, which is the most common problem with browser and Office policies.

The same approach answers questions about mapping Office registry keys, such as Outlook settings, to OMA-URI: find the ADMX template that sets the key, ingest it, then configure the policy it defines. Many Office and Edge settings are also in the Settings Catalog, so check there first.

User Scope vs. Device Scope

The ./Device/ and ./User/ prefixes are not interchangeable. Some settings exist only in one scope. A setting sent in the wrong scope usually does not apply and may not show a clear error. The CSP reference lists the scope for each setting; check it before you write the path.

OMA-URI Examples: Common Windows Configuration Settings

SettingOMA-URI pathData typeValueUse
Defender network protection./Device/Vendor/MSFT/Policy/Config/Defender/EnableNetworkProtectionInteger1 (on), 2 (audit), 0 (off)Block connections to known malicious hosts
MDM wins over Group Policy./Device/Vendor/MSFT/Policy/Config/ControlPolicyConflict/MDMWinsOverGPInteger1 (MDM wins)Make MDM policies in the Policy CSP win over matching Group Policy settings
Settings page visibility./Device/Vendor/MSFT/Policy/Config/Settings/PageVisibilityListStringshowonly: or hide: followed by page IDsLimit which Settings pages users can see
Edge home button./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~Startup/ShowHomeButtonString<enabled/>An ADMX-backed Edge policy
Turn off Windows Copilot (older Copilot only)./User/Vendor/MSFT/Policy/Config/WindowsAI/TurnOffWindowsCopilotInteger1Applied to the earlier Copilot sidebar; the newer Copilot app is managed differently
BitLocker settings./Device/Vendor/MSFT/BitLocker/[setting]Depends on the settingSee the BitLocker CSPEncryption requirements and recovery options
Local administrators groupLocalUsersAndGroups or RestrictedGroups in the Policy CSPString (XML)See the CSP pageControl who is a local administrator

For more on how MDM and Group Policy overlap, see MDM vs GPO.

OMA-URI vs. Settings Catalog vs. Group Policy: Which One Do You Need?

The choice comes down to where your devices are and whether a simpler tool already covers the setting.

  • Domain-joined PCs that stay on the company network: Group Policy has the widest coverage and needs no paths.
  • Cloud-managed or remote PCs, and the setting is in the Settings Catalog or a built-in template: use those. They are validated, easier to read and easier to audit.
  • Cloud-managed or remote PCs, and the setting is not in the Catalog: use a custom OMA-URI setting. That is the case it exists for.
  • Not sure: look the setting up in the CSP reference. If it has a CSP path that supports the operations your MDM needs, it can be managed through MDM; if it has none, it usually cannot.

On PCs that receive both Group Policy and MDM, the MDMWinsOverGP setting makes MDM policies in the Policy CSP block their Group Policy equivalents. It is available from Windows 10 version 1803. Before you turn it on, check which settings your existing GPOs enforce: the matching Group Policy settings stop applying once MDM wins.

How to Create a Custom OMA-URI Policy in Any MDM Platform

The five fields are the same in every MDM that offers custom Windows settings, because the path format comes from the OMA standard. In Microsoft Intune, the steps are:

  1. In the Intune admin center, go to Devices > Manage devices > Configuration > Create > New policy.
  2. Choose Windows 10 and later as the platform and Templates > Custom as the profile type.
  3. Under Configuration settings, select Add and enter the name, a description, the OMA-URI path (case-sensitive), the data type and the value.
  4. Assign the profile to a test group first, then review and create it.

Microsoft notes that Intune does not support every setting in the CSP reference: a setting must support the Add, Replace and Get operations. If the value the device returns does not match the value sent, Intune reports an error.

After deployment, check the status per device. If the setting does not apply and the path came from a formatted source, retype it. Record the previous value before you change anything, so you can roll back by sending the old value.

Troubleshooting OMA-URI Policies: Error Codes, Silent Failures, and What to Check First

The Three Failure States (and What They Mean)

Error (often 0x87d1fde8, "Remediation failed"): the CSP received the setting and could not apply it. Common causes:

  • A wrong path: a typo, the wrong case or a trailing space.
  • The wrong data type for the setting.
  • An ADMX-backed setting sent before its ADMX file was ingested.
  • A value outside the allowed range.

Not applicable: the setting does not exist on the device's Windows build or edition. Check the supported versions in the CSP reference.

Nothing reported at all: the profile never reached the device. Common causes are an assignment to a group the device or user is not in, a co-management workload that leaves configuration with Configuration Manager, or a scope mismatch.

How to Diagnose a Failed Policy

  1. On the device, open Settings > Accounts > Access work or school, select the work account, and create the Advanced Diagnostic Report. It shows which settings the device received and which Group Policy settings MDM is blocking.
  2. Check Event Viewer under Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin for errors that name the path.
  3. For protocol-level detail, the community SyncML Viewer tool shows the OMA-DM messages the device sends and receives during a sync.

If the console shows success but the setting is not in effect, the diagnostic report is the ground truth: if the setting is not listed there, the device never received it.

Where OMA-URI Fits in 2026: MMP-C and the Dual-Engine Reality

OMA-URI is not going away. Microsoft has added a second management channel for Windows, the Microsoft Management Platform cloud (MMP-C), which uses the Windows declared configuration protocol. Devices enrolled in Intune can use both channels: some newer Intune features, such as Endpoint Privilege Management, use the declared configuration channel, while CSP settings, including custom OMA-URI settings, continue to use OMA-DM.

For anyone writing custom settings, nothing changes: OMA-URI remains the way to reach CSP settings that have no higher-level option. If you also run Configuration Manager in co-management, keep a record of which tool owns each area, so settings do not compete.

Managing this across many devices

Most of the settings people reach for OMA-URI to configure are the everyday ones. trio.so applies Windows policies for BitLocker, passwords, the firewall and updates through MDM, keeps BitLocker recovery keys in the console, and runs scripts on enrolled Windows PCs for anything a policy does not cover. Macs, iPhones, Android and Linux devices sit in the same console. See Windows device management.

The trio.so Create policy wizard on the Type and platform step with Windows selected and common Windows policy types such as Device restrictions, Wi-Fi, VPN, Firewall, Software updates and Password policy.
In trio.so, a Windows policy starts from a type such as Firewall, Software updates or Password policy.

Related reading: MDM vs GPO, Autopilot vs Intune, PowerShell execution policies and Microsoft Intune alternatives.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Configure Windows devices from one console

trio.so applies BitLocker, password, firewall and update policies to Windows PCs and runs scripts for anything a policy does not cover.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

A path that points to one setting in a Windows Configuration Service Provider. An MDM sends the path, a data type and a value, and Windows applies the setting.

Open Mobile Alliance, the industry body that defined OMA Device Management, the protocol Windows MDM is built on. OMA-URI means Open Mobile Alliance Uniform Resource Identifier.

Go to Devices > Manage devices > Configuration > Create > New policy, choose Windows 10 and later and Templates > Custom, then add the name, description, OMA-URI path, data type and value, and assign it to a test group first.

The Settings Catalog lists validated settings with names and options you pick from. OMA-URI lets you type the CSP path yourself, for settings the Catalog does not offer. Use the Catalog whenever it has the setting.

Usually a wrong path, a wrong data type, a value outside the allowed range, a missing ADMX ingestion, or a setting that the device's Windows version does not support. Check the path and format against the CSP reference and the device's diagnostic report.

Related

From the blog

The related industry news, interviews, technologies, and resources.