Skip to content
Submit a ticket
  • There are no suggestions because the search field is empty.

Intune Deployment: Install the Decisions Desktop App (PWA) at Scale

Deploy the Decisions desktop Progressive Web App (PWA) to Windows users using Microsoft Intune.

Overview

The Decisions “desktop” experience is a Progressive Web App (PWA), not a Win32 program. That’s why the Decisions download opens a browser install flow and no .msi or .exe is available. This article shows two supported Intune deployment options for organization-wide rollout.

Also remember: You can centrally deploy the Decisions Teams app from the Teams admin center. See our guide: Deploying the Decisions Teams App

What You’ll Need

  • Microsoft Intune with target user groups

  • Windows 10/11 devices with Microsoft Edge (or Google Chrome for the script option)

  • Decisions web app URL: https://app.boarddecisions.com/

Option A — Force-Install With Microsoft Edge Policy (Recommended ✅)

Use Intune Administrative Templates to silently install the PWA per user and add a Start menu entry.

  • In Intune: Devices → Configuration profiles → Create profile

  • Platform: Windows 10 and later

  • Profile Type: Templates → Administrative Templates

  • Open Microsoft Edge settings and configure Configure the list of force-installed web apps (WebAppInstallForceList)

  • Add the Decisions web app URL: https://app.boarddecisions.com/ and a friendly name like Decisions

  • Assign the profile to your target user groups

💡 Result: Edge installs the PWA per user, silently, and creates Start menu/desktop shortcuts.

Option B — Deploy a Scripted Install via Intune (Edge or Chrome)

If you prefer a script, push this PowerShell as a user-context script. It installs the PWA with Edge first, then Chrome if Edge isn’t present.

 
# Decisions PWA install via Edge/Chrome

$Url = "https://app.boarddecisions.com/"




$Edge = "$env:ProgramFiles(x86)\Microsoft\Edge\Application\msedge.exe"

if (Test-Path $Edge) {

Start-Process -FilePath$Edge -ArgumentList"--install-app=$Url --silent" -WindowStyleHidden -Wait

exit0

}




$Chrome = "$env:ProgramFiles(x86)\Google\Chrome\Application\chrome.exe"

if (Test-Path $Chrome) {

Start-Process -FilePath$Chrome -ArgumentList"--install-app=$Url --silent" -WindowStyleHidden -Wait

exit0

}




exit 1

 Detection Rule (Example)

  • Check for the Start menu shortcut created after install:

    • %APPDATA%\Microsoft\Windows\Start Menu\Programs\Decisions.lnk

    • or $env:APPDATA\Microsoft\Windows\Start Menu\Programs\Decisions.lnk

FAQ and Tips

  • Is There an MSI/EXE? No. Decisions is delivered as a PWA, so no standalone installer is distributed.

  • Per-User or Per-Device? PWAs install per user. Target assignments to user groups.

  • Updates? The PWA updates automatically through the browser engine.

  • Uninstall? Users can remove the app from the Start menu or the browser’s Apps list; admins can also remove the policy or script assignment.

Troubleshooting

  • No Shortcut Appears: Confirm policy assignment, user sign-in, and that Edge is installed and allowed to install PWAs.

  • Multiple Browsers Installed: The script prefers Edge; it falls back to Chrome if Edge isn’t found.

  • Firewall/SSL Inspection: Allow https://app.boarddecisions.com/.

Suggested tags: Intune Deployment, Decisions Desktop, PWA, Microsoft Edge Policy, WebAppInstallForceList, Windows 10/11, Microsoft Endpoint Manager, Silent Install, Chrome PWA