Set application parameters centrally on every device in your organization — from the tenant address and the set of drives to scheduled backups and the interface language. Via Active Directory (GPO) or Microsoft Intune, with familiar ADMX templates.
The template describes to the administrator which settings to configure. OneMount reads
them from the registry (SOFTWARE\Policies\OneMount) and only
reads — so a policy always wins over the user's own settings, and a managed
setting becomes disabled in the app with a "managed by your organization" note.
From Microsoft Store — with Intune or with Group Policy and winget. All installation options.
To the domain Central Store, locally, or to Intune (see below).
In the "OneMount" section — computer or user scope, your choice.
gpupdate /force and restart OneMount on the devices.
28 policies. Each comes with a detailed description right in the policy editor.
OneMount 0.9.55+ · files go straight from the PC to OneDrive or SharePoint. Why OneDrive is not a backup →
The Microsoft Store version is updated by the Store.
Pick the scenario that fits your infrastructure.
Copy the files to the Central Store — the policies become available on every domain controller and workstation:
Manage in the Group Policy Management Console (GPMC), linking GPOs to the OUs you need.
In the admin center:
OneMount.admx first, then the OneMount.adml files you need.The settings appear among the profile options.
Copy the files to the local policy store:
Manage via gpedit.msc →
Administrative Templates → OneMount.
Tip. If the domain has an active Central Store, the policy editor takes
templates only from there and ignores the local folder. After changing policies, run
gpupdate /force on the device and restart OneMount — settings are read at
startup. The full guide is in the README.md inside the archive.
The key removes the manual user list: everyone who signs in to OneMount on a managed machine automatically joins your organization and gets a license as soon as a seat is free.
In the customer portal on the
"Organization" page — the "Organization ID" block, format
XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.
Keep the key secret: anyone who has it can join users to your organization and occupy paid seats. If it leaks, click "Regenerate" in the portal — the old key stops working instantly, existing members are not affected.
Import the ADMX templates into Intune (Devices → Configuration → Import ADMX) and set the same policy — or deploy a PowerShell script that writes the key to the registry:
Without policies a user can enter the key in the app: Account → Organization → Join.
The "Organization enrollment key" policy (the "Licensing" category of these very templates), or the registry value directly:
The key is read live, so the policy also applies to already installed copies — nothing needs to be reinstalled. A key from policy takes priority over one entered manually, and users can no longer change the organization in the app.
Download the ADMX templates and manage OneMount centrally.
Download templates (ZIP)