Microsoft Teams topics

Teams External Access vs. B2B Direct Connect vs. B2B Collab

underQualifried — Fri, 16 Oct 2026 16:15:03 GMT

I've received conflicting info regarding whether B2B Direct Connect and Teams External Access are the same thing.

Last time I looked into this, they both seemed to rely on the 'Default External Identities' controls from Entra - they were two faces of the same coin.

Now it's not so clear. Can someone clarify?

Stopping notifications for specific chats

lalanc01 — Thu, 15 Oct 2026 12:39:42 GMT

When will you bring back the stop notifications for a specific post that was removed in the new Teams?

This generate a lot of noise/notifications when there's a lot of replied in the post.

The New Unified Events Experience in Microsoft Teams: Webinars & Town Halls in One Place

GiulianoDeLuca — Thu, 15 Oct 2026 15:03:15 GMT

Hi everyone 👋

Microsoft has redesigned the Meet app in Teams into a new unified Events app. Webinars, town halls and custom events now share a single workflow for creating, discovering and managing events.

I recorded a step-by-step video walkthrough, and I'd like to share the key points here for anyone planning the transition in their organization.

🔍 What's new • Discover tab: attendees, presenters and organizers can find upcoming events, register, and watch past recordings without relying only on calendar invites

• Manage tab: a central hub to create, edit and track events across every stage

• Templates: schedule webinars, town halls and custom events faster • Create from scratch: custom events follow Town hall policies for broadcast-style events and Webinar policies for collaborative ones

• Event landing pages with integrated Q&A and Polls

• Scheduling from shared and delegate mailboxes

⚙️ Admin & licensing notes

• Existing Webinar and Town hall policies continue to apply, and no admin action is required for the rollout

• Since April 1, 2026, several event features that used to require Teams Premium are included in Teams Enterprise

• Events with up to 3,000 interactive attendees are supported; larger events (up to 100,000) require an attendee capacity pack

• Teams Live Events was retired on June 30, 2026, so town halls are now the way to run large broadcast-style events

💬 I'd love to hear from you: • Have you already moved from Live Events to town halls? • Which do you use more in your organization, webinars or town halls? • Any tips or gotchas from your rollout?

Thanks for reading, and feel free to share your experience in the replies!

Giuliano De Luca Solutions Architect | Microsoft 365

JSON Formatting

DuncanV — Thu, 15 Oct 2026 13:52:57 GMT

I created a JSON that counts the days after a certain start date "A" and stops after a date "B" if there is no date in B it keeps counting. Further the days count<90 turn green, 90-120, turn yellow, >120 turn red. The problem I encounter is that it works fine in 0. All items, but no longer in a specific view, although the record gives the correct number (B-A) the visual view keeps counting from A.

Did anyone had something similar?

The JSON code checked out correct and it was mentioned that the error is to be found in SharePoint backend configuration settings, rather than frontend browser code or indexing times.

What could/should be changed in the backend configuration to solve this?

Teams Chat messages disappears

Johol62 — Thu, 15 Oct 2026 12:38:22 GMT

Problem with Teams Windows client.
When you hover the mouse over the chat column, all the contacts disappear.
If you click on the Chat icon to the left or press CRTL+2 you get the error message "We ran into a problem getting your chats and channels"
I have tried to do both a repair and reset from the advanced app settings.
Also tried to remove Teams and do a new installation.
Finally I have manually delete the cache files from:
%userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams
What's next to get Teams working again?

How are organisations monitoring attendance and participation during live Microsoft Teams meetings?

NikH9922 — Wed, 14 Oct 2026 12:32:15 GMT

Hi everyone,

I’m interested in how organisations are monitoring and verifying attendance and participation during live Microsoft Teams meetings, particularly where accurate records are important.

Teams attendance reports provide useful information about when participants join and leave, but they don’t necessarily provide a complete picture of what happens throughout a session.

For example, how are organisations managing:

Participants switching their cameras off for extended periods
People stepping away while remaining connected
Monitoring attendance throughout longer meetings, training sessions or online events
Verifying that participants remain present
Maintaining reliable attendance records for compliance, accreditation or reporting purposes

Are you relying on Teams’ built-in attendance reports, monitoring participants manually, or using additional tools?

I’m particularly interested in how organisations are addressing these challenges without creating additional administrative work for those running the sessions.

Would be great to hear what approaches or solutions others have found effective.

Microsoft Teams transcription language settings

GerardChen — Wed, 14 Oct 2026 09:05:34 GMT

Hi!

With a Microsoft 365 Business Premium license and a Copilot license, I can use transcription during a Teams meeting by setting the spoken language to Auto Detect. However, the transcription is sometimes inaccurate. Is there a way to limit the language detection scope? For example, is it possible that I select only English and Chinese, and Auto Detect is restricted to those two languages instead of also attempting to detect languages such as Spanish or French ?

