Teams Web

  1. Microsoft Teams is a hub for teamwork in Microsoft 365 for Education. Keep all your content, apps, and conversations together in one place.
  2. Microsoft Teams is a web-based desktop app, developed on top of the Electron framework from GitHub which combines the Chromium rendering engine and the Node.js JavaScript platform. This article is in list format, but may read better as prose. You can help by converting this.
  3. Some browsers, such as Internet Explorer 11, Safari, and Firefox, support the Microsoft Teams web app but don't support some of the Teams calling and meeting features. To work around this limitation, the Teams web app lets users receive audio through a PSTN connection and lets them view presented content (screen share) at a reduced display rate.
-->

Microsoft Teams has clients available for desktop (Windows, Mac, and Linux), web, and mobile (Android and iOS). These clients all require an active internet connection and do not support an offline mode.

Note

For details about each clients' capabilities on different platforms, see Teams features by platform.

Teams Meeting add-in in Outlook Web App The Teams Meetings button in Outlook Web App will appear as part of new event creation if the user is on an early version of the new Outlook on the web. See the Outlook Blog to learn about how users can try the early version of the new Outlook on the web.

Effective November 29, 2018, you'll no longer be able to use the Microsoft Teams for Windows 10 S (Preview) app, available from the Microsoft Store. Instead, you can now download and install the Teams desktop client on devices running Windows 10 S mode. To download the desktop client, go to https://teams.microsoft.com/downloads. MSI builds of the Teams desktop client are not yet available for devices running Windows 10 S mode.

For more information about Windows 10 S mode, see Introducing Windows 10 in S mode.

Desktop client

Tip

Watch the following session to learn about the benefits of the Windows Desktop Client, how to plan for it, and how to deploy it: Teams Windows Desktop Client

The Microsoft Teams desktop client is a standalone application and is also available in Microsoft 365 Apps for enterprise. Teams is available for 32-bit and 64-bit versions of Windows (8.1 or later), ARM64 for Windows 10 on ARM, and Windows Server (2012 R2 or later), as well as for macOS and Linux (in .deb and .rpm formats). On Windows, Teams requires .NET Framework 4.5 or later; the Teams installer will offer to install it for you if you don't have it. On Linux, package managers such as apt and yum will try to install any requirements for you. However, if they don't then you will need to install any reported requirements before installing Teams on Linux.

The desktop clients provide real-time communications support (audio, video, and content sharing) for team meetings, group calling, and private one-on-one calls.

Desktop clients can be downloaded and installed by end users directly from https://teams.microsoft.com/downloads if they have the appropriate local permissions (admin rights are not required to install the Teams client on a PC but are required on a Mac).

Note

For more details about installing Teams on a Chromebook, please see How to install and run Microsoft Office on a Chromebook.

IT admins can choose their preferred method to distribute the installation files to computers in their organization. Some examples include Microsoft Endpoint Configuration Manager (Windows) or Jamf Pro (macOS). To get the MSI package for Windows distribution, see Install Microsoft Teams using MSI.

Note

Distribution of the client via these mechanisms is only for the initial installation of Microsoft Team clients and not for future updates.

Windows

The Microsoft Teams installation for Windows provides downloadable installers in 32-bit and 64-bit architecture.

Note

The architecture (32-bit vs. 64-bit) of Microsoft Teams is agnostic to the architecture of Windows and Office that is installed.

The Windows client is deployed to the AppData folder located in the user’s profile. Deploying to the user’s local profile allows the client to be installed without requiring elevated rights. The Windows client leverages the following locations:

  • %LocalAppData%MicrosoftTeams

  • %LocalAppData%MicrosoftTeamsMeetingAddin

  • %AppData%MicrosoftTeams

  • %LocalAppData%SquirrelTemp

When users initiate a call using the Microsoft Teams client for the first time, they might notice a warning with the Windows firewall settings that asks for users to allow communication. Users might be instructed to ignore this message because the call will work, even when the warning is dismissed.

Note

Windows Firewall configuration will be altered even when the prompt is dismissed by selecting “Cancel”. Two inbound rules for teams.exe will be created with Allow action for both TCP and UDP protocols.

If you want to prevent Teams from prompting users to create firewall rules when the users make their first call from Teams, use the Sample PowerShell script - inbound firewall rule below.

Mac

Mac users can install Teams by using a PKG installation file for macOS computers. Administrative access is required to install the Mac client. The macOS client is installed to the /Applications folder.

