Preparing for the Teams 2.1 Client to Arrive

Get Ready to Deploy the New Teams Client to End Users

Updated March 27, 2023: The preview of the new Teams client is available.

With all the speculation that Microsoft will release a public preview of the new Teams (V2.1) client in late March 2023, it’s time to review how users can access the preview code once Microsoft makes it available.

Teams uses update policies to dictate which users have access to preview features. Teams also allows tenants to align with Office preview channels if they wish. The first job is therefore to define the user group to test the new Teams client and make sure to assign a Teams update policy that allows them to access preview features to their accounts. Once the policy is effective, users can switch between preview and production versions as they like.

A New Option in the Teams Update Policy

A hint that Microsoft will provide controls to allow customers to roll out the new Teams client at their own rate is in the PowerShell Get-CsTeamsUpdateManagementPolicy cmdlet. This reveals a UseNewTeamsClient setting. Microsoft added the setting in version 4.9.1 of the MicrosoftTeams PowerShell module in November 2022. The values accepted by the Set-CsTeamsUpdateManagementPolicy cmdlet are:

  • MicrosoftChoice: Microsoft controls the use of the new client. This is likely how Microsoft will force customers to eventually move from the old to the new client.
  • UserChoice: Individual users can choose to use the new client.
  • AdminDisabled: The organization disables the new client for users assigned the policy.

The interpretations of the options are mine and are not formally confirmed by Microsoft. The point is that it will be possible for organizations to control when users get the new client and which users get the new client.

Building a New Teams Architecture

Microsoft has been working on the new Teams client architecture for a long time. Some hints came in my May 2021 discussion with Rish Tandon (the then VP for Teams Engineering). At the time, Rish acknowledged that client performance wasn’t where Microsoft wanted it to be. A further hint came when Microsoft revealed the Teams consumer client for Windows 11. The consumer client uses the new Teams client architecture based on ReactJS and the WebView2 Edge component.

Of course, the Teams consumer client is a pale shadow of its enterprise counterpart when it comes to features and functionality, as people will discover when they move from Teams Free (classic) to the new Teams (free) version. There are no channels to deal with (regular, private, or shared), the number of users is limited, there’s no Phone system or Teams room devices, and so on. Acknowledging these limitations, the Teams consumer client (2.0 in the architecture) proved a useful step to proving the concepts and components used in the next generation of the Teams enterprise client (2.1).

Microsoft’s recent press briefings have emphasized benchmarks like a 50% reduction in memory, less demand for CPU, and a consequent extended battery life for laptops. Cynics might say that all of this comes from removing the overhead imposed by Electron. Certainly there’s some truth in that assertion but the overall engineering effort required to move the Teams desktop and browser clients to the new architecture spans more than simply swapping code libraries.

When Production Software Arrives

After running the public preview for the new version of the Teams client for several months, Microsoft will make the client generally available (GA). At that point, a recent change will affect when organizations see the GA software.

Microsoft 365 message center notification MC510331 (February 2, Microsoft 365 roadmap item 117577) announced that Teams will support targeted release for commercial cloud customers. In other words, if your tenant opts in to use targeted release for some or all users, you’ll be amongst the first to get the new Teams client. Release preferences are in the Org settings section of the Microsoft 365 admin center (Figure 1).

Release options for a Microsoft 365 tenant

Preparing for New Teams client
Figure 1: Release options for a Microsoft 365 tenant

Those who choose to remain with the standard release will receive the software later. Given the size of the Microsoft 365 infrastructure, the difference between first and last tenants receiving the new client could be several months.

A Big Moment Approaches for Teams

People have complained about the performance and memory consumption of the Teams client for years. Despite much tweaking and filling in performance gaps since 2016, it’s obvious that the road has run out for the original Teams client. Launching a new Teams client is an important point for Microsoft. They only have 280 million monthly active users to please. No pressure then!

Support the work of the Office 365 for IT Pros team by subscribing to the Office 365 for IT Pros eBook. Your support pays for the time we need to track, analyze, and document the changing world of Microsoft 365 and Office 365.

15 Replies to “Preparing for the Teams 2.1 Client to Arrive”

    1. I asked Microsoft about the site you pointed to. Their response is that it’s an internal method to distribute Teams builds. You won’t be able to install the new release unless you’re on an authorized list (Microsoft employee or TAP participant).

      1. It can be bypassed though so whatever “authorization” they’re doing clearly isn’t working.

        1) Open Telerik Fiddler Classic on your PC
        2) Go to in Google Chrome or your browser of choice.
        3) Find in Fiddler where d3abb3d5b68294df might be different for you but you can search for “config-prod” in Fiddler and you should get it.
        4) Go back to Fiddler and click on the AutoResponder tab.
        5) Click “Enable rules” & “Unmatched requests passthrough”
        6) Find config-prod-d3abb3d5b68294df.js in Fiddler and then double-click on it
        7) Right-click on config-prod-d3abb3d5b68294df.js and then select “Unlock for Editing”
        8) Find “disableExperience:[{buildType:[“local”],value:!1},{value:!0}]” and then replace it with “disableExperience:[{buildType:[“local”],value:!1},{value:!1}]”
        9) Drag to AutoResponder and you’re good to go.
        10) You can open and it’ll work + the Teams 2.1 client will also work too.

        I downloaded from as proof.

        Picture @

      2. @nickmaleao: I pasted the whole file on which should make this a bit more easier.

        You need to double-click on the “config-prod-XXXXXXXXXXXX.js” request and then right-click and select “Unlock for Editing” and then go to SyntaxView or TextView. Copy everything from Pastebin and then paste it into the SyntaxView or TestView. Please make sure to remove everything from SyntaxView/TextView first before pasting the entire text from Pastebin.

        An easiest way to get “config-prod-XXXXXXXXXXXX.js” to show up in Fiddler is use Incognito Mode on your browser and then go to

        On Fiddler, please make sure that “Enable rules” and “Unmatched requests passthrough” are both selected.

      3. Hi Coral, I was wondering if you are willing to get in touch with me on Twitter to help me out here. Fiddler’s not exactly my thing 😅

  1. To confirm Teams 2.1 will be rolled out as such?
    Currently – Microsoft/Tap (presumably).
    End of March – Public Preview controlled through Teams Admin Center update policies.
    Future – Targeted Release users in the tenant.

  2. On Mac I was able to access the v2 in a browser but not in the client. Is the setup different?

    1. You’d need the Mac 2.1 client. I’m not sure if it’s available yet (I don’t use Mac and have only ever used the 2.1 client on Windows 11).

  3. Im working wih teams v2 here: using overwrite source functionallity in browser (this case with Chrome). The sollution is easy:
    – Ovewrite file config-prod-xxx.js with disableExperience:[{buildType:[“local”],value:!1},{value:!1}]

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.