Deploy Chromium-Edge PWAs as Start menu tiles

2 minute read


Yesterday colleague of mine sent me interesting video - How to open “multiple instances” of Microsoft Teams. Which got me thinking, is there a way to customize those apps and attach them for employees to have quick access links on their workstations?? Drum roll…🥁

Deploy new Edge

This whole solution is based on the newest Chromium-Edge so first thing you should do is to migrate your users to it. With the help of Intune it’s a piece of cake 😊. Go to apps and click Add, select Microsoft Edge and proceed with configuration.




Now that it is being deployed we can prepare our Start menu Tiles.

Start menu Tiles

Basically what installing a site as an app in Edge is creation of simple shortcut with some AppID:

“C:\Program Files (x86)\Microsoft\Edge\Application\msedge_proxy.exe” –profile-directory=”Default” –app-id=idedlkepfahmdemmnladahgfmcaapdjg

But what you can do is modify this like that:

“C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge_proxy.exe” –profile-directory=”Default” –app=

And you get link to my blog!😆


That’s one app but how about creating multiple apps using Powershell! For this project I’ve created input data file with:

  • App Name
  • Site link
  • App icon
    "Application": "Blog",
    "Link": "",
    "Icon": "universe-icon.ico"
    "Application": "Fun",
    "Link": "",
    "Icon": "9gag-icon.ico"
    "Application": "Teams",
    "Link": "",
    "Icon": "teams-icon.ico"

This input then goes to this script

$Config = Get-Content .\ConfigJSON.json | ConvertFrom-Json
foreach ($item in $Config) {
    $SourceFileLocation = "C:\Program Files (x86)\Microsoft\Edge\Application\msedge_proxy.exe"
    $Arguments = "--profile-directory=Default --app=$($item.Link)"
    #This is a location of global start menu on workstation
    $ShortcutLocation = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\$($item.Application).lnk"
    $WScriptShell = New-Object -ComObject WScript.Shell
    $Shortcut = $WScriptShell.CreateShortcut($ShortcutLocation)
    $Shortcut.TargetPath = $SourceFileLocation
    #Location of icons on workstation
    $Shortcut.IconLocation = (Get-item ".\icons\$($item.icon)").FullName
    $Shortcut.Arguments = $Arguments
    Write-Output "Adding $($item.Application) to start menu"

And that is how we created Start menu items which work as Edge PWAs!

Start layout deployment

Again thanks to Intune this task couldn’t be easier!!
Firstly drag and drop all apps to some group and place group in destined location


Secondly export created layout to xml with Powershell

Export-StartLayout -Path c:\temp\layout.xml

Resulting XML will contain all tiles so you will need to modify it just to leave our configuration

<LayoutModificationTemplate xmlns:defaultlayout="" xmlns:start="" Version="1" xmlns="">
  <LayoutOptions StartTileGroupCellWidth="6" />
  <DefaultLayoutOverride LayoutCustomizationRestrictionType="OnlySpecifiedGroups">
      <defaultlayout:StartLayout GroupCellWidth="6">
        <start:Group Name="Important">
          <start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\Maciej Horbacz.lnk" />
          <start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\Fun.lnk" />
          <start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\Teams.lnk" />

And to block newly created tiles from editing by user you must specify parameter at line:

<DefaultLayoutOverride LayoutCustomizationRestrictionType="OnlySpecifiedGroups">

But the rest of the tiles will not be changed.

Such prepared xml can be deployed using Intune. Go to Configuration profiles, create Device restrictions profile, upload xml




And no other settings are required!


Chromium-Edge PWAs is such great feature! And taking advantage of it is simple a thing!
One last thing… make sure that the icons are somewhere to found the workstation

See you in next! 😉 🧠

Leave a comment