Architectural Limitation: Move LBR from Gateway to Voice Routes for Shared Trunks

JrMcClean — Tue, 13 Oct 2026 20:11:34 GMT

The Problem:

Currently, Location-Based Routing (LBR) in Microsoft Teams is hard-locked to the root OnlinePSTNGateway object (e.g., via -GatewaySiteLbrEnabled). This creates two major administrative roadblocks:

Derived Trunk Limitations: For organizations utilizing multi-tenant partner architectures and derived trunking models (such as AudioCodes Live Pro/Express), the underlying global gateway configuration is owned and managed by the provider. Because administrators lack root modification rights over these shared gateway objects, they cannot enable or configure LBR. View Teams Admin Center Restricted SBC Gateway Settings Managing gateways via the Teams Admin Center (Voice > Direct Routing > SBCs) results in restricted or failing LBR configurations.

Rigid Global Enforcement: Forcing LBR as a strict hardware-level switch creates deployment roadblocks, such as entirely blocking unmapped or remote workers. This is overly restrictive in regions like North America, where strict anti-toll-bypass compliance is not a legal mandate (unlike regions like India).

The Proposed Solution:

Decouple LBR from the Gateway Object: Shift LBR evaluation away from the root hardware gateway switch toggle and allow it to occur at the Voice Route, PSTN Usage, or Calling Policy layer.

Support Derived & Shared Trunks: This decoupling will instantly make LBR compatible with multi-tenant SBC models, allowing enterprises to manage geographic routing via distinct voice routes (which are already peered with gateways), bypassing the need for root gateway property access.

Regional Flexibility & Compliant Enforcement: Enable regional flexibility so enterprises can bypass unnecessary toll-bypass blocks in regions where they aren't mandated (like North America) without breaking calls for "Unknown" network sites. Crucially, for heavily regulated regions like India, system-enforced policies should automatically lock LBR on to strictly maintain local country regulations without relying on manual overrides.

Business Impact:

This enhancement will unlock advanced routing flexibility for thousands of enterprises utilizing modern cloud-hosted and derived trunking architectures. It bridges the gap between legacy PBX design constraints and modern multi-tenant cloud voice management, significantly reducing deployment friction for global organizations.

Meeting setup in teams Channel is not allowing me to update the Agenda and send updates

JOELMC — Fri, 09 Oct 2026 20:55:37 GMT

I am interested to understand why when I have setup a meeting from A channel I am not able to change the invitation to all the team members. When I go into teams Calendar ,. I update the agenda description, the send updates at the top right view shows up when I do the changes , however , When I click it , the changes don't take effect.

Management of unsupported WFH Teams-certified desk phones

Overclocker — Fri, 09 Oct 2026 20:21:10 GMT

Hello, I'm looking for best practice or suggestions on management of unsupported WFH Teams-certified desk phones for company with Microsoft enterprise E3 and E5 licensed users. We're a Microsoft shop with Teams for messaging, but not for desk phones. So far, we've had only one employee buy their own Yealink Teams-certified desk phone for WFH use. It showed up as an incident in our MTR Pro Management portal for Account management Sign in (Teams) and we found out it was for a personal Yealink Teams-certified desk phone they setup and logged into at home.

I asked multiple IT groups at the company I work for, and this is the answer they gave me "This device was allowed to enroll into Intune/Entra/MTR Pro portal because the user is a user in our Microsoft Tenant. The Android AOSP enrollment does not have any method of limiting what devices are allowed to enroll or of identifying that it is either personal or corporate. I was unable to find any Microsoft documentation that would have prevented this from occurring. If another user finds a used Teams Room device at a garage sale and thinks it would be cool to have one at home, the same thing will happen again."

What are our options to manage unsupported Teams-certified desk phones in our environment?

TIA

Shared Channels: @Channel mentions fail to trigger activity notifications for team-shared members

HishNa — Thu, 08 Oct 2026 11:51:47 GMT

Hello everyone,

I am facing a persistent issue regarding notification behavior in Microsoft Teams Shared Channels that I hope someone can clarify or help with.

Scenario:

We have a Shared Channel that is shared with multiple teams (e.g., 17 teams in total).

Note: I know that this way of communicating is not the recommended way, but we are not allowed to use any Viva products etc.

Users accessing the channel are members of those shared-in teams, but they are not listed as direct individual members in the Shared Channel's own member list.

Users have their channel notification settings correctly configured to receive notifications (e.g., "All new posts" or standard banner/activity settings).

The Problem:

When someone uses a channel mention (e.g., @ChannelName) in this shared channel, the users who have access via the team-sharing mechanism do not receive any activity feed notifications.

