Skip to main content

Deploying the Substly Extension with Microsoft Intune

This guide outlines how to deploy the Substly browser extension centrally, with a silent installation, using Microsoft Intune.

Written by Rickardh Forslund
Updated today

The Substly browser extension is an important tool to help detect Shadow IT and monitor SaaS usage across your organization.​ Following this guide, deployment should take minutes.
​
Let's get started!
​


Step 1: Activate your Extension in Substly

  1. Go to your Substly Extension view and press Activate.
    ​

  2. Download the πŸ“¦ Substly ADMX files.
    ​

  3. Copy your unique Substly Key.
    ​​


    ​

Step 2: Import the Substly ADMX files to Intune

  1. Go to Intune Admin Center and Devices β†’ Configuration β†’ Import ADMX.
    ​

  2. Import the Substly .admx and .adml files for Windows, Chrome and Edge.
    ​

⚠️ Make sure Windows ADMX is processed first
​
For Intune to process additional ADMX files, Windows.admx must be in place.
Upload Windows.admx first and make sure it is fully processed before proceeding. If you already have such a file, you do not have to import it again.

Step 3: Create a policy for the Substly Client Key​

  1. Jump to Policies to create a configuration profile.
    ​

  2. Select Windows 10 and later as platform, with the profile type Templates.
    ​

  3. Find or scroll down to Imported Administrative templates and create.
    ​

  4. Name the new policy Substly Client Key.
    ​

  5. In the Configuration settings step, open Computer Configuration β†’ Substly β†’ Chrome Extension.
    ​

  6. Click on Client key.
    ​

  7. Check Enabled and paste in your unique Substly key.
    ​

  8. Assign the policy to all Devices, and save.
    ​

  9. Repeat these steps for Edge.

βœ… Assign the policy to all Devices
​
The policy itself does not deploy anything to users, only configures future

deployment. We recommend assigning the policy to all devices in this step.

❌ Do not use Excluded groups by mistake
​
When setting your scope, note that Intune has Included groups above and Excluded groups right below. Make sure to work in the Included section.

Step 4: Deploy the Substly Extension

  1. Create a new policy, with the profile of Settings catalog.
    ​

  2. Name this policy Substly Extension Force Install.
    ​

  3. In this policy, add settings for Chrome and Edge using the Settings picker.
    ​

  4. Add Chrome settings.
    ​

    1. Find and select the category:
      ​Google Google Chrome Extensions.
      ​

    2. Scroll to the subcategory:
      ​Configure the list of force-installed apps and extensions.
      ​


      ​

    3. In the left-hand view, Enable this setting to see an input field.
      ​

    4. Input the Extension ID and update URL for Chrome:
      ​fkjmkdagklhjcebfnejjkjmfclgnplgd;https://clients2.google.com/service/update2/crx
      ​


      ​

  5. Staying in the same policy, add Edge settings.
    ​

    1. Find and select the category:
      ​Microsoft Edge\Extensions
      ​

    2. Scroll to the subcategory:
      ​Control which extensions are installed silently
      ​

    3. In the left-hand view, Enable this setting to see an input field.
      ​

    4. Input the Extension ID and update URL for Edge:
      ​

      ghjglhcgjblhpnfcpkgpjbekjmmhjamn;https://edge.microsoft.com/extensionwebstorebase/v1/crx
      ​

  6. Assign the policy to your target device group.
    ​


    ​

⚠️ Deploying additional browser extensions?
​
Intune does not support multiple policies for silently installing a browser extension - in such cases, it will only deploy one of them.
​
If you already have such a policy, or add one in the future, make sure to deploy all extensions through a single policy profile.



Optional: Deploy PowerShell script for user identification

If your organization is on an Entra environment, this step might be necessary in order to cover Chrome. If anonymous authentication is sufficient, you can skip this step.
​

  1. Download our PowerShell script:

  2. In Intune, go to Devices β†’ Scripts and remediations β†’ Platform scripts.
    ​

  3. Add a new Platform script.
    ​

  4. Select the type Windows 10 and later.
    ​

  5. Name it Substly Extension User Key Setter.
    ​

  6. In the next step, upload the script under Script location.
    ​

  7. Toggle all options in this view to No.
    ​

  8. Assign to all Devices and create.


​
​
​All done! Welcome to real-time SaaS discovery πŸ₯³

Congratulations on a successful deployment of the Substly Extension!
You are now ready to help your organization detect, monitor and handle shadow IT and SaaS usage.
​



πŸ’¬ FAQ

Can't find the answer to your particular question? Get in touch.

Q: Are users notified when the Substly Extension is installed?
A: No. Users will not be notified, and do not have to take any action.

Q: Can users see the Substly Extension?
A: Yes, but only if they actively review their browser extensions. There are also Substly features that allow you to communicate with users via the extension.

Q: Can users remove the Substly Extension?
A: No. Forced installation of browser extensions cannot be uninstalled by users.

Q: Can users simply log out from the Substly Extension?
A: No, not if you have followed this guide and the ClientKey is set.



πŸ€” Troubleshooting

We are happy to help, and can resolve most issues.
​

Q: Why is my Devices tab in Substly not being populated?
​
A: This is likely due to an incomplete deployment, where Substly cannot set the ClientKey or UserKey properly. It can also indicate users are not logged into their managed browser profile.
​
There are two settings under your Extension tab in Substly to resolve this:

  • Allow login with Device ID

    This allows authentication via UserKey. Otherwise, the user needs to be signed into a managed browser profile.
    ​

  • Allow anonymous authentication
    This allows anyone to authenticate, as long as they have the ClientKey.
    ​
    If you have the first setting enabled, and still do not see devices getting populated, enable anonymous authentication to confirm whether the extension is getting installed and ClientKey is being set.





​
​

Did this answer your question?