Create a User Level Custom Windows MDM (OMA URI) Policy
Admins can configure and deploy custom MDM policies to Windows devices to meet specific needs that are not covered by JumpCloud’s existing MDM policy library. Open Mobile Alliance Uniform Resource Identifier (OMA URI) is used in MDM to configure settings and manage devices through policies.
This is a user level policy that applies to a user's profile across managed devices. You can bind this policy to individual users or user groups. For policies that apply system-wide to a device and all of its users, see Get Started: Policies and Learn More section of this article.
Prerequisites
- Devices must be enrolled in Windows MDM (Mobile Device Management).
- Target devices must be running Windows 10 or later. This policy is supported on the following Windows editions:
- Windows Pro
- Windows Enterprise
- Windows Education
- Windows SE
- IoT Enterprise
- IoT Enterprise LTSC
- For more information on device compatibility, see Agent Compatibility, System Requirements, and Impacts.
Considerations
- Users must log out and back in to all devices where this policy was applied for it to take effect.
Creating the Policy
To create a Custom MDM (OMA URI) policy for Windows users, do the following:
- Log in to the JumpCloud Admin portal.
If your data is stored outside of the US, check which login URL you should be using depending on your region. If your organization uses LDAP, RADIUS, or requires firewall allow list configuration, the Fully Qualified Domain Names (FQDNs) will also be region specific. See JumpCloud Data Centers for the URLs, FQDNs, and IP addresses.
- Go to Device Management > Policy Management. The Policy Management page is displayed.
- On the Policy Management page, click +Add New.
- Select User Policy to assign the policy to users and users groups. On the New User Policy page:
- Select the Windows tab.
- Search and select the required policy name and click Configure. The Details tab of the policy is displayed.
- On the Details tab, configure the required policy configuration settings.
- (Optional) In the Policy Name field, enter a new name for the policy or keep the default. Policy names must be unique.
- (Optional) In the Policy Notes field, enter details such as creation date of the policy, and information on testing and deployment of the policy.
Configuring the Policy
- In the Settings section, enter the details as required. For more information, see Group OMA-URI entires by AreaName.
- Enter the exact value in the OMA URI field. OMA URI is a unique path that targets a specific setting or configuration.
- Select the Format from the dropdown. The available formats are - integer, string, float, boolean, xml, and base64.
- In the Value field, enter the exact value.
- Use the + button to add more identifiers.
To find the exact the OMA-URI and the associated value details for a specific policy, see Microsoft’s support documentation for Configuration Service Provider (CSP).

Applying the Policy
- (Optional) Select the Policy Groups tab. Select one or more policy groups where you want to add this policy.
- Select the User Groups tab. Select one or more user groups where you want to apply this policy. For user groups with multiple OS member types, the policy only applies when a user logs into a supported Windows device that is enrolled in MDM.
- Or, select the Users tab. Select one or more users to whom you want to assign this policy.
- Click Create Policy. A success message is displayed indicating the completion of policy creation.
Viewing Policy Status
- Select the Statustab.
- To see the last Result Log for a device where this policy is applied, click view.
- If any errors occur, they're listed inExit Status. If you have an Exit Status of 0, no errors occurred when applying or enforcing this policy.
Was this information helpful?