Manage the Walkie Talkie app in Microsoft Teams

Overview of Walkie Talkie

The Walkie Talkie app in Microsoft Teams provides a push-to-talk (PTT) experience that enables clear, instant, and secure voice communications – turning Android and iOS devices into a walkie talkie. Your users connect with their team through the same underlying Teams channels that they're already members of.

Team members can listen and talk to other team members who are connected through Walkie Talkie on the same channel. Users continue to receive transmissions until they tap Stop listening. Walkie Talkie supports communicating in standard and private channels in Teams. Shared channels aren't supported.

With Walkie Talkie, users can communicate through a familiar PTT experience without needing to carry bulky radios. And because Walkie Talkie works over Wi-Fi or cellular data, your users can stay connected to and instantly communicate with their team from anywhere they have an internet connection.

To learn more about the end-user experience, see Get started with Teams Walkie Talkie, Communicate with your team with Walkie Talkie, and Set up and use a wired headset with Walkie Talkie.


Walkie Talkie currently is not available in China.

License requirements

Walkie Talkie is included in all paid licenses of Teams in Microsoft 365 and Office 365 subscriptions. For more information about getting Teams, check out How do I get Microsoft Teams?

Prepare your network

Walkie Talkie requires connectivity to the internet. Use the following guidance to set up your organization's network for Walkie Talkie:

Deploy Walkie Talkie

You deploy and manage Walkie Talkie from the Teams admin center. Walkie Talkie is supported on Android devices with Google Mobile Services (GMS) and iOS devices.


Deployment is a three-step process. You'll need to complete all three steps for your users to have access to Walkie Talkie.

Step 1: Make sure Walkie Talkie is enabled in your organization

You control whether the app is available at the organization level on the Manage apps page in the Microsoft Teams admin center. To confirm that the app is enabled in your organization:

  1. In the left navigation of the Teams admin center, go to Teams apps > Manage apps.
  2. In the list of apps, search for the Walkie Talkie app, select it, and then make sure the Status toggle is set to Allowed.

Step 2: Create and assign an app permission policy

Control which users in your organization can use Walkie Talkie by assigning app permission policies in the Teams admin center. To learn more, see Use app permission policies to control user access to apps.

Make sure Walkie Talkie is an allowed app in the app permission policy, and you assign the policy to all users who need Walkie Talkie.

Step 3: Pin Walkie Talkie for your users

Pin Walkie Talkie to Teams for easy access. This step depends on which license your users have.

E license: Use an app setup policy to pin Walkie Talkie to Teams

App setup policies let you customize Teams to pin apps that are most important for your users in your users.

To pin the Walkie Talkie app for your users, you can edit the global (Org-wide default) policy or create and assign a custom policy in app setup policy. To learn more, see Use app setup policies to pin and auto-install apps for users.

Screenshot showing adding Walkie Talkie to the pinned apps list in the Add pinned apps pane.

F license: Use the Tailored frontline app experience to pin Walkie Talkie and other apps to Teams

The tailored frontline app experience in Teams pins the most relevant apps in Teams for users who have an F license. Pinned apps include Walkie Talkie, Shifts, Tasks, and Approvals. By default, this feature is on, giving your frontline workers an out-of-the-box experience tailored to their needs.

The apps are pinned to the app bar at the bottom of Teams mobile clients where users can quickly and easily access them.

To learn more, including how the experience works with app policies that you set, see Tailor Teams apps for your frontline workers.

Network considerations

The following network conditions are required for an optimal experience.

Metric Required
Latency (RTT) < 300 ms
Jitter < 30 ms
Packet Loss < 1%

As noted, the quality of real-time media over an IP network is greatly affected by the quality of the network connectivity, but especially by the amount of:

  • Latency - The time it takes to get an IP packet from point A to point B on the network. This network propagation delay is tied to the physical distance between the two points and the speed of light, including more overhead taken by the various routers in between. Latency is measured as Round-trip Time (RTT).
  • Inter-arrival jitter - The average change in delay between successive packets.
  • Packet loss - Packet loss is often defined as a percentage of packets that are lost in a given window of time. Packet loss directly affects audio quality—from small, individual lost packets that have almost no impact, to back-to-back burst losses that cause complete audio cut-out.

Expected data usage from Walkie Talkie is around 20 Kb/s when sending or receiving audio. When idle, expected data usage from Walkie Talkie is negligible.

Also, keep in mind the following:

  • Walkie Talkie should work well in low bandwidth situations, or situations where the user's phone is connected and working. Walkie Talkie doesn't work when there's no connectivity at all.
  • If users are using mobile data to communicate in Teams, Walkie Talkie will use the same method.

Devices and accessories

Heads-up and hands-free communication is key for real-time collaboration. Frontline workers often need to communicate with each other when their phones are locked. This experience is possible through the following devices and headsets:

Generic wired headsets

Walkie Talkie works with any generic wired (3.5 mm and USB-C) headset on Android. As long as the generic headset has a play/pause button or an answer/end call button, frontline workers can tap the button to start and end transmissions on Walkie Talkie in Toggle-to-Talk mode.

Specialized headsets and devices that have a dedicated PTT button

Walkie Talkie is integrated with a range of specialized headsets and devices that have a dedicated PTT button. Press and hold the PTT button on the headset or device to instantly send transmissions. Here's a list of these headsets and devices from our partners.


Manufacturer Model Wired or wireless Platform
BlueParrott Wireless Android, iOS
Jabra Wireless Android, iOS
Klein Electronics
  • 3.5 mm
  • USB-C
Wired Android

Rugged Android phones

Manufacturer Model Setup
Crosscall Core-X4, Core-M5, Action-X5, Core-X5, Core-T5 Manual setup: With Teams installed, go to Settings > Buttons. On the Dedicated button (1 or 2), select Long press, and then choose PTT App. Select the blue wheel next to Custom, and select Teams.
Kyocera DuraForce Ultra 5G, DuraSport 5G Manual setup: With Teams installed, go to Settings > Programmable keys. Choose PTT key or Press and hold (depending on the device), and select Teams.
Honeywell CT30 XP, CT30 XP HC, EDA51, EDA52, EDA52 HC Manual setup: With Teams installed, the dedicated PTT button works with Walkie Talkie by default.
Important: Customers using Honeywell CT30 should upgrade to Android version: A11 HON4290 MR14.
Samsung Galaxy XCover7 (not available in North America), Galaxy XCover6 Pro, Galaxy Tab Active5
  • Manual setup: With Teams installed, go to Settings > Advanced Features > XCover/Active key. Turn on Control XCover key with app, and select Teams.
  • MDM setup
Sonim XP8 Manual setup: With Teams installed, go to Settings > Programmable Keys. Choose Select PTT Key app, and select Teams.
Zebra TC5x, TC15 (not available in North America), TC5301 , TC7x, TC2x, EC5x, MC3300, MC9300, ET40 Manual setup: With Teams installed, the dedicated PTT button (LEFT_TRIGGER_2) works with Walkie Talkie by default.


These headsets and devices are not Teams certified. They have been validated to work with Walkie Talkie in Teams.

Considerations when using Bluetooth devices


If your users are using Bluetooth accessories, make sure that your mobile device management (MDM) solution doesn't block Bluetooth devices.

On devices running Android OS version 12 or later, Bluetooth permissions are required and location permissions to connect using the BLE stack are no longer required. If "nearby permissions" aren't granted at the Teams level, a user receives a prompt for Bluetooth permissions. This prompt is displayed, whether or not a Bluetooth accessory, such as a headset, is connected to their device. If a Bluetooth accessory is connected, tapping Allow connects Walkie Talkie to the Bluetooth accessory.

Get insight into Walkie Talkie usage and performance

The Walkie Talkie usage and performance report in the Teams admin center gives you and overview of Walkie Talkie activity and performance in your organization. The report provides information such as the number of PTT transmissions made and received, channel activity, transmission duration, and device and participant details.

Data residency

Walkie Talkie customer data for tenants in the European Union Data Boundary (EUDB) and in the United Kingdom is stored in data centers located in the EU. To be considered a tenant in the EUDB, the tenant must have a default geography in a EUDB country/region or select a country/region in EUDB country/region as their residence during sign-up.

All other tenants have their Walkie Talkie customer data stored in data centers located in the United States. Tenants aren't provided with a choice for the specific deployment region for data storage.

How can I determine customer data location?

See Microsoft Entra ID and data residency.

Give feedback or report an issue

To send feedback or report an issue, go to Settings > Help & feedback, and then choose Send feedback. Enter your feedback or details about the issue you're experiencing. Indicate at the beginning of your feedback report that you're sending feedback about Walkie Talkie so we can easily identify Walkie Talkie issues.

Users in your organization can attach logs while sharing feedback to Microsoft, if you enable the policy to set whether users can send feedback about Teams to Microsoft.