Install Apty Widget Microsoft Edge Extension via Win32App in Intune

This document will provide end-to-end instructions on how to deploy the Apty Widget Microsoft Edge Extension via Intune for devices with Windows 10 (or above).



1. You need to download and install WinAppUtil application to package applications in Microsoft Intune. 

2. You should have appropriate licenses to deploy a Windows 10 device with Intune.

3. You should have the Microsoft Edge browser installed on your device.


Step 1: Go to C:\Windows\Temp\ in your system. Just press the Windows key + R key on your keyboard and enter temp. And click on OK. Once you're inside the temp folder, create a new folder named EdgeAddOnAptyExtension

Step 2: Inside this folder, create two files. 

The first file (EdgeAddOnAptyExtension.ps1) contains a PowerShell script that creates a registry key that forces Microsoft Edge to install the extension. 

The second file (Install.cmd) will be used in Intune configuration, which will basically call the PowerShell script from EdgeAddOnAptyExtension.ps1 

Step 3: Add the following content inside the PowerShell file (EdgeAddOnAptyExtension.ps1). 

#Set variables as input for the script
#Enter the Customer Application Key in place of the given KeyValue
$KeyPath = "HKLM:\Software\Policies\Microsoft\Edge\ExtensionInstallForcelist"
$KeyName = "21"
$KeyType = "String"
$KeyValue = "ApplicationKey;"

#Verify if the registry path already exists
if(!(Test-Path $KeyPath)) {
    try {
        #Create registry path
        New-Item -Path $KeyPath -ItemType RegistryKey -Force -ErrorAction Stop
    catch {
        Write-Output "FAILED to create the registry path"

#Verify if the registry key already exists
if(!((Get-ItemProperty $KeyPath).$KeyName)) {
    try {
        #Create registry key
        New-ItemProperty -Path $KeyPath -Name $KeyName -PropertyType $KeyType -Value $KeyValue
    catch {
        Write-Output "FAILED to create the registry key"

Note: This script can be used to implement every Edge extension. But make sure you replace the $KeyValue with the value needed for your extension. Also while reusing this script, you must use a unique number for $KeyName (in this case, any number other than 21) to avoid overwriting.

Step 4: The file Install.cmd contains the following code.

Powershell.exe -Executionpolicy bypass -File EdgeAddOnAptyExtension.ps1


In order to create the package, start Powershell on your system and run the WinAppUtil application. Copy the path where the WinAppUtiapplication is saved. In this demo, the location is C:\Windows\temp\EdgeAddOnAptyExtension\IntuneWinAppUtil.exe

Then run the command as shown below. 


Source folder path and output folder paths are defined as: C:\Windows\Temp\EdgeAddOnAptyExtension

Setup file: EdgeAddOnAptyExtension.ps1 

Once the commands run successfully, you can go back to the folder C:\Windows\Temp\EdgeAddOnAptyExtension and you can see the .intunewin file there. 


Here you need to create a Configuration Profile within Intune, then configure settings to add the IDs to the allow the list, and then configure the silent installation settings.

Step 1: Go to the Microsoft Endpoint Manager Admin Center, navigate to Devices, Configuration Profiles and then Create Profile.

Step 2: Select Windows 10 and later and profile type as Settings Catalog, as shown below:

Step 3: Give the profile an appropriate Name and add a Description. Then click Next

Step 4: Now on the Configuration Settings screen, click on Add settings, look under Microsoft Edge and then Extensions, select Allow specific extensions to be installed, and Control which extensions cannot be installed:

Step 5: Now configure for Silent Installation of Extensions. Within the same configuration profile created above, add an additional setting named, Control which extensions are installed silently from the same area as before, under Microsoft Edge and then Extensions:

Step 6: Then close the Settings Picker, set the Control which extensions are installed silently to Enabled, and add the Update URL. 

Update URL: ApplicationKey:URL to fetch data

URL to fetch data:

Save the changes to complete the deployment process.

Best Practice 

Assign this to a test group of users or devices before enabling in prod (as you should, for all new configurations within Intune) and check out the results.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.