Install Teams by using the PKG file

  1. From the Teams download page, under Mac, click Download.
  2. Double click the PKG file.
  3. Follow the installation wizard to complete the installation.
  4. Teams will be installed to /Applications folder. It is a machine-wide installation.

Note

During the installation, the PKG will prompt for admin credentials. The user needs to enter the admin credentials, regardless of whether or not the user is an admin.

If a user currently has a DMG installation of Teams and wants to replace it with the PKG installation, the user should:

  1. Exit the Teams app.
  2. Uninstall the Teams app.
  3. Install the PKG file.

IT admins can use managed deployment of Teams to distribute the installation files to all Macs in their organization, such as Jamf Pro.

Note

If you experience issues installing the PKG, let us know. In the Feedback section at the end of this article, click Product feedback.

Linux

Users will be able to install native Linux packages in .deb and .rpm formats. Installing the DEB or RPM package will automatically install the package repository.

  • DEB https://packages.microsoft.com/repos/ms-teams stable main
  • RPM https://packages.microsoft.com/yumrepos/ms-teams

The signing key to enable auto-updating using the system's package manager is installed automatically. However, it can also be found at: https://packages.microsoft.com/keys/microsoft.asc. Microsoft Teams ships monthly and if the repository was installed correctly, then your system package manager should handle auto-updating in the same way as other packages on the system.

Note

If you find a bug, submit it using Report a Problem from within the client. For known issues, see Support Teams in your organization.For Teams for Linux support you can use the Linux forum support channel on Microsoft Q&A. Be sure to use the teams-linux tag when posting questions.

Install Teams using DEB package

  1. Download the package from https://aka.ms/getteams.
  2. Install using one of the following:
    • Open the relevant package management tool and go through the self-guided Linux app installation process.
    • Or if you love Terminal, type: sudo dpkg -i **teams download file**
Web

You can launch Teams via Activities or via Terminal by typing teams.

Install Teams using RPM package

  1. Download the package from https://aka.ms/getteams.
  2. Install using one of the following:
    • Open the relevant package management tool and go through the self-guided Linux app installation process.
    • Or if you love Terminal, type: sudo yum install **teams download file**

You can launch Teams via Activities or via Terminal by typing teams.

Install manually from the command line

Install manually on Debian and Ubuntu distributions:

Install manually on RHEL, Fedora and CentOS based distributions:

Alternatively, to use yum instead of dnf:

Install manually on openSUSE based distributions:

Web client

