Domain Deployment
The simplest method of Intune deployment is via a win32 script. Follow the steps below to deploy Check with Intune.
Setup Script
Download a copy of the Setup-Windows-Chrome-and-Edge.ps1 script from the Check repository on GitHub using the button below.
Run the script locally on your computer to generate the following scripts:
Deploy-Windows-Chrome-and-Edge.ps1
Remove-Windows-Chrome-and-Edge.ps1
Detect-Windows-Chrome-and-Edge.ps1
You will be prompted during the Setup script on how you want to configure Check. Follow the script's guidance to ensure you're accurately entering values for the script. These values will be used for both the Deploy and Detect to ensure the extension is properly deployed.
Set the output location the script will use to generate the three new scripts.
You can also download the three scripts directly from the Check GitHub repo and edit the configuration settings manually.
Adding to Intune
Prerequisites
Microsoft Intune admin access
The Microsoft Win32 Content Prep Tool (
IntuneWinAppUtil.exe) to package scripts as.intunewinfiles
Step 1: Package the Scripts
Intune Win32 apps require an .intunewin package. Place your three configured scripts in a folder, then run:
This creates Deploy-Windows-Chrome-and-Edge.intunewin.
Step 2: Create the Win32 App in Intune
Open the Microsoft Intune admin center
Navigate to Apps > Windows
Click Add > Select Windows app (Win32) > Select
Upload the
.intunewinfile created in Step 1
Step 3: Configure App Information
Name
Check by CyberDrain - Browser Extension
Description
Deploys and configures the Check by CyberDrain phishing protection extension for Chrome and Edge browsers.
Publisher
Your company name or CyberDrain
Step 4: Configure Program Settings
Install command
powershell.exe -ExecutionPolicy Bypass -File Deploy-Windows-Chrome-and-Edge.ps1
Uninstall command
powershell.exe -ExecutionPolicy Bypass -File Remove-Windows-Chrome-and-Edge.ps1
Install behavior
System
Device restart behavior
No specific action
Step 5: Configure Requirements
Operating system architecture
64-bit
Minimum operating system
Windows 10 1607 (or your minimum supported version)
Step 6: Configure Detection Rules
Under Detection rules, select Use a custom detection script
Upload
Detect-Windows-Chrome-and-Edge.ps1Set the following:
Run script as 32-bit process on 64-bit clients
No
Enforce script signature check
No
Keep Run script as 32-bit process on 64-bit clients set to No so the detection script runs in the 64-bit PowerShell/registry context on 64-bit devices. This is important because the script checks values under HKLM:\SOFTWARE\Policies\...; running it as 32-bit could read redirected WOW6432Node paths and cause detection to fail incorrectly. The detection script checks that all registry keys written by the install script exist and have the correct values. It exits with code 0 when everything matches (app detected) and code 1 when any value is missing or wrong (app not detected, triggers reinstall).
Step 7: Assign the App
Under Assignments, click Add group under Required
Choose your target:
All devices — deploys to every Intune-managed Windows device
All users — deploys to devices used by any licensed user
Select groups — deploy to specific Azure AD / Entra ID groups
Click Review + create > Create
Updating Settings
When you need to change extension settings (e.g., enable page blocking, update branding):
Re-run the setup script with new values, or manually edit the config blocks in both
Deploy-andDetect-scriptsRe-package with
IntuneWinAppUtil.exeIn Intune, either update the existing app or delete and recreate it with the new package
Because the detection script body changes when settings change, Intune will detect the app as "not installed" on endpoints and automatically redeploy with the updated configuration.
Uninstalling
To remove the extension from managed devices:
Option A: In Intune, change the app assignment from Required to Uninstall. Intune will run the
Remove-Windows-Chrome-and-Edge.ps1script on targeted devices.Option B: Delete the app from Intune entirely. Note that this stops management but does not actively remove the registry keys from devices that already have them.
Troubleshooting
Extension not appearing after deployment: Check that the install script ran as System (not User). Verify registry keys exist under
HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionSettings\andHKLM:\SOFTWARE\Policies\Microsoft\Edge\ExtensionSettings\.Intune keeps reinstalling the app: The detection script values don't match what the install script wrote. Ensure both scripts have identical configuration values.
Detection script shows as failed: Run the detection script manually on a test device as Administrator to see which check fails (it will exit at the first mismatch).
Download the following from the Check repo on GitHub
Run Deploy-ADMX.ps1. As long as you keep the other two files in the same folder, it will correctly add the available objects to Group Policy.
Open Group Policy and create a policy using the imported settings that can be found at
Computer Configuration → Policies → Administrative Templates → CyberDrain → Check - Microsoft 365 Phishing Protection

You can use a CIPP standard to deploy Check. It works the same way that the Intune instructions do but CIPP handles all the work for install and detection script building.
For more, see our Standards documentation.
Last updated