The workaround/oddity:

They only receive the activity notification if we explicitly add each user as a direct individual member to the Shared Channel.

The dilemma:

Since the channel is shared with 17 teams, adding hundreds of users manually or via scripts as direct members creates massive redundancy and clutters the UI (users see the team and the channel redundantly).

Inconsistency:

We noticed that in older shared channels created some time ago, channel mentions worked across team shares without needing direct individual memberships. It seems newer shared channels behave differently and strictly require direct membership to trigger activity feed notifications for @Channel mentions.

Questions:

Is this a known design limitation or a recent backend change in Microsoft Teams for newer Shared Channels regarding how @Channel mentions resolve indirect team members?

How are organizations supposed to utilize @Channel mentions effectively in large-scale collaborations involving multiple shared teams without bloating the direct membership list?

Any insights or workarounds would be greatly appreciated.

Thank you!

Microsoft Places bug: Room images are too big, hiding info. Need a compact/resize option

RomJG — Wed, 07 Oct 2026 15:02:42 GMT

Hi everyone,

We are currently deploying Microsoft Places and configuring our Resource Mailboxes. We are facing a major UI/UX issue regarding the Room Cards (Space Profiles).

No matter what image size, resolution, or aspect ratio we upload for a room (via Entra ID / Exchange mailbox photo), the Microsoft Places interface automatically scales and stretches the image to fill the top banner.

The image container is so large that it takes up almost the entire height of the card. As a result, critical information such as room capacity, available features/equipment, and the booking button are pushed completely out of view. Users are forced to scroll down every single time just to see basic details.

This creates a poor user experience. While removing the room picture entirely provides a more compact layout, we would still like to use visual cues without sacrificing readability.

Feature Requests for the Product Team:

Allow administrators to disable or shrink the room image banner directly within the Places settings.

Introduce a compact layout option for Room Cards where text and action buttons (like "Book") are prioritized at first glance.

Fix the auto-scaling behavior so it doesn't force a massive zoom on standard 1:1 or 16:9 images.

Is anyone else experiencing this, or did you find a clean workaround to force a more compact view?

Thanks!

Teams PowerShell no longer works on MacOS - Windows only dependency after 7.9.0

merill — Sat, 03 Oct 2026 00:16:27 GMT

Since MicrosoftTeams 7.9.0, Connect-MicrosoftTeams with the default interactive sign-in fails on macOS before any sign-in prompt appears. It throws System.DllNotFoundException: Unable to load shared library 'kernel32.dll'. Version 7.8.0 connects without error on the same machine. The current release, 8.0.0, has the same problem.

Environment

macOS 27.0.1 on Apple silicon (Arm64)
PowerShell 7.6.2 on .NET 10.0.8
MicrosoftTeams 7.9.0 and 8.0.0 fail; 7.8.0 works

Steps to reproduce

Install-Module MicrosoftTeams -RequiredVersion 8.0.0 -Scope CurrentUser
Import-Module MicrosoftTeams -RequiredVersion 8.0.0
Connect-MicrosoftTeams

Expected result

A browser sign-in opens and the session connects, as it does with 7.8.0.

Actual result

No sign-in prompt appears. The command fails straight away:

System.DllNotFoundException: Unable to load shared library 'kernel32.dll' or one of its dependencies.
   at Microsoft.TeamsCmdlets.Powershell.Connect.TeamsPowerShellSession.GetConsoleWindow()
   at Microsoft.TeamsCmdlets.Powershell.Connect.TeamsPowerShellSession.GetConsoleWindow()
   at Microsoft.TeamsCmdlets.Powershell.Connect.TeamsPowerShellSession.GetConsoleOrTerminalWindow()
   at Microsoft.Identity.Client.PublicClientApplicationBuilder.<>c__DisplayClass12_0.<WithParentActivityOrWindow>b__0()
   at Microsoft.Identity.Client.AcquireTokenInteractiveParameterBuilder.WithParentActivityOrWindowFunc(Func`1 parentActivityOrWindowFunc)
   at Microsoft.Identity.Client.PublicClientApplication.AcquireTokenInteractive(IEnumerable`1 scopes)
   at Microsoft.TeamsCmdlets.Powershell.Connect.TokenProvider.MsalTokenProvider.GetAccessTokenInteractive(ModuleConfiguration config, AzureAccount azAccount, IEnumerable`1 scopes)
   at Microsoft.TeamsCmdlets.Powershell.Connect.AuthenticationFactory.Authenticate(AzureAccount account, AzureEnvironment environment, String tenantId, SecureString password, AuthenticationFlow authFlow, String resource, IEnumerable`1 scopes, String clientAppId)
   at Microsoft.TeamsCmdlets.Powershell.Connect.RMProfileClient.AcquireAccessToken(AzureAccount account, AzureEnvironment environment, String tenantId, SecureString password, AuthenticationFlow authFlow)
   at Microsoft.TeamsCmdlets.Powershell.Connect.RMProfileClient.Login(AzureAccount account, AzureEnvironment environment, String tenantId, SecureString password, AuthenticationFlow authFlow)
   at Microsoft.TeamsCmdlets.Powershell.Connect.ConnectMicrosoftTeams.ProcessRecord()

