Welcome to the build repository for Microsoft Teams
This README.md file has not been updated for nearly a year or more and may contain inaccuracies.
This repository contains multiple files:
- defconfig which shows daily builds, experimental builds, preview builds, and public builds for Microsoft Teams classic.
- defconfig2 which shows builds in all rings for Microsoft Teams classic, Microsoft Teams (personal), Microsoft Teams, and Microsoft Teams Rooms.
This repository contains the source code for:
- Get-MicrosoftTeams.ps1 which allows you to fetch the latest builds in different environments, and different rings.
- launch.ps1 which allows you to create your own
RELEASES file.
[!NOTE]
Installing these builds does not necessarily mean you will have access to new features.
For more information, please visit this blog post.
Frequently Asked Questions (FAQ)
Teams 1.0 — Microsoft Teams classic based on Electron 22.3.27 and Electron 31.7.7
What are daily builds?
Preview the latest development builds of Microsoft Teams.
These builds may also contain newer versions of SlimCore.
What are experimental builds?
Preview the latest development builds of Microsoft Teams but with access to new ideas which may or may not ship into daily builds. These builds may also contain newer versions of SlimCore.
-E will be displayed in the three-dot menu (...) > About > Version:
Teams 2.0 — Microsoft Teams (personal) based on Microsoft Edge WebView2
Teams 2.1 — Microsoft Teams based on Microsoft Edge WebView2
Teams 2.1 — Microsoft Teams Rooms based on Microsoft Edge WebView2
What are Canary (R0) builds?
Preview the latest development builds of Microsoft Teams.
What are Canary SlimCore (R0s) builds?
Preview the latest development builds of Microsoft Teams but with access to newer versions of SlimCore.
What does Microsoft Teams version 1.7.00.4065 mean?
We use the 1.X.00.DDDXX version format for Teams 1.0.
Here is an example:
Microsoft Teams version 1.7.00.4065 is broken down into the following:
7 (X) is the year of the build.
8 represents 2025.7 represents 2024.6 represents 2023.5 represents 2022.4 represents 2021.3 represents 2020.2 represents 2019.1 represents 2018.0 represents 2017.
40 (DDD) is the day number of that year.
40 represents Friday, February 9, 2024.39 represents Thursday, February 8, 2024.38 represents Wednesday, February 7, 2024.
65 (XX) is automatically generated by Azure DevOps.
We have two build flavors for Teams 1.0:
Stable (S) = Any build version ending with 51 to 99 is a stable build.Experimental (E) = Any build version ending with 1 to 49 is an experimental build.
What does Microsoft Teams version 24041.300.2689.9173 mean?
We use the YYDDD.XXXX.XXXX.XXXX version format for Teams 2.0 and Teams 2.1.
Here is an example:
Microsoft Teams version 24041.300.2689.9173 is broken down into the following:
24 (YY) is the year of the build.041 (DDD) is the day number of that year.
041 represents Saturday, February 10, 2024.040 represents Friday, February 9, 2024.039 represents Thursday, February 8, 2024.
300 (XXXX) is automatically generated by Azure DevOps.2689 (XXXX) is the amount of builds we have created excluding servicing builds.9173 (XXXX) is automatically generated by Azure DevOps.
What does client version 49/24031000600 mean?
We use the XXXX/YYMMDDXXXXX version format for the React Web Client (RWC).
Here is an example:
Client version 49/24031000600 is broken down into the following:
49 (XXXX) is the platform ID.
24 (YY) is the year of the build.03 (MM) is the month of the build.10 (DD) is the day of the build.00600 (XXXXX) is automatically generated by Azure DevOps.
Microsoft Teams supports the version parameter which allows you to force different versions of the React Web Client (RWC).
Here are a few examples:
Microsoft Teams uses platform IDs to differentiate different platforms for flighting, telemetry, and more.
Here are a few examples:
| Platform ID |
Friendly Name |
| 27 |
Microsoft Teams classic based on Electron (Windows) |
| 28 |
Microsoft Teams classic based on Electron (macOS) |
| 34 |
Microsoft Teams Rooms based on Electron (Windows) |
| 35 |
Microsoft Teams classic for Surface Hub based on Electron (Windows) |
| 38 |
Microsoft Teams classic for Surface Hub 2 based on Electron (Windows) |
| 41 |
Microsoft Teams classic based on Electron (Linux) |
| 48 |
Microsoft Teams (personal) based on Microsoft Edge WebView2 (Windows) |
| 49 |
Microsoft Teams based on Microsoft Edge WebView2 (Windows) |
| 50 |
Microsoft Teams based on Microsoft Edge WebView2 (macOS) |
| 51 |
Microsoft Teams Rooms based on Microsoft Edge WebView2 (Windows) |
| 1415 |
Microsoft Teams Web (Windows, macOS, and Linux) |
| 1416 |
Microsoft Teams (Android) |
| 1417 |
Microsoft Teams (iOS) |
| 1449 |
Microsoft Teams Rooms (Android) |
| 1454 |
Microsoft Teams PWA (Linux) |
Teams 2.0 — Microsoft Teams (personal):
You will have to create a JSON file named configuration.json in %LOCALAPPDATA%\Packages\MicrosoftTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams:
{
"core/devMenuEnabled": true
}
Teams 2.1 — Microsoft Teams:
You will have to create a JSON file named configuration.json in %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams:
{
"core/devMenuEnabled": true
}
Teams 2.1 — Microsoft Teams Rooms:
You will have to create a JSON file named configuration.json in %LOCALAPPDATA%\Packages\MSTeamsRooms_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams:
{
"core/devMenuEnabled": true
}
How can I use this repository for my scripts?
Microsoft Teams uses Experimentation and Configuration Service (ECS) to retrieve the latest builds, experiments, feature flags, settings, and more.
Here are a few examples:
Here are a few examples of these parameters:
| Parameter |
Value |
environment |
dev; prod; life; gcc; gcchigh; dod; gallatin; ag08; ag09 |
audienceGroup |
ring0; ring0_s; ring1; ring1_5; ring1_6; ring2; ring3; ring3_6; ring3_9; general; general_gcc |
teamsRing |
ring0; ring0_s; ring1; ring1_5; ring1_6; ring2; ring3; ring3_6; ring3_9; general; general_gcc |
experience |
cdl-worker; react-web-client; multi-window; meeting-room |
buildType |
production; container; local |
osPlatform |
windows; mac; linux; chromeos; android; ios |
id |
Your Object ID from Microsoft Entra ID.
This repository uses 3a7cf1d3-06fa-4ead-bf45-a6286ff2620a |
aaduserid |
Your Object ID from Microsoft Entra ID.
This repository uses 3a7cf1d3-06fa-4ead-bf45-a6286ff2620a |
tenantId |
Your Tenant ID from Microsoft Entra ID.
This repository uses 72f988bf-86f1-41af-91ab-2d7cd011db47 |
agent |
Segmentation; TeamsBuilds; TeamsNorthstar; TeamsWebview2 |
评论