Deploy New Microsoft Teams App on Windows using Intune

In this blog post, we will explore the process of deploying the New Microsoft Teams app on Windows 10 and Windows 11 devices using the Intune admin center.

Microsoft has completely redesigned the New MS Teams app. It was made generally available to users starting on October 5, 2023. It’s twice as fast and uses 50% less computing resources than the previous Teams version.

You can read more about the new Microsoft Teams app here: Switch to the new Microsoft Teams. If you want to deploy the new Microsoft Teams app on macOS devices, please refer to this guide: Deploy New Microsoft Teams on macOS using Intune.

How to deploy Zoom using Intune

Step-by-Step guide

Step 1 – Download New Microsoft Teams App

The first step is to download the necessary installation files required for deploying the New Microsoft Teams App. We will require two installations: teamsbootstrapper.exe and MSTeams-x64.msix for offline Installation of new MS Teams app. You can obtain both files by using the links provided below:

  1. Download the .exe installer
  2. Download MSTeams-x64.msix

If you intend to deploy the New Microsoft Teams app on a Windows operating system with an architecture other than 64-bit, you’ll need to download the corresponding .msix from the Microsoft website and use it for the deployment.

Step 2 – Download Powershell Scripts

To deploy the new Microsoft Teams app on Windows devices, I’ll utilize the following three PowerShell scripts.

  • Install.ps1: This script will deploy the new Microsoft Teams using its offline installer.
  • Uninstall.ps1: This script will uninstall the new Microsoft Teams App.
  • Detect.ps1: This script will detect the presence of the new Microsoft Teams App on the target devices.

You can download all these scripts from my GitHub repository. Here is the link: Microsoft Teams (new) PowerShell scripts. I have also provided the scripts content below:

Install.ps1

<# 
.SYNOPSIS 
Install New Microsoft Teams App on target devices 
.DESCRIPTION 
Below script will install New MS Teams App Offline.
 
.NOTES     
        Name       : New MS Teams App Installation Offline
        Author     : Jatin Makhija  
        Version    : 1.0.0  
        DateCreated: 12-Jan-2024
        Blog       : https://cloudinfra.net
         
.LINK 
https://cloudinfra.net 
#>
# Define paths and filenames
$msixFile = ".\MSTeams-x64.msix"
$destinationPath = "C:\windows\temp"
$bootstrapperPath = ".\teamsbootstrapper.exe"

# Copy MSTeams-x64.msix to the destination directory
Copy-Item -Path $msixFile -Destination $destinationPath -Force

# Check if the copy operation was successful
if ($?) {
    # If successful, execute teamsbootstrapper.exe with specified parameters
    Start-Process -FilePath $bootstrapperPath -ArgumentList "-p", "-o", "$destinationPath\MSTeams-x64.msix" -Wait -WindowStyle Hidden
    Write-Host "Microsoft Teams installation completed successfully."
} else {
    # If copy operation failed, display an error message
    Write-Host "Error: Failed to copy MSTeams-x64.msix to $destinationPath."
    exit 1
}

Uninstall.ps1

./teamsbootstrapper -x

Detect.ps1

<# 
.SYNOPSIS 
Detect New Microsoft Teams App on target devices 
.DESCRIPTION 
Below script will detect if New MS Teams App is installed.
 
.NOTES     
        Name       : New MS Teams Detection Script
        Author     : Jatin Makhija  
        Version    : 1.0.0  
        DateCreated: 12-Jan-2024
        Blog       : https://cloudinfra.net
         
.LINK 
https://cloudinfra.net 
#>
# Define the path where New Microsoft Teams is installed
$teamsPath = "C:\Program Files\WindowsApps"

# Define the filter pattern for Microsoft Teams installer
$teamsInstallerName = "MSTeams_*"

# Retrieve items in the specified path matching the filter pattern
$teamsNew = Get-ChildItem -Path $teamsPath -Filter $teamsInstallerName