The full exception message also lists every path .NET tried for kernel32.dll.dylib, libkernel32.dll and so on, all "no such file".

Cause

TeamsPowerShellSession.GetConsoleOrTerminalWindow() calls the Windows GetConsoleWindow function through [DllImport("kernel32.dll")]. The module passes it to MSAL as the parent-window callback (PublicClientApplicationBuilder.WithParentActivityOrWindow), and MSAL calls that callback inside AcquireTokenInteractive. macOS has no kernel32.dll, so the call throws before sign-in starts.

Comparing Microsoft.TeamsCmdlets.PowerShell.Connect.dll across versions:

7.8.0: only the Integrated Windows Authentication path, which runs only on Windows, sets this callback.
7.9.0 and 8.0.0: AzureSessionProvider also sets it when it builds the client application, and that client is used for interactive sign-in on every platform.

A fix would be to set the callback only on Windows, or have GetConsoleOrTerminalWindow() return IntPtr.Zero on other platforms. Linux has no kernel32.dll either, so I'd expect interactive sign-in to fail there too, but I haven't tested it.

Workarounds

Stay on 7.8.0:

Install-Module MicrosoftTeams -RequiredVersion 7.8.0 -Scope CurrentUser
Import-Module MicrosoftTeams -RequiredVersion 7.8.0

Use device code sign-in. Connect-MicrosoftTeams -UseDeviceAuthentication doesn't call GetConsoleWindow, and on 8.0.0 it gets to the device code prompt without this error.

I found this while testing Maester (maester.dev), which calls Connect-MicrosoftTeams from Connect-Maester -Service Teams and -Service All.

Teams Enables Easier File Sharing in Federated Chat

TonyRedmond — Fri, 02 Oct 2026 07:07:57 GMT

A change to Teams makes it easier for users to share files in federated chat. Sounds good, but Microsoft planned to overwrite existing tenant controls to make the feature work, and that’s wasn't so good. That issue is now resolved, but the real question is whether Microsoft 365 tenants want users to share files through federated chat. I’m not so sure and would control this facility tightly. Apart from anything else, you might need some more MDO licenses to protect against possible infection.

https://office365itpros.com/2026/10/02/easier-federated-chat/

Teams unexpectedly ends calls with Anker PowerConf S3 A3302 over USB

Mirko — Fri, 02 Oct 2026 06:41:33 GMT

ANKER POWERCONF Sthree

Unintended Teams call terminations

Diagnostic dossier - public version

Model Athree three zero two ; Public version: hostname, GUIDs and original archive names removed

Summary for support intake

Teams calls end spontaneously when PowerConf Sthree is used over USB with Sync device buttons enabled. The issue is reported on two units and multiple PCs, both laptops and desktops. The user is disconnected from the call; this is not merely a loss of audio.

The weblogs identify an Sthree HID call-control hangup: telephony off-hook state is inactive ; followed by onDidHook ; followed by leaveCallContext=hid_triggered. An independent USB trace shows a brief stop/restart of microphone streaming immediately before the zero report. A physical button press is not required to observe these states.

With synchronization OFF, we recorded the same stop/start and zero report during a call that continued. The issue is also reproduced without the Trust two four five three zero receiver. Two Bluetooth calls with synchronization saved as ON were stable, using a different control path.

Observed environment

Item ; Details

- Speakerphone ; Anker PowerConf Sthree Athree three zero two; USB VID two nine oneA / PID three three zero two

- Firmware ; two dot two dot eight reported by the user; not verified separately for both units

- Teams ; two six two four six dot one six zero four dot five one three three dot eight three eight

- Windows ; Microsoft components one zero dot zero dot two six one zero zero.x; detailed collection on a test PC

- USB conditions ; Sthree port and cable unchanged throughout. No active Sthree Bluetooth connection reported during USB tests.

- Receiver compared ; Trust two four five three zero, keyboard/mouse kit; not required to reproduce the issue

Responsibility remains unresolved: neither the requester of the initial microphone stop nor the responsible component among Anker firmware, the Windows audio/HID stack and Teams interpretation has been established. The termination chain is identified; the internal cause still requires investigation.

one. Comparison of tests

