Microsoft Teams Cancels Interpreter Usage Dashboard, Leaving Admins Without Adoption Reporting

Interpreter itself is not going anywhere. Only the reporting dashboard was dropped.

What was cancelled​

The item is roadmap ID 565217, titled "Microsoft Teams: Tenant-level dashboard for Interpreter." The description, which was written as though the feature had already shipped, promised that admins now have a dedicated dashboard in the Teams Admin Center to view Interpreter usage across their organization, and can track adoption and usage trends in one place to better understand how Interpreter is being used.

At the time of cancellation, the entry still showed these planned details:

Some of those values look odd. Android and iOS are mobile clients, yet the feature was an admin-center dashboard. The roadmap never explained that, and I wouldn't read anything into it. Roadmap platform tags are often rough.

The roadmap item's history​

The cancellation is easier to read once you see how the entry changed over the summer.

• June 2026: M365 Admin, a site that tracks roadmap changes, recorded that the item was created 2026-06-09 23:15:32Z. At that point it listed a release date of July CY2026 and only iOS as the platform.
• The first description went further. It promised admins could "Monitor adoption, track usage trends, and understand costs—all in one place." The words "understand costs" were later removed. The final wording mentions only adoption and usage trends.
• Mid-summer: Merill Prabhu's message center tracker showed the item as "In development" with a GA date of November CY2026. Another tracker reported it was modified on June 16, 2026, and listed for General Availability in November 2026.
• October 2026: The entry now reads Cancelled.

So the feature went from a July target to November in about a week, quietly lost its cost-tracking promise, and was then cancelled before its new date. Microsoft gave no reason, and I won't guess at one. Still, dropping "understand costs" is worth noticing. Interpreter has a monthly usage allowance, and a dashboard showing spend against that allowance is exactly what finance teams would have wanted.

One caution: a few third-party summaries described metrics and impacts the roadmap never stated. Microsoft never said what the dashboard would show, such as per-user detail, retention periods, export options or charts. Treat any claims like that as speculation.

Bottom line: the only official promise was an organization-wide view of Interpreter adoption and usage trends. That promise is gone, and Microsoft hasn't named a replacement.

Why admins wanted it: Interpreter has a usage allowance​

Interpreter isn't a free, unlimited extra. Microsoft's admin documentation on Learn says it is part of the Microsoft Copilot license... more precisely, it states that Interpreter comes with a Microsoft Copilot license, which includes 20 hours of interpretation per user per month, and that access beyond those hours depends on available capacity. Users also need an eligible Microsoft 365 base license and an eligible Teams license. Teams Rooms devices use a Teams Rooms Pro license in place of the Copilot license, with the same 20 hours a month. M365 Admin's coverage of the Rooms rollout put it as 20 hours of interpretation included per room account per month with a Teams Rooms Pro license.

With an allowance like that, a usage dashboard would have answered some obvious questions:

• Which departments actually use Interpreter?
• Is anyone close to the 20-hour limit?
• Is the Copilot spend paying off in multilingual meetings?

Without the dashboard, there's no dedicated Microsoft tool for any of this. Microsoft's general Teams usage reports in the Microsoft 365 admin center show usage trends, meetings, calls, and messaging data, but nothing in the available documentation says they break out Interpreter usage. Don't assume they do.

The controls you still have (all in PowerShell)​

Here's what Interpreter administration looks like today. Microsoft's Learn page says you must use PowerShell to manage Interpreter for your entire organization. There are two parameters, -AIInterpreter and -VoiceSimulationInInterpreter, applied through CsTeamsMeetingPolicy for meetings and CsTeamsCallingPolicy for one-to-one Teams VoIP calls.

Turn Interpreter on or off in meetings (enabled by default):

Set-CsTeamsMeetingPolicy -Identity <policy name> -AIInterpreter Disabled
Set-CsTeamsMeetingPolicy -Identity <policy name> -AIInterpreter Enabled

Turn Interpreter on or off in one-to-one Teams VoIP calls (also enabled by default):

Set-CsTeamsCallingPolicy -Identity <policy name> -AIInterpreter Disabled
Set-CsTeamsCallingPolicy -Identity <policy name> -AIInterpreter Enabled

Set the default voice for interpreted speech:

Set-CsTeamsMeetingPolicy -Identity <policy name> -VoiceSimulationInInterpreter Enabled
Set-CsTeamsMeetingPolicy -Identity <policy name> -VoiceSimulationInInterpreter Disabled

• Enabled (the default): users' translated speech plays in a simulated version of their own voice.
• Disabled: users start with an automated voice, and Ava is preselected.

Microsoft's documentation strongly recommends leaving voice simulation enabled for the best listening experience. It also states that voice samples and biometric data are never stored.

To be clear, these are on/off switches and defaults. They don't produce usage figures, and changing a policy won't tell you who uses the feature.

Where Interpreter works and where it doesn't​

According to Microsoft's Learn documentation (last updated September 22, 2026), Interpreter is supported in:

• Teams desktop on Windows and Mac
• Teams mobile on iOS and Android
• Teams web in Chrome, Edge, Safari and Firefox
• Teams Rooms on Windows
• Scheduled meetings and channel meetings
• VDI
• One-to-one Teams-to-Teams VoIP calls

The same page lists these as not supported:

• One-to-one PSTN calls
• Teams events
• Teams Rooms on Android
• Personal peripherals used with Teams Rooms
• Teams free

The Microsoft Support page for end users also excludes ad-hoc meetings, town halls and webinars. It adds that recordings capture only the original audio, not the interpretation.

There is one inconsistency to know about. Message center post MC1446807 announced that Microsoft Teams Rooms on Android will support real-time Interpreter agent for up to nine languages, and said it would be available late August 2026. Yet the September Learn page still lists Rooms on Android as unsupported. Test on your own Android Rooms devices before telling users it works.

The language lists also differ. The admin page lists nine languages: Mandarin Chinese, English, French, German, Italian, Japanese, Korean, Portuguese and Spanish. The end-user Support page adds Taiwanese.

What admins should do now​

1. Update your planning. If your rollout plans or Copilot reviews counted on a November usage dashboard, remove it.
2. Check your policies. Interpreter is enabled by default at the tenant level. Run Get-CsTeamsMeetingPolicy and Get-CsTeamsCallingPolicy and confirm the settings are what you intend, especially in regulated environments where voice simulation needs sign-off.
3. Plan around the gap. Until Microsoft offers a reporting option, any picture of adoption will come from user feedback and pilot programs, not from an official dashboard. That isn't ideal, but it's the honest situation.
4. Keep an eye on the roadmap. "Not at this time" leaves room for the feature to come back, possibly in another form. A cancelled entry is not a promise either way.

The bigger picture​

Microsoft is shipping AI agents into Teams quickly, and admin reporting for them is lagging behind. Here, Microsoft can turn Interpreter on by default for every licensed user, but admins have no official way to see how much it's used. Microsoft's own Inside Track blog says administrators have the ability to manage and configure Interpreter settings. That's true, but managing a feature isn't the same as being able to measure it.

The 20-hour monthly allowance is a reasonable perk. Without usage data, though, admins have no clear way to tell whether anyone is getting near it.