Intune App Packaging

How to Deploy Microsoft Teams (New) via Intune (Win32 Packaging Guide)

Published 17 March 2026 · 8 min read

Teams is one of the trickier apps to package for Intune. Microsoft moved from the classic Teams client to the new Teams (Teams 2.0) in 2024, and the packaging approach is different for each. This guide covers the new Teams MSIX/bootstrapper approach, which is the correct method for fresh deployments as of 2024 onwards.

Contents
  1. New Teams vs classic Teams
  2. Download the bootstrapper
  3. Wrap with the Content Prep Tool
  4. Add the app in Intune
  5. Install and uninstall commands
  6. Detection rule
  7. Known gotchas

New Teams vs classic Teams

As of late 2024, Microsoft has replaced the classic Teams client (which was an Electron app) with the new Teams client built on Edge WebView2. The packaging approach is different:

⚠️
Do not deploy the classic Teams MSI to new deployments
If you are setting up Teams for the first time, use the new Teams bootstrapper. Classic Teams was retired in July 2024 and will not receive security updates.

Download the bootstrapper and MSIX

Microsoft provides the new Teams bootstrapper on their official page. You need two files:

Bootstrapper: https://go.microsoft.com/fwlink/?linkid=2243204&clcid=0x409
MSIX package: https://go.microsoft.com/fwlink/?linkid=2196106

Download both files and place them in the same source folder (e.g. C:\AppSource\Teams).

💡
Check for updated download links
Microsoft occasionally updates these URLs. Confirm you have the latest links from the Microsoft Teams admin documentation before packaging.

Wrap with the Content Prep Tool

The bootstrapper EXE is the setup file, but both files need to be in the source folder:

IntuneWinAppUtil.exe -c "C:\AppSource\Teams" -s "teamsbootstrapper.exe" -o "C:\IntunePackages"

Add the app in Intune

Intune Admin Centre → Apps → Windows → + Add → Windows app (Win32)
  1. Upload the .intunewin file
  2. Name: Microsoft Teams
  3. Publisher: Microsoft Corporation

Install and uninstall commands

⚙️
Program settings
[]
Install command-p provisions for all users on the machine, -o specifies the MSIX file path
teamsbootstrapper.exe -p -o "MSTeams-x64.msix"
Uninstall command-x removes the provisioned Teams package
teamsbootstrapper.exe -x
Install behaviour
System
Device restart behaviour
No specific action

Detection rule

New Teams installs as an MSIX package, so use a registry detection rule rather than a file path:

🔍
Registry detection rule
[]
Rule type
Registry
Key path
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Teams
Value name
Version
Detection method
Key exists

Alternatively, use a PowerShell detection script:

# Detect new Microsoft Teams
$teamsPackage = Get-AppxPackage -AllUsers -Name "MSTeams" -ErrorAction SilentlyContinue
if ($teamsPackage) {
    Write-Output "Detected: $($teamsPackage.Version)"
    exit 0
} else {
    exit 1
}
💡
Test your detection rule first
Before deploying to users, install the app manually on a test device and verify the detection rule matches. Run the detection script or check the file path exists before assigning to a group.

Known gotchas

WebView2 dependency

New Teams requires Microsoft Edge WebView2 Runtime. On Windows 11 this is pre-installed. On Windows 10, deploy WebView2 as a dependency in Intune before Teams. Add it as a required dependency on the Teams Win32 app.

WebView2 bootstrapper download:

https://go.microsoft.com/fwlink/p/?LinkId=2124703

Teams appearing in both work and personal accounts

New Teams on Windows 11 may show both the personal and work versions. The work version is the one deployed via Intune. The personal version is a Windows 11 inbox app. You can remove the personal version via a PowerShell script targeting the MicrosoftTeams Appx package (note: different package name from MSTeams which is the work version).

Machine-level vs per-user Teams

The -p flag provisions Teams at machine level so it is available to all users who sign in. Without this flag it installs per-user only.

Installer typeMSIX via bootstrapper EXE
Silent installYes - teamsbootstrapper.exe -p -o MSIX
DependencyEdge WebView2 (pre-installed on Win 11)
Detection methodRegistry key or PowerShell
Reboot requiredNo

Frequently Asked Questions

Q: How do I deploy the new Microsoft Teams via Intune?

Download teamsbootstrapper.exe and MSTeams-x64.msix from Microsoft, wrap with IntuneWinAppUtil, then use the install command: teamsbootstrapper.exe -p -o "MSTeams-x64.msix"

Q: What is the difference between classic Teams and new Teams?

Classic Teams was retired in July 2024. New Teams uses the MSIX bootstrapper deployment method instead of the old Machine-Wide Installer MSI. For new deployments, always use the new Teams approach.

Q: Does new Microsoft Teams require WebView2?

Yes. New Teams requires Microsoft Edge WebView2 Runtime. On Windows 11 this is pre-installed. On Windows 10, deploy WebView2 as a required dependency in Intune before Teams.

Q: How do I detect new Microsoft Teams in Intune?

Use a PowerShell detection script: Get-AppxPackage -AllUsers -Name "MSTeams". If the package exists, exit 0. Otherwise exit 1.

// need intune set up properly?
Fixed-price Intune setup for UK businesses

I set up Intune for UK small businesses at a fixed price - app deployment, compliance policies, Conditional Access, and full documentation handed over at the end.

View Packages
More App Packaging Guides
→ Deploy Slack via Intune→ Deploy Zoom via Intune→ Deploy Google Chrome via Intune
#intune #app-packaging #win32 #endpoint-management