Deploy Browser Extension via Intune

Learn how to deploy the Kabeen extension on browsers via Microsoft Intune

Microsoft Intune allows automatic deployment of the Kabeen browser extension on Windows workstations managed by your organization.

Prerequisites

  • Administrator rights on Microsoft 365 and Intune
  • Intune licenses for affected workstations
  • Native Kabeen agent already deployed (recommended)

Deployment on Microsoft Edge

Step 1: Create a Configuration Profile

  1. Log in to the Microsoft Intune admin center
  2. Navigate to Devices > Configuration > Create > New policy
  3. Select:
    • Platform: Windows 10 and later
    • Profile type: Templates > Administrative template

Step 2: Configure Force Installation

  1. In the profile, search for Microsoft Edge > Extensions
  2. Enable Control which extensions are installed silently
  3. Add the extension ID: jgdflahjneomipldehpneckiplknghbc

Step 3: Assign the Profile

  1. In the Assignments tab, select user or device groups
  2. Click Create to deploy the profile

Deployment on Google Chrome

Step 1: Import Chrome ADMX Template

  1. Download the Chrome ADMX templates
  2. In Intune, navigate to Devices > Configuration > Import ADMX
  3. Import the chrome.admx and chrome.adml files

Step 2: Create the Policy

  1. Create a new policy using the imported Chrome template
  2. Configure Extensions > Force-installed apps and extensions
  3. Add: hkmgmmaopoofgchofbngplopnhajbojc;https://clients2.google.com/service/update2/crx

Verify Deployment

After deployment, verify on a workstation:

  1. Open the relevant browser
  2. Access extension settings
  3. The Kabeen extension should appear as installed by your organization
  4. It cannot be disabled by the user

Troubleshooting

Extension doesn't appear

  • Verify the policy is assigned to the user/device
  • Manually sync policies: Settings > Accounts > Work access > Info > Sync
  • Wait up to 8 hours for full propagation

Extension can be disabled

  • Ensure installation mode is "Force-installed"
  • Verify no other policy contradicts this configuration