Get clients for Microsoft Teams

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

Note

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. We recommend that you use one of the Teams apps described below in this article after November 29.

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 currently not part of Office 365 ProPlus. Teams is available for both Windows (7+), both 32-bit and 64-bit versions, and macOS (10.10+). 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.

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).

IT admins can choose their preferred method to distribute the installation files to computers in their organization, such as System Center 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%\Microsoft\Teams

  • %LocalAppData%\Microsoft\TeamsMeetingsAddin

  • %AppData%\Microsoft\Teams

  • %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.

Screenshot of a Windows Security Alert dialog.

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 Block action for both TCP and UDP protocols.

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.

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.

Browser Notes
Internet Explorer 11 Calling and Meetings aren't supported. Users who try to join a meeting on Internet Explorer 11 will be directed to download the Teams desktop client.
Microsoft Edge Calling and Meetings supported on Edge RS2 or later
Chrome, the latest version plus two previous versions Meetings supported on Chrome 59 or later
Support for Calling is coming soon
Firefox, the latest version plus two previous versions Calling and Meetings aren't supported. Users who try to join a meeting on Firefox will be directed to download the Teams desktop client. 

Note

Safari isn't currently supported. Check the Teams Roadmap for news about new features in Teams. Users who try to open Teams on Safari will be directed to download the Teams desktop client.

Note

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

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 see here for more information.

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

  • Android: 4.4 or later

  • iOS: 10.0 or later

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, and are not available to be distributed through MDM (mobile device management) solutions or side-loaded.

Decision Point icon. Decision Point Are there any restrictions preventing users from installing the appropriate Microsoft Teams client on their devices?
Next Steps icon. Next Steps If 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.

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 kick off.

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

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.

Screenshot of Notifications settings.

Sample PowerShell Script

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.

$users = Get-Childitem c:\users
foreach ($user in $users) 
{
    $Path = "c:\users\" + $user.Name + "\appdata\local\Microsoft\Teams\Current\Teams.exe"
    if (Test-Path $Path) 
	{
	        $name = "teams.exe " + $user.Name
	        if (!(Get-NetFirewallRule -DisplayName $name))
		{
	            New-NetFirewallRule -DisplayName “teams.exe” -Direction Inbound -Profile Domain -Program $Path -Action Allow
		}
	}
}
<#
        .ABOUT THIS SCRIPT
        (c) Microsoft Corporation 2018. All rights reserved. Script provided as-is without any warranty of any kind. Use it freely at your own risks.

        Must be run with elevated permissions. Can be run as a GPO Computer Startup script, or as a Scheduled Task with elevated permissions. 

        The script will create a new inbound firewall rule for each user folder found in c:\users. 

        Requires PowerShell 3.0
        
#>