# Check if Microsoft Teams is installed
if ($teamsNew) {
    # Display message if Microsoft Teams is found
    Write-Host "New Microsoft Teams client is installed."
    exit 0
} else {
    # Display message if Microsoft Teams is not found
    Write-Host "Microsoft Teams client not found."
    exit 1
}

Step 3 – Create an Intunewin file

As we will be utilizing the Win32 app deployment method to deploy this app, the application must be uploaded in the .intunewin file format. Let’s check the steps to create .intunewin file:

  • Create a New folder that will hold all New Microsoft Teams app Installation files. I have created a folder in C:\temp called NewTeamsInstaller.
  • Move All Installation files into the NewTeamsInstaller folder, which includes the below files:
    1. Install.ps1
    2. Uninstall.ps1
    3. MSTeams-x64.msix
    4. teamsbootstrapper.exe
Copy all MS Teams Installation files in one folder
Copy all MS Teams Installation files in one folder
  • Create an empty folder called Output anywhere in C:\ or D:\ drive. You can name it whatever you like. This will be the folder where we will generate .Intunewin file. I have created this folder in C:\temp.
Create a folder called Output where we will generate .Intunewin file
Create a folder called Output where we will generate .Intunewin file
  • Launch the Powershell console as an administrator and then navigate to the folder where the Microsoft Win32 Content Prep Tool is located to set it as the current directory.
  • Run IntunewinAppUtil.exe You will get options to specify the Source Folder, Setup File, Output Folder, and Catalog Folder.
    • Source Folder: Provide the folder where all application setup files are copied. C:\temp\NewTeamsInstaller.
    • Setup File: Provide the file’s name to execute on the target device. We are going to use Install.ps1 file to Install the app. Therefore, provide the Setup file as Install.ps1.
    • Output folder: Provide a location of a folder where .Intunewin file will be generated. You can provide any folder you like, But I generally create an empty Output folder. C:\temp\Output.
    • Catalog folder: Specify N not to specify any Catalog folder or press Enter to skip.
Use IntuneWinAppUtil.exe to create .Intunewin file
Use IntuneWinAppUtil.exe to create .Intunewin file
  • You can find the .intunewin file generated in the “Output folder” location that was specified while creating this file. We will use this file to create the Win32 app deployment from the Intune admin center.
New Microsoft Teams App .intunewin file has been created successfully
New Microsoft Teams App .intunewin file has been created successfully

If you are facing any Issues creating .Intunewin file. You can refer to my step-by-step guide which provides more details on “How to create an IntuneWin file.

How to create Intunewin file (Step-by-step) Guide

Step 4 – Create Win32 App Deployment for New Teams App

Now that we have created .intunewin file. Using this file, we will create a Win32 app deployment on the Intune admin center to deploy the New Microsoft Teams app on the target devices.

