
How IT installs, updates and controls apps on Windows PCs: deployment methods, Microsoft's tools, app control and patching third-party apps.
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.


Content writer, trio.so
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.
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.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:
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".
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.
The data type must match the "Format" the CSP reference lists for the setting. Intune offers these types for Windows custom settings:
Paths copied from web pages or PDFs often carry invisible characters. Paste them into a plain-text editor first, or type them by hand.
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.
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.
| Setting | OMA-URI path | Data type | Value | Use |
|---|---|---|---|---|
| Defender network protection | ./Device/Vendor/MSFT/Policy/Config/Defender/EnableNetworkProtection | Integer | 1 (on), 2 (audit), 0 (off) | Block connections to known malicious hosts |
| MDM wins over Group Policy | ./Device/Vendor/MSFT/Policy/Config/ControlPolicyConflict/MDMWinsOverGP | Integer | 1 (MDM wins) | Make MDM policies in the Policy CSP win over matching Group Policy settings |
| Settings page visibility | ./Device/Vendor/MSFT/Policy/Config/Settings/PageVisibilityList | String | showonly: or hide: followed by page IDs | Limit which Settings pages users can see |
| Edge home button | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~Startup/ShowHomeButton | String | <enabled/> | An ADMX-backed Edge policy |
| Turn off Windows Copilot (older Copilot only) | ./User/Vendor/MSFT/Policy/Config/WindowsAI/TurnOffWindowsCopilot | Integer | 1 | Applied to the earlier Copilot sidebar; the newer Copilot app is managed differently |
| BitLocker settings | ./Device/Vendor/MSFT/BitLocker/[setting] | Depends on the setting | See the BitLocker CSP | Encryption requirements and recovery options |
| Local administrators group | LocalUsersAndGroups or RestrictedGroups in the Policy CSP | String (XML) | See the CSP page | Control who is a local administrator |
For more on how MDM and Group Policy overlap, see MDM vs GPO.
The choice comes down to where your devices are and whether a simpler tool already covers the setting.
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.
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:
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.
Error (often 0x87d1fde8, "Remediation failed"): the CSP received the setting and could not apply it. Common causes:
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.
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.
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.
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.

Related reading: MDM vs GPO, Autopilot vs Intune, PowerShell execution policies and Microsoft Intune alternatives.
trio.so applies BitLocker, password, firewall and update policies to Windows PCs and runs scripts for anything a policy does not cover.
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.
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.





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

How IT installs, updates and controls apps on Windows PCs: deployment methods, Microsoft's tools, app control and patching third-party apps.

How to remotely wipe a Windows 10 or 11 laptop: the MDM wipe options, Intune Wipe vs Retire, what happens offline, and why BitLocker matters first.

Fix "The Group Policy Client service failed the sign-in" and "Windows couldn't connect to the Group Policy Client service": service, permissions, repair.

What each PowerShell execution policy does, how to check and set it with Set-ExecutionPolicy, and how to fix "running scripts is disabled".

Tired of intrusive ads on Windows 10? Discover effective methods for how to block ads on Windows 10 and enhance your browsing experience.

Curious about patch management challenges? WSUS vs SCCM offers unique solutions for efficient updates and robust system security in your firm.

How to pause, delay or disable Windows Update on Windows 11 and 10 with Settings, Group Policy, the registry and services, and why IT should defer instead.

Intune vs SCCM compared: cloud vs on-premises, co-management, Configuration Manager's future, and which fits a small, mid-size or hybrid fleet.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients