Skip to main content

Intune / Group Policy

Any of the settings in Configuration can be locked down centrally by setting registry values under HKLM\SOFTWARE\Policies\OncallBusyBarAgent, one subkey per section:

HKLM\SOFTWARE\Policies\OncallBusyBarAgent\Graph      (values: ClientId, TenantId, PollIntervalSeconds)
HKLM\SOFTWARE\Policies\OncallBusyBarAgent\Mic         (values: Enabled, PollIntervalSeconds)
HKLM\SOFTWARE\Policies\OncallBusyBarAgent\BusyBar     (values: Address)

Set only the values you want to lock down. Anything unset falls through to the user's own appsettings.json. Enabled should be set as a String value (true or false); the interval and address values can be a String or a DWORD, whichever your deployment tool makes easier. How the registry values get set is up to you: an Intune Settings Catalog custom OMA-URI profile, a Win32 app deployment script, or plain Group Policy all work identically from this app's point of view: it only reads the registry, it doesn't care how the values arrived.

Administrative template (ADMX/ADML)​

For a friendlier, point-and-click way to set these than raw OMA-URI or a script, the repo ships an administrative template at admx/: OncallBusyBarAgent.admx plus its language resource, en-US/OncallBusyBarAgent.adml. It gives IT a UI in Intune's Settings Catalog or the local/domain Group Policy Editor for the exact same registry values described above; it doesn't add any new capability the app doesn't already have.

Import into Intune​

  1. Devices → Manage devices → Configuration → Import ADMX tab → Import.
  2. Upload OncallBusyBarAgent.admx as the ADMX file, and en-US/OncallBusyBarAgent.adml as the ADML file for the en-US language.
  3. Once imported, create a Settings Catalog configuration profile and search for "BUSY Bar on call agent" to find the six settings, organized under Microsoft Graph sign-in, Microphone fallback, and BUSY Bar device categories.
  4. Set only the settings you want to lock down and assign the profile to your target devices. Anything left "Not configured" falls through to the user's own appsettings.json, exactly as described above.

Updating this file later: re-uploading a changed ADMX with the same settings fails with a namespace error unless you first delete any configuration profiles using it and delete the old ADMX, or give the new version's policyNamespaces a different namespace (e.g. append a version number). Plan for this before making a breaking change to the policy definitions.

Use with Group Policy instead​

Copy OncallBusyBarAgent.admx to %SystemRoot%\PolicyDefinitions and en-US\OncallBusyBarAgent.adml to %SystemRoot%\PolicyDefinitions\en-US (or your domain's central policy store, if you have one) on a machine with the Group Policy Management Console. The settings then appear under Computer Configuration → Administrative Templates → BUSY Bar on call agent.

What this does not cover​

This template only exposes the six settings already documented in Configuration's registry table (Graph:ClientId, Graph:TenantId, Graph:PollIntervalSeconds, Mic:Enabled, Mic:PollIntervalSeconds, BusyBar:Address). If a future version of the app adds new config keys, this template needs a matching update to expose them the same way. The app itself will still read a manually-set registry value under the same HKLM\SOFTWARE\Policies\OncallBusyBarAgent key even if this template hasn't been updated to add a friendly control for it yet.