The web client (https://teams.microsoft.com) is a full, functional client that can be used from a variety of browsers. The web client supports Calling and Meetings by using webRTC, so there is no plug-in or download required to run Teams in a web browser. The browser must be configured to allow third-party cookies.

Teams fully supports the following Internet browsers, with noted exceptions for calling and meetings. This table applies to operating systems running on desktop computers.

BrowserCalling - audio, video, and sharingMeetings - audio, video, and sharing123
Internet Explorer 11Not supportedMeetings are supported only if the meeting includes PSTN coordinates. To attend a meeting on IE11 without PSTN coordinates, users must download the Teams desktop client.
Video: Not supported
Sharing: Incoming sharing only (no outgoing)
Microsoft 365 apps and services will not support Internet Explorer 11 starting August 17, 2021 (Microsoft Teams will not support Internet Explorer 11 earlier, starting November 30, 2020). Learn more. Please note that Internet Explorer 11 will remain a supported browser. Internet Explorer 11 is a component of the Windows operating system and follows the Lifecycle Policy for the product on which it is installed.
Microsoft Edge, RS2 or laterFully supported, except no outgoing sharing4Fully supported, except no outgoing sharing
Microsoft Edge (Chromium-based), the latest version plus two previous versionsFully supportedFully supported
Google Chrome, the latest version plus two previous versionsFully supportedFully supported
Sharing is supported without any plug-ins or extensions on Chrome version 72 or later.
Safari 14+1:1 calls not supported. Group calls fully supported.
Video: Fully supported
Sharing: Fully supported
Meetings: Fully supported
Video: Fully supported
Sharing: Fully supported
Safari 13.1+1:1 calls not supported. Group calls supported with full audio support.
Video: Incoming only
Sharing: Fully supported
Meetings are supported with full audio support.
Video: Incoming only
Sharing: Fully supported
Firefox, the latest version plus two previous versionsNot supportedMeetings are supported only if the meeting includes PSTN coordinates. To attend a meeting on Firefox without PSTN coordinates, users must download the Teams desktop client.
Video: Not supported
Sharing: Incoming sharing only (no outgoing)
Safari versions before 13Not supportedMeetings are supported only if the meeting includes PSTN coordinates. To attend a meeting on Safari without PSTN coordinates, users must download the Teams desktop client.
Video: Not supported
Sharing: Incoming sharing only (no outgoing)
Safari is enabled on versions higher than 11.1 in preview. While in preview, there are known issues with Safari's Intelligent Tracking Prevention.

1 To give and take control of shared content during sharing, both parties must be using the Teams desktop client. Control isn't supported when either party is running Teams in a browser. This is due to a technical limitation that we're planning to fix.

2 Blur my background isn't available when you run Teams in a browser. This feature is only available in the Teams desktop client.

3 Teams meetings on browsers are limited to a single incoming video feed of active speaker.

4 Edge RS2 or later doesn't support sending real-time audio and video traffic through HTTP proxies.

Note

As long as an operating system can run the supported browser, Teams is supported on desktop computers. For example, running Firefox on the Linux operating system is an option for using Teams.

For mobile operating systems, we recommend that you run the Teams app, available from the Android and iOS stores. Running Teams in a mobile operating system is supported, but many features are unavailable.

The web client performs browser version detection upon connecting to https://teams.microsoft.com. If an unsupported browser version is detected, it will block access to the web interface and recommend that the user download the desktop client or mobile app.

Mobile clients

The Microsoft Teams mobile apps are available for Android and iOS, and are geared for on-the-go users participating in chat-based conversations and allow peer-to-peer audio calls. For mobile apps, go to the relevant mobile stores Google Play and the Apple App Store. The Windows Phone App was retired July 20, 2018 and may no longer work.

In China, here's how to get Teams for Android.

Supported mobile platforms for Microsoft Teams mobile apps are the following:

  • Android: Support is limited to the last four major versions of Android. When a new major version of Android is released, the new version and the previous three versions are officially supported.

  • iOS: Support is limited to the two most recent major versions of iOS. When a new major version of iOS is released, the new version of iOS and the previous version are officially supported.

Note

The mobile version must be available to the public in order for Teams to work as expected.

Mobile apps are distributed and updated through the respective mobile platform’s app store only. Distribution of the mobile apps via MDM or side-loading is not supported by Microsoft. Once the mobile app has been installed on a supported mobile platform, the Teams Mobile App itself will be supported provided the version is within three months of the current release.

Decision PointAre there any restrictions preventing users from installing the appropriate Microsoft Teams client on their devices?
Next StepsIf your organization restricts software installation, make sure that process is compatible with Microsoft Teams. Note: Admin rights are not required for PC client installation but are required for installation on a Mac.

Teams Web Browser View

Client update management

Clients are currently updated automatically by the Microsoft Teams service with no IT administrator intervention required. If an update is available, the client will automatically download the update and when the app has idled for a period of time, the update process will begin.

Client-side configurations

Currently, there are no supported options available to configure the client either through the tenant admin, PowerShell, Group Policy Objects or the registry.

Notification settings

Microsoft Teams Web Login

There are currently no options available for IT administrators to configure client-side notification settings. All notification options are set by the user. The figure below outlines the default client settings.

Sample PowerShell script - inbound firewall rule

This sample script, which needs to run on client computers in the context of an elevated administrator account, will create a new inbound firewall rule for each user folder found in c:users. When Teams finds this rule, it will prevent the Teams application from prompting users to create firewall rules when the users make their first call from Teams.

Using the Teams web version? Make it perform better by offloading it to the client.

The Teams full-fat installer has some issues for Citrix admins right now, mainly due to its aggressive (and bloated) way of installing into the user profile. You can use the Teams Machine-Wide Installer and even the VDI Installer to mitigate against some of this, but a lot of us (particularly those using Citrix Virtual Apps) are holding out for the server-level installer that integrates with Citrix policies. In the meantime, though, you can use Browser Content Redirection policies to optimize the performance of Teams within the web client.

This subject has already been excellently covered by fellow CTP Rody Kossen over on his blog so I’m just documenting the steps here for my own personal knowledge base, along with some bits of video which may help some of you out there to get it up and running.

The Teams web client is exactly what it says on the tin – a browser-based instance of Microsoft Teams. In my own limited experience, I don’t see an awful lot different from the full-fat application. You can make video and audio calls, and all the other functionality seems to be there, short of the close integration into the notification area. For many the web client has been a decent halfway-house solution until the application comes up to scratch for Citrix deployment.

Obviously optimizing heavy applications like Teams can be quite important. Especially in Citrix Virtual Apps environment, where a user monopolizing resources can have a heavy knock-on effect on other users on the same RDSH server. As well as looking at Teams, we will also demonstrate redirection of YouTube video so we can see the offloading in action.

I did all of my testing on fat Windows client devices which obviously are the best candidates for redirection in this way. However it is possible to achieve on thin clients, depending on the flavour of client you are using.

Setup

So firstly, make sure your VDA version is up-to-date. You can use the 7.15 LTSR (CU3 or higher) version to enable this or 7.16+ (for Internet Explorer only) or 1808+ (for Chrome and IE).

Also your client needs to be on the latest (or 1808+) version of the Workspace App.

The IE redirection relies on a Browser Helper Object (BHO). You will need to make sure that IE Enhanced Protected Mode is turned off and the policy for “Enable third-party browser extensions” is Enabled.

Once the IE BHO is loaded, you should be able to see it in the Manage Add-Ons list within Internet Explorer as below.

For Chrome, you need to also install the required redirection extension on the VDA. It is available at this link.

Microsoft Teams Web Sign In

Policy settings

Next you need to enable the required Citrix policy settings to enable this. Here’s a quick video to show you the settings you need:-

Summary of the settings for you cut-and-pasters out there 🙂 (Note there is a slight mistake in the video, I put https://youradfs.domain.com instead of https://youradfs.domain.com/* – the correct syntax is in the summary below!)

Browser content redirection – Allowed

Browser content redirection ACL config –

  • https://www.youtube.com/*
  • https://youtube.com/*
  • others (e.g. https://vimeo.com/*)
  • https://teams.microsoft.com/*
  • https://login.microsoftonline.com/*teams*

Browser content redirection authentication sites

  • https://youradfs.domain.com/* (change to your own address as necessary)
  • https://login.microsoftonline.com/*teams*
  • https://teams.microsoft.com/*

Redirection in action (streaming video)

Now, we will do a quick demo to show you the actual offloading in action.

When you run the redirection through Chrome, you will see a number of HdxBrowserCef.exe processes active on the client machine as the redirection is passed back to the client device.

When you run the redirection through Internet Explorer, you will see a single HdxBrowser.exe process active on the client machine.

I have a quick video here showing a streaming video being played on a VDA, both with and without the content redirection (in this instance, I had enabled for Chrome only – I disabled IE redirection by disabling third-party browser extensions via GPO)

Finalizing Teams web client redirection

Now, the final bit is for us to test the Teams web client redirection. Teams (as pointed out by Aaron Parker) is built on Chromium, but it seems to have some reliance on some IE components in this configuration (even if you run the web client in a different browser, the IE BHO still needs to be allowed to run), so we need to make sure the GPO controlling it is correctly configured in order for the redirection to work.

Once we’ve done that, we can verify if Teams optimization is working in Chrome and IE by doing a quick test (video):-

…and as we can see, it seems to be working as required (Internet Explorer being a non-supported browser for Teams meetings notwithstanding).

Security issues

Now, there are two possible configurations you can run this form of redirection in. There is client-side fetch, client-side render and server-side fetch, client-side render. (You can consider server-side fetch, server-side render a third config, but this is essentially BCR turned off) The details are covered much more in-depth on Rody’s blog posts, however, if the client-side fetch, client-render is used, the client fetches and downloads the content as well as rendering it. In a server-side fetch, client-render situation, the VDA fetches and downloads the content and then passes it to the client for rendering.

Obviously the client-side fetch would give a performance benefit, but this means that potentially the internal proxy and other web security features will be being bypassed. This is not an ideal situation from a security standpoint so many enterprises may wish to use the “server-side fetch, client render” configuration. There is a small impact on performance, but not anything hugely noticeable in my testing. To enable the server-side fetch, configure the Browser Content Redirection Proxy Configuration policy with the path to your proxy server, as below.

Browser content redirection in general needs to be properly assessed and tested from a security standpoint. You are moving traffic (and potentially data) back to an endpoint that may or may not meet security standards for your environment. Obtaining proper security approval and ensuring it meets your regulatory standards is a part of this process that shouldn’t be ignored.

More resources

Some extra reading around this area (including Rody’s excellent posts)

Summary

So that’s how we can configure Teams optimization as a stopgap until the Microsoft and Citrix products come together more dynamically to enable it. Also, as I showed, we can offload video streaming sites (and anything else you may find that gives you performance issues), provided we are not introducing a security vulnerability in our estates. Happy redirection!