Microsoft Intune

How to connect Corma to your Microsoft tenant account

This article covers the process to auto-install the Corma Launcher extension on the Chrome & Edge web browser on a Window computer using Microsoft Intune, which involves:

• Pushing an administrative template to end-user devices (steps 1-3).

• Validating that the installation was successful (Step 4).

The installation process doesn’t identify the visitors (end-users) or include metadata about them. Pair this installation with a follow-up configuration to identify visitors to Corma.

For complete documentation on using Intune to push administrative templates, see Microsoft's article: Using the settings catalog.

Prerequisites

• ⚠️ Prerequisite Check

  • Google Admin Console Conflict: This installation method is not compatible if you already use Google Admin Console to manage Chrome extensions on target devices. If so, continue using Google Admin Console for Corma.

  • Separate Profiles: Chrome and Edge policies must be configured as two separate profiles in Intune.

Before you continue, we recommend that you communicate efficiently with your teams on the Corma app. You can use our one pager communication document for this purpose.

Find below the detailed steps for the following prerequisites:

• Create a configuration profile

• Configure your new profile

• Complete the profile creation workflow

• Validate the installation

1. Create a configuration profile

   1. Sign in to the Microsoft Intune admin center

   2. Navigate to Devices > Configuration Profiles

   3. Select + Create profile above the Search bar

      

   4. In the profile settings:

      • Platform: Select Windows 10 and later.

      • Profile type: Select Settings Catalog.

   5. Select Create in the bottom-left corner of the form

      

   6. Select Create in the bottom-left corner.

   7. In the Basics tab, enter a name (e.g., Corma Launcher - Chrome) and an optional description.

   8. Select Next to open Configuration settings.

2. Configure extension settings

   1. In the Configuration settings tab, select + Add settings. This opens a settings pane.

   2. Configure the extensions (both can be done at the same time in the same policy.

   For chrome extension:

   1. In the Configuration settings tab, select + Add settings.

   2. Search for ExtensionInstallForcelist in the Settings picker search bar.

   3. Select Configure the list of force-installed apps and extensions under Google > Google Chrome > Extensions.

      

   4. Close the settings picker side pane.

   5. Toggle the setting to Enabled.

      

   6. Enter the Corma Chrome extension string into the input box:

      iolppafpkhfdepflackhngphhjkocjoa;https://clients2.google.com/service/update2/crx

   For Microsoft Edge

   1. Download the Microsoft Edge Policy Templates.

   2. Extract the archive and navigate to windows\admx.

   3. Copy msedge.admx, msedgeupdate.admx, and msedgewebview2.admx to C:\Windows\PolicyDefinitions\.

   4. Copy matching .adml files from windows\admx\en-US to C:\Windows\PolicyDefinitions\en-US\.

   5. Open Group Policy Management Editor for your GPO.

   6. Navigate to:

      Computer Configuration > Policies > Administrative Templates > Microsoft Edge > Extensions

   7. Right-click Control which extensions are installed silently and select Edit.

      

   8. Close the settings pane

   9. Select Enabled

      

   10. In the Value column, paste:

       olpgbphkganafbdmkdjddhpfhnjoapke

       Click OK to close the contents window, then click Apply and OK.

       ⚠️ Chrome and Edge profiles need to be configured as 2 seperate profiles

3. Complete the profile creation workflow

   1. (Optional) Adjust scope tags in the Scope tags tab if required by your organization.

      For full documentation on scope tags, see Microsoft's article: Use role-based access control (RBAC) and scope tags for distributed IT.

   2. Select Next to open the Assignments tab.

   3. Assign the profile to target users or devices.

      ℹ️ Tip: We recommend targeting a single test device first before rolling out to larger employee groups.

   4. Select Next to open Review + create.

   5. Review your configuration and select Create.

      

4. Validate the installation

   1. Confirm Registry Key Presence On a target Windows device:

      1. Open the Registry Editor (regedit).

         Navigate to:

         HKEY_LOCAL_MACHINE > SOFTWARE > Google > Chrome > ExtensionInstallForceList

      2. Verify that a key exists containing:

         epnhoepnmfjdbjjfanpjklemanhkjgil;<https://clients2.google.com/service/update2/crx>

         

   2. Confirm Extension in Browser

      1. Open Google Chrome or Microsoft Edge on the target device (restart if open).

      2. Open chrome://extensions or edge://extensions in your browser.

      3. Confirm that Corma Launcher is listed and managed by your organization.