Italian local times, UTC+zero two hours zero zero minutes, on one October two zero two six. ON/OFF refers to button synchronization. IDs Eone-Enine reference the archives in the archive index below. These outcomes are not statistical estimates of reliability.

Test ; Configuration ; Outcome and evidence

- Eone ; one four hours five two minutes ; USB; ON ; Call ended: Sthree telephony off-hook state is inactive report, onDidHook, hid_triggered.

- Etwo ; one five hours one zero minutes ; USB; ON ; Reports transition from inactive to active about six zero ms apart; ETW shows microphone stop/start before zero. Weblog for the same session unavailable.

- Ethree ; one five hours three five minutes ; Outside Teams ; Three recording cycles: microphone start ; followed by telephony off-hook state is active; stop is followed by the inactive state. Teams not detected in one four snapshots.

- Efour ; one five hours four three minutes ; USB; OFF ; Stable call ~twomzero six. Stop/start and zero report at one five hours four four minutes zero two seconds; Teams logs disabled controls.

- Efive ; one six hours zero one minutes ; USB; ON; Trust removed ; Stable call ~twomfive zero. No intermediate stop/start. Manual termination verified.

- Esix ; one six hours one five minutes ; USB; ON; Trust reinserted ; First call stable ~fivemone six and ended manually. Second ended through HID after a brief stop/start.

- Eseven ; one six hours two six minutes ; USB; ON; Trust removed ; Issue reproduced. Five transient USB/HID cycles; final hangup directly confirmed in weblogs.

- Eeight ; one six hours three five minutes ; Bluetooth; OFF ; Stable call ~threemthree one. OFF saved before the call; manual termination verified.

- Enine ; one six hours four two minutes ; Bluetooth; ON saved ; Two stable calls reported. No HID hangup in the available window; second manual termination verified.

Additional user observations

A one zero-minute call did not end unexpectedly with synchronization OFF. In the problematic tests, the option was already enabled before starting the call. The user reports no Sthree button presses during the unexpected terminations.

Trust hypothesis: updated after the control test

The initial stable test without the dongle was a provisional lead. Subsequent reproduction without Trust rules it out as a necessary cause. There is insufficient evidence to attribute the terminations to radio interference from the receiver or to recommend replacing it.

two. Termination chain observed in Teams and USB

Eone - HID-triggered termination at one four hours five two minutes

Italian local time ; Relevant log line/event

- one four hours five two minutes four zero seconds one six zero milliseconds ; PowerConf Sthree, Standard Hook Protect USB: Telephony usage telephony off-hook state (three two), value zero; received hook event; invoking onDidHook.

- one four hours five two minutes four zero seconds one six one milliseconds ; onDidHook: leaves active call; startHangupScenario.

- one four hours five two minutes four zero seconds two two zero milliseconds ; telephony off-hook state is active and line busy tone state is active: state restored after about six zero ms.

- one four hours five two minutes four one seconds one six three milliseconds ; leaving call, leaveCallContext=hid_triggered.

- one four hours five two minutes four one seconds three six five milliseconds ; calling_call_disconnected, same hid_triggered context.

LocalUserInitiated is the software classification of the local termination and does not prove a human action. Standard Hook Protect USB is the name of the HID handler selected by Teams; it does not establish that a proprietary Anker driver is damaged.

Eseven - Reproduction without Trust at one six hours two eight minutes

Italian local time ; Event

- one six hours two eight minutes four zero seconds five five four milliseconds ; Teams: connected call state three, active call.

- one six hours two eight minutes four six seconds three nine four milliseconds ; Sthree USB microphone: interface three, alternate setting zero.

- one six hours two eight minutes four six seconds four zero zero milliseconds ; Teams: received hook event on StandardHookProtectUSB.

- one six hours two eight minutes four six seconds four zero five milliseconds ; Sthree Raw Input: zero two-zero zero-zero zero, telephony off-hook state is inactive.

- one six hours two eight minutes four six seconds four four four milliseconds ; USB: interface three alternate setting one; restart after five zero ms.

- one six hours two eight minutes four six seconds four six four milliseconds ; Sthree Raw Input: zero two-zero three-zero zero, telephony off-hook state is active.

- one six hours two eight minutes four seven seconds four one four milliseconds ; Teams: leaving call, hid_triggered, leaveCallState three.

- one six hours two eight minutes four seven seconds five six three milliseconds ; Teams: disconnected, leaveCallContext=hid_triggered.

The initial stop/start sequence precedes the hangup. Stops and zero reports after termination may instead be consequences of it. ETW and Raw Input observe different points in the stack: timestamp differences do not measure firmware latency alone.

three. Independent verification and controls

Report identification and decoding

The Sthree USB Raw Input path is HID / VID_two nine oneA & PID_three three zero two / MI_zero zero / Colzero two. Captured preparsed data was used with HidP_GetUsages from hid.dll, Input report and Telephony Usage Page zeroxzeroB. Decoding is based on the descriptor, not an assumption about a byte.

Report ; Parser result

- zero two-zero zero-zero zero ; No active telephony usages: telephony off-hook state (usage three two) is inactive, line busy tone state (usage one five one) is inactive.

- zero two-zero three-zero zero ; Usages three two and one five one active: telephony off-hook state is active, line busy tone state is active.

USB interface three is AudioStreaming: class zeroxzero one, subclass zeroxzero two. Alt zero has zero endpoints; alt one enables IN endpoint zeroxeight one, the microphone stream. Stopping/starting the stream is not equivalent to physically disconnecting the port.

Ethree - Three recordings outside Teams

USB microphone operation ; Subsequent report ; Approx. interval

- one five hours three six minutes three zero seconds one eight eight milliseconds ; start ; one five hours three six minutes three zero seconds two three seven milliseconds ; telephony off-hook state is active ; four nine ms

- one five hours three six minutes three six seconds eight one four milliseconds ; stop ; one five hours three six minutes three six seconds eight two zero milliseconds ; telephony off-hook state is inactive ; six ms

- one five hours three six minutes four one seconds zero zero eight milliseconds ; start ; one five hours three six minutes four one seconds zero three three milliseconds ; telephony off-hook state is active ; two five ms

- one five hours three six minutes four nine seconds two three four milliseconds ; stop ; one five hours three six minutes four nine seconds two four one milliseconds ; telephony off-hook state is inactive ; seven ms

- one five hours three six minutes five one seconds eight six two milliseconds ; start ; one five hours three six minutes five one seconds eight eight seven milliseconds ; telephony off-hook state is active ; two five ms

- one five hours three six minutes five seven seconds nine three nine milliseconds ; stop ; one five hours three six minutes five seven seconds nine five zero milliseconds ; telephony off-hook state is inactive ; one one ms

Teams is not detected in the one four process snapshots for Ethree; sampling is not a continuous trace of all process starts. This comparison shows that Teams is not required to observe the zero state when the microphone stops, but does not distinguish firmware from the Windows stack.

Efour - Same phenomenon, stable call with OFF

During the call: alt zero at one five hours four four minutes zero two seconds zero two seven milliseconds, Raw telephony off-hook state is inactive at zero four zero milliseconds within the same second, alt one at zero eight eight milliseconds within the same second, Raw telephony off-hook state is active at one one three milliseconds within the same second. Teams logs audio device sync is disabled and controls not enabled. The call continues until the manual click at one five hours four five minutes five one seconds zero three zero milliseconds. OFF does not necessarily eliminate the reports: it prevents their use as call controls.

four. Bluetooth and alternative hypotheses

Enine - Two calls with synchronization saved as ON

At one six hours four two minutes three four seconds five eight one milliseconds, the client logs “Toggling sync device buttons enabled to true”; at five eight four milliseconds within the same second, “audioDeviceSyncEnabled: true”. No synchronization-disabled or HID-hangup log lines appear within the two-call window available in the weblogs.

First call: connected at one six hours four two minutes five three seconds zero three eight milliseconds. Manual termination is reported by the user; the corresponding explicit hangup line is absent from the examined user-log segment. Second call: connected at one six hours four five minutes zero five seconds three zero three milliseconds, hangup click at one six hours four six minutes five eight seconds five three three milliseconds/five three five milliseconds within the same second, disconnected at seven zero five milliseconds within the same second with multi-window_hangup-button_click.

Selected Bluetooth endpoints: microphone [endpoint ID omitted] and speaker [endpoint ID omitted]. The monitor confirms active endpoints and Sthree USB endpoints in the unplugged state; no Sthree USB HID reports captured.

Why Bluetooth is not an identical control to USB

Teams uses call-control-service-vtwo / VoipCallCoordinator for the Bluetooth path. The USB HID handler does not associate these endpoints with the USB telephony device. Saving ON also logs “Slimcore version doesnt support toggle sync”: the client’s true value is confirmed, but does not establish identical propagation and handling of all native controls.

Conclusion: Bluetooth is stable in the short tests and supports a USB/HID-path-specific issue. This does not establish lasting stability under all conditions or, by itself, assign responsibility to a component.

Dongle, radio and USB connection

The Trust two four five three zero is not required to reproduce the issue. The logs do not establish that it generates the hangup command: the decisive reports belong to the Sthree. Radio effects at two dot four GHz, USB controller/power issues and software interactions are distinct mechanisms and must not be conflated.

