Microsoft Intune

Use Microsoft Intune to push the Robost extension to Chrome or Edge on Intune-managed Windows devices. The approach uses Intune’s Administrative Templates (ADMX-backed) or a custom OMA-URI configuration profile to deliver the Chrome Enterprise policy that force-installs the extension and supplies enrollment credentials.

Extension ID: gefljjkloapnkdffchpnakeplfmfiggh

Update manifest URL: https://storage.googleapis.com/clarity-extension-dist/update.xml

Prerequisites

• Microsoft Intune admin access
• Chrome or Edge deployed to target devices (or already present)
• Robost enrollment token — generate one via the Robost API (POST /settings/devices) or request one from Robost support. Self-service device enrollment in the admin console is planned.
• Target Intune device group identified

Step 1 — Create a configuration profile

1. In the Intune admin center, go to Devices → Configuration profiles → Create profile.
2. Set Platform to Windows 10 and later.
3. Set Profile type to Templates → Administrative Templates.
4. Name the profile (e.g. Robost Extension Policy) and click Next.

Step 2 — Force-install the extension

1. In the template settings, search for Configure the list of force-installed apps and extensions (under Google Chrome → Extensions or Microsoft Edge → Extensions).
2. Enable the setting and add the following value:

gefljjkloapnkdffchpnakeplfmfiggh;https://storage.googleapis.com/clarity-extension-dist/update.xml

This tells the browser to install the extension from the self-hosted update manifest and prevent user removal.

Step 3 — Push managed enrollment config via OMA-URI

Intune’s ADMX template does not expose Chrome’s ExtensionSettings policy in the UI, so use a custom OMA-URI profile to deliver the managed configuration.

1. Go to Devices → Configuration profiles → Create profile → Custom.
2. Add an OMA-URI row with the following values:
   • Name: Robost Managed Config
   • OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Extensions/ExtensionSettings
   • Data type: String
   • Value: paste the JSON below, replacing the placeholder values with your actual server URL and enrollment token:

{
  "gefljjkloapnkdffchpnakeplfmfiggh": {
    "managed_configuration": {
      "api_base_url": "https://api.robostai.com",
      "enrollment_token": "ctk_YOUR_ENROLLMENT_TOKEN_HERE"
    }
  }
}

The extension reads api_base_url and enrollment_token from chrome.storage.managed at startup. When both keys are present, the device enrolls automatically without any user action.

Note

For Microsoft Edge, replace the OMA-URI prefix Chrome~Policy~googlechrome with Edge~Policy~microsoftedge. The managed-config key names (api_base_url, enrollment_token) are identical for both browsers.

Note

For self-hosted deployments, replace https://api.robostai.com with your internal server URL (e.g. https://robost.yourdomain.com).

Step 4 — Assign and deploy

1. Assign both profiles to your target device group.
2. Click Review + save and confirm each profile.
3. Sync devices or wait for the next Intune check-in (typically 15–30 minutes for Windows).

Verifying the rollout

On a managed device:

1. Open chrome://policy (or edge://policy) and click Reload policies. Confirm ExtensionInstallForcelist shows the extension ID and update URL, and that ExtensionSettings contains the managed config block.
2. Open chrome://extensions → confirm Robost is listed as Installed by your administrator.
3. Open the extension’s options page (click the puzzle icon → Robost) and confirm Enrolled shows Yes.