`To Create Win32 app deployment, follow below steps:

  1. Login on Microsoft Intune admin center.
  2. Click on Apps and then click on All Apps.
  3. Click on + Add and Select Windows app (Win32) from the app type, then click Select.

App Information

Click on “Select app package file” and browse to .Intunewin file.

New MS Teams App Win32 App deployment - App Information tab
New MS Teams App Win32 App deployment – App Information tab

Provide Information in the mandatory fields below. The rest of the fields are optional but useful for application documentation and troubleshooting issues.

Required Fields:

  • Name – Provide a unique name of the application.
  • Description – Provide a useful description.
  • Publisher – Provide Publisher Information. For Example: Microsoft.
New MS Teams App Win32 App deployment - App Information tab
New MS Teams App Win32 App deployment – App Information tab

Program

Provide the Install command, uninstall commandInstall behavior, and Device restart behavior. Click on Next to proceed.

  • Install command: %SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -windowstyle hidden -executionpolicy bypass -command .\install.ps1
  • Uninstall command: %SystemRoot%\sysnative\WindowsPowerShell\v1.0\powershell.exe -windowstyle hidden -executionpolicy bypass -command .\uninstall.ps1
  • Installation time required (mins): Keep default which is 60 minutes.
  • Allow available uninstall: Yes
  • Install behavior: System
  • Device restart behavior: Select No specific action.
New MS Teams App Win32 App deployment - Program tab
New MS Teams App Win32 App deployment – Program tab

Requirements

You can specify the requirements that devices must meet to deploy the app. If your devices are a mix of 32-bit and 64-bit types, check the boxes for 32-bit and 64-bit in the operating system architecture drop-down menu. Else, go with 64-bit.

  • Operating System Architecture: 64-bit
  • Minimum operating system: Select the minimum OS requirement for this deployment.

Detection Rules

We will utilize the Detect.ps1 PowerShell script to identify the app installation on the target computers. Follow the settings below to configure the detection script for the app deployment. Click on Next to proceed. Download Detect.ps1 from the Github Repo: Download Detect.ps1 from Github.

  • Rule format: Use a custom detection script.
  • Script file: Browse to the Powershell script Detect.ps1.
  • Run script as 32-bit process on 64-bit clients: No
  • Enforce script signature check and run script silently: No
New MS Teams App Win32 App deployment - Detection Rules tab
New MS Teams App Win32 App deployment – Detection Rules tab

Dependencies

Click Next.

Supersedence

Click Next.

Assignments

Click on Add group to add an Entra security group containing users or devices. You can start with adding a few devices in the group to test the application deployment, and once the testing is successful, add more devices.

New MS Teams App Win32 App deployment - Assignments tab
New MS Teams App Win32 App deployment – Assignments tab

Review + Create

Review the deployment and click on Create to start the deployment process.

Sync Intune Policies

The device check-in process might not begin immediately. If you’re testing this policy on a test device, you can manually kickstart Intune sync either from the device itself or remotely through the Intune admin center.

Alternatively, you can use PowerShell to force the Intune sync on Windows devices. Another way to trigger the Intune device check-in process is by restarting the device.

Step 5 – Monitoring Deployment Progress

You can follow below steps to monitor the installation:

From the Microsoft Intune admin center >Apps > All apps. Click on the MS Teams app deployment and check the Overview page, which will show the deployment status.

Monitoring New Microsoft Teams App deployment status on Intune admin center
  • If you click ‘Device Install Status,’ you will find the app deployment status for each target device. Confirm the success of the deployment by checking the ‘Status‘ column, which should show as ‘Installed.'”
Monitoring New Microsoft Teams App deployment status on Intune admin center
Monitoring New Microsoft Teams App deployment status on Intune admin center

End-user Experience

After the successful completion of the app deployment on the target devices, follow the steps below to check and confirm the app installation on a device:

  • Click on the Windows logo and search for the “Teams” app.
  • If the app is installed successfully, you will find the Microsoft Teams (work or school) app with the new logo. This confirms that the App has been deployed on the devices successfully.
Confirm the Installation of New Microsoft Teams app from the Start Menu
Confirm the Installation of New Microsoft Teams app from the Start Menu

Further Reading

To learn more about the New Microsoft Teams App, explore the links below:

11 thoughts on “Deploy New Microsoft Teams App on Windows using Intune”

  1. Is this install system wide context? Our organization does not want Teams installed on a per profile basis which leads to out of date clients if a user hasn’t logged into the machine in a while to update their install.

    Reply
    • Yes, the “Install behavior” is set to “System” in the Program tab when creating the app deployment. Therefore, the installation will occur in the System Context. I hope this answers your query.

      Reply
  2. Many Thanks, QQ I get a Edge Webview2 runtime Requirement on launch. is that something that auto deploys as this worked via Co portal / live system but on autopilot it installed this package but said lacked Edge Webview2 Runtime (so wondered if I need to make a dependancy app to deploy this as a Device app. – Or better to do as user as This Runtime might get auto added later?

    Reply
  3. works pretty good, the first time it stated the app was installed but it was not. Had to do a uninstall and then the next install worked.

    Reply
  4. My devices come with an office suite including Teams Personal and want to uninstall Teams personal and install Teams work or school only. Devices are enrolled as Windows Autopilot. What would be the best practice?

    Reply

Leave a Comment