Etwo includes two USBHUBthree “Client Initiated Recovery Action” events on Generic USB Hub VID_zero fiveEthree/PID_zero six one zero, root port four, about one minute before the main sequence. The Sthree is on root port three, not directly downstream of that hub. These events do not establish the cause of the hangup.

five. Instrumentation, limitations and support requests

SthreeMonitor vthree collection

Raw Input and preparsed HID data; PnP inventory/changes; audio endpoint/default snapshots; processes and network; Windows events; USB ETW trace through USBXHCI, UCX and USBHUBthree. The supervisor separates collectors into processes with timeouts, writes logs during collection and handles markers and stopping. It was introduced to fix the console freeze in the previous synchronous collection.

ETW session ; Events processed / lost

- Etwo ; one six,one three four / zero

- Ethree ; one six,two seven three / zero

- Efour ; nine,eight six seven / zero

- Efive ; three,one six one / zero

- Esix ; two four,four one six / zero

- Eseven ; eight,four four nine / zero

Checked Sthree USB completions show no errors. Pending status zeroxfour zero zero zero zero zero zero zero and rundown values are not treated as completion errors. In Etwo, no Sthree PnP/Raw Input removals are recorded; audio polling at two s does not exclude shorter pauses.

Collected drivers: Microsoft USB audio one zero dot zero dot two six one zero zero dot nine four four four (wdma_usb.inf); HID telephony/headset one zero dot zero dot two six one zero zero dot nine two seven eight (hidtelephonydriver.inf); HID consumer one zero dot zero dot two six one zero zero dot one (hidserv.inf); USB composite one zero dot zero dot two six one zero zero dot nine four four four (usb.inf). Different versions of different components do not establish a conflict.

Limitations to retain in the assessment

Raw Input is downstream of drivers, not a direct capture of bytes on the wire. Kernel-context ETW PIDs do not identify the originating client. teams.jsonl is empty in the collections considered: separate weblogs are the application-level source. In Etwo, the detailed PnP baseline is incomplete; the marker arrived after stopping began. Internal firmware and RF interference are not measured; the initial Teams export and some windows do not retain all lines at the same level of detail.

Request to Microsoft

Identify the client and reason for the initial microphone reconfiguration. Review telephony off-hook state handling during transient USB-stream pauses and protection against unintended hangups in the Standard Hook Protect USB handler. Specify the audio/HID capture with client attribution needed to complete the diagnosis.

Request to Anker

Review the telephony state exposed by Athree three zero two with firmware two dot two dot eight when the USB microphone stops/starts; confirm expected behavior and Teams compatibility. Identify any firmware fix for the exact model, avoiding unrelated updates.

Mitigation verified in the tests: USB with synchronization OFF. Bluetooth is an alternative that was stable in the short tests. No indiscriminate driver reinstallation has been performed, nor has a need to replace the Trust been established.

six. Archive index and references

This post summarizes the evidence; full logs are not included. The table uses aliases, not original filenames. Technical sequence timestamps and software versions are retained. Full archives should only be shared through a private channel agreed with support.

ID ; Archive aliases (original names omitted)

- Eone ; Teams-WebLogs-Eone.zip

- Etwo ; SthreeMonitor-Etwo.zip

- Ethree ; SthreeMonitor-Ethree.zip

- Efour ; SthreeMonitor-Efour.zip / Teams-WebLogs-Efour.zip

- Efive ; SthreeMonitor-Efive.zip / Teams-WebLogs-Efive.zip

- Esix ; SthreeMonitor-Esix.zip / Teams-WebLogs-Esix.zip

- Eseven ; SthreeMonitor-Eseven.zip / Teams-WebLogs-Eseven.zip

- Eeight ; SthreeMonitor-Eeight.zip / Teams-WebLogs-Eeight.zip

- Enine ; SthreeMonitor-Enine.zip / Teams-WebLogs-Enine.zip

Export mentioned but unavailable at the time of the relevant analysis: Teams-WebLogs-unavailable.zip. No conclusion relies on its contents. Local CSV/TXT analyses are derived from the files above and do not replace the originals.

Official technical references

Windows HID parser - HidP_GetUsages

https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/hidpi/nf-hidpi-hidp_getusages

USB alternate settings

https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/select-a-usb-alternate-setting

Teams - device and button settings

https://support.microsoft.com/en-us/teams/notifications-settings/manage-your-device-settings-in-microsoft-teams

Anker - PowerConf / Sthree / PowerConf+ FAQ

https://www.ankerjapan.com/blogs/faq/powerconf-powerconf-sthree-powerconf

Summary based on logs and tests provided by the user. It distinguishes observed evidence, reported outcomes and unresolved hypotheses. It does not assign unproven responsibility to Microsoft, Anker or Trust.

How to transfer an external SIP call directly to a Teams user's voicemail?

Jaimin18 — Thu, 01 Oct 2026 08:32:27 GMT

Hi,

I am working on an external SIP-based reception platform that connects to Microsoft Teams through Direct Routing.

My requirement is to transfer an external call directly to a Teams user's voicemail without ringing the user's Teams devices.

The current flow is:

External Call → Reception Platform → SIP/Direct Routing → Microsoft Teams

A normal SIP transfer to the Teams user's SIP address rings the user. I need the call to go directly to their Teams voicemail.

I have been investigating SIP REFER/INVITE and found references to using:

sip:email address removed for privacy reasons;opaque=app:voicemail

I also found information about a User-to-User SIP header, but I am not sure which approach is officially supported by Microsoft Teams Direct Routing.

I have tried the opaque=app:voicemail approach, but I have not been able to get the call to reliably go directly to voicemail.

Could someone please clarify:

What is the officially supported way to transfer an external SIP call directly to a Teams user's voicemail?
Is opaque=app:voicemail supported with Direct Routing/SBC?
Is there a specific SIP header or URI parameter required?
Should the SBC modify the REFER or the subsequent INVITE?

Any Microsoft documentation or example SIP messages would be very helpful.

Thanks!

Add Outlook as an App in Teams?

oks_tle — Wed, 30 Sep 2026 08:56:06 GMT

Any news on this ?

I'd ask at Add Outlook as an App in Teams? | Microsoft Community Hub but "Replies have been turned off".

Thanks

Unable to access Teams from a PC (only mobile access)

alexander_999 — Wed, 30 Sep 2026 08:12:41 GMT

We have a user who can't access Teams on PC, but it works as usual on mobile (however, no connections to Outlook for Teams or the ability to create Teams meetings). Have tested several different PC’s as well as app and browser, none of them work.

The problem is that the user cannot find the primary organization when logging in to Teams and it only shows guest organizations (which cannot be connected to either).

Below is the answer I got when I made a diagnosis of the login problems. I have found that this "guest account" is Microsoft.com, but that does not remove the fact that the primary organization does not show up at all. Do not know if anyone has seen this before or knows what to do. So all kinds of info are helpful because I am completely out of ideas.

What identifies the right external organization

User: Name (email address removed for privacy reasons)
App: Microsoft Teams
Type of access: B2B collaboration
Error code: 500571
Error: Guest account is disabled
External target tenant: f8cdef31-a31e-4b4a-93e4-5f571e91255a
Correlation-ID: d7c0c004-ed20-4cd5-a056-7ce0d7f0ae24

This means that it is the organization that owns the tenant ID f8cdef31-a31e-4b4a-93e4-5f571e91255a that should be contacted. If you have several guest organizations associated with you, there is no need to guess in this case — the failed event points out exactly which external tenant received the request.

Practical way to find which organization it is

Search your documentation or previous invitations by tenant ID f8cdef31-a31e-4b4a-93e4-5f571e91255a.
Ask User to check which organization he was trying to switch to in Teams just when the error occurred.
If you have multiple external partners with similar names, match the tenant ID to the partner you have B2B collaboration with.
Please send the correlation ID and time 2026-09-09 10:43 UTC to the external administrator so that they can find the same event at their place.

Conclusion

You need to contact the external organization that corresponds to the tenant ID f8cdef31-a31e-4b4a-93e4-5f571e91255a and ask them to check Users guest account. This is where the account appears to be disabled.

Teams Retains Stale App Metadata After Removing and Re-uploading a Sideloaded App

bharath123 — Tue, 29 Sep 2026 07:54:51 GMT

After the app is removed and subsequently re-uploaded, Microsoft Teams appears to retain stale application metadata or session information from the previous installation. This may include the previous app identity, bot or static tab references, and WebView session state.

As a result, Teams may display errors such as "This app can't be found" or prevent navigation to the Messages/Chat section, even though the application configuration and React routing are functioning correctly.

The issue appears to occur particularly when the application is re-uploaded using the same manifest version. Completely quitting and restarting Teams may temporarily resolve the problem.

Expected Behavior

After removing a sideloaded app and uploading it again, Teams should load the latest application configuration and should not retain stale metadata or session state from the previous installation.

Actual Behavior

Teams may continue using stale app metadata or session state after the app has been removed and re-uploaded, resulting in navigation failures or "This app can't be found" errors.

Is there any rate limiting on inbound messages through bot framework?

DigvendraSinghTomar — Mon, 28 Sep 2026 08:40:46 GMT

I found this documentation regarding rate limits for app using bot framework - https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/rate-limit. However, it seems to be applicable to outbound messages from our service backend to MS Teams. Is there any similar rate limiting for messages being pushed to our backend from Teams conversations?