Shared Channels: @Channel mentions fail to trigger activity notifications for team-shared members
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!What's New in Microsoft Teams | August - September 2026
A quick note before we get into it: What's New in Teams is shifting from a monthly to a quarterly rhythm. You'll hear from us next in December, March, and June, and each edition will round up everything announced and released over the full quarter. One post, one fuller view of what's new. Two investments shape where Teams is heading, and you'll see both in this quarter's releases: AI transforming teamwork with agents as part of the team, and a simpler, smarter, more secure foundation underneath it all. AI in Teams is showing up in the flow of your work. Teams Phone Agent brings that to your phone line, helping callers with common requests in more than 60 languages and routing them with context attached, so a missed call turns into a next step instead of a lost one. Context carries forward, too. Video recap turns a meeting you missed into a short, narrated highlight reel, so what a meeting decided outlasts the conversation itself. And protection for everyday collaboration is always top of mind. The new Security Detection Report brings detections such as impersonation and malicious URLs into one view in the Teams admin center, so admins see the whole picture in one place. Read on for all the latest updates! Feature categories: (All features listed are generally available unless otherwise noted) Chat and Collaboration Meetings Teams Phone Workplace Teams Events Fundamentals and Security Teams Platform Certified devices Chat and Collaboration Ask Copilot in Teams conversations Stay in the flow of work and get help from Copilot directly within your conversations. Open Copilot from a message or selected text in a Teams conversation, with the relevant context already included, making it easier to gain insights, explore questions, and move work forward without needing to re-explain information. Find agents and apps faster through Teams search Discover the tools you need with agents and apps surfaced directly in Teams search results. As you type in the search bar, matching agents and apps appear alongside other relevant results, helping you spend less time searching and more time getting things done. Find and share files faster in Teams Locate the files you need while sharing content in Teams. Search for cloud-based files directly from the attachment experience, making it easier to find and share the right content without interrupting the flow of collaboration. Emoji shortcuts on iOS and Android Express yourself with emoji shortcuts. Desktop emoji shortcuts now work on iOS and Android. Insert emojis directly in the compose box by typing a word between colons, so :smile: becomes 😊. Autocomplete suggestions help speed up entry, and custom emojis are also supported. Clearer text highlighting in dark mode and high contrast mode Make highlighted text easier to read while composing messages in Teams. Improvements to text highlighting in dark mode and high contrast mode provide a more consistent and accessible editing experience, helping content stand out more clearly. Meetings Video recap in Teams Meeting recap now delivers a bite-sized video recap of with key highlights from your Teams meeting. It combines AI-generated voiceover summaries with video snippets, spotlighting the most important moments while preserving the original tone and flow, so you can catch up on key topics in a few minutes. Video recaps now support meetings in 23 languages across 31 regional variants, learn more. Translation button to change the language for intelligent meeting recaps After an intelligent meeting recap is generated, you can change the recap language at any time using a translation button, even if a different language was selected during the meeting. Multilingual teams get more flexibility to read meeting insights, action items, and discussion summaries in the language that is most comfortable for them. Redesigned meeting controls Stay focused on your conversations with a customizable meeting toolbar that keeps the controls you need within easy reach. Pin your most-used controls, unpin those you don’t need, and drag and drop them into the order that works for you. Raise Hand now lives inside the React button, while Leave has its own spot on the right to help avoid accidental exits. Teams Phone Teams Phone Agent Teams Phone Agent is an AI-powered receptionist for your business’s phone line, so callers can get help with common requests even after hours. For customer-facing organizations and departments using Teams Phone, such as bank branches or IT help desks, it takes repetitive calls off employees' plates so they can focus on the conversations that truly need a human touch. With support for over 60 languages and locales, Teams Phone Agent handles common requests such as answering routine questions or booking appointments. , And it can route a caller to the right department or employee with an AI-generated summary of the conversation, so customers do not have to navigate phone menus or repeat themselves. Custom voice agents are available for specialized workflows. Teams Phone Agent is now generally available, learn more. If the player doesn’t load, open the video in a new window: Open video Intelligent call recap in Queues app Intelligent call recaps in Queues app help you catch up on recorded or transcribed queue calls with AI-generated summary notes covering key discussion points and follow-up actions. To open a recap, find the call record in the Queues app call history and select Recap. Copilot in Queues app’s shared call history for post-call insights Quickly catch up on a call queue call and uncover key details with the ability to use Copilot in the shared call history in Queues app. After a recorded call is completed, users with Copilot can now open the call record in the shared call history, access the Copilot Chat sidecar from the Recap tab, and ask questions about the call. Automatic recording and transcription for call queues Capture customer interactions without requiring your organization’s calling representatives to manually start recording. Admins can enable automatic recording and transcription for individual Teams call queues and control access to recordings. Recordings are stored in SharePoint and accessible through call recaps in the shared call history in Queues app. View and manage auto attendant shared voicemails in Queues app Help your team stay on top of customer messages by managing auto attendant shared voicemails directly in Queues app. Calls routed from an auto attendant to voicemail will appear in Queues app, giving collaborative calling teams a centralized place to track, triage, and respond to messages. Customize recording and transcription notifications for Teams calls Give your organization greater control over how recording and transcription are communicated during Teams calls. IT admins can customize select user notification strings for recording and transcription in the Teams admin center, helping tailor the experience for participants in Teams VoIP calls. Enhance control of delegated calls with call lock and delegate join alerts Call delegation in Teams gains real controls: a delegator can lock an active call and see when a delegate joins. Locking prevents delegates from joining or resuming the call, and optional warning tones notify participants when a delegate joins or resumes. Workplace Interpreter agent support in Teams Rooms on Android The Interpreter agent acts as a translator in Microsoft Teams meetings, letting participants listen in their chosen language with real-time translation. It is now available in Teams Rooms on Android licensed for Teams Rooms Pro. New room optimization mode in Teams desktop Room optimization mode makes it easier to use your laptop for meetings and collaboration in spaces such as focus or huddle rooms that do not yet have a Teams Rooms system. It replaces shared display mode, has a new location, and enables or disables room-specific features. When room peripherals are connected, Teams can automatically select audio and video devices, enable speaker recognition and shared display, and disable voice isolation. Modernized Gallery view in Teams Rooms on Android The updated Gallery view in Teams Rooms on Android prioritizes video on the meeting stage, arranges participants in consistent aspect ratios, and minimizes movement of participant tiles on stage. You can hide the room self-preview video and choose to see audio and video participants equally on stage instead of prioritizing video participants. Admins can set the default behavior using local device settings and the Pro Management portal. Teams Events Breakout rooms in Teams Meetings & Events Breakout rooms are now supported in Teams Meetings & Teams Events with up to 1,000 participants across 100 rooms, increased from the previous limit of 300 participants across 50 rooms. Organizers can use breakout rooms to create smaller focused sessions within an event for more interaction and collaboration. Specify who has control of production tools in Teams Events Organizers can designate who controls production tools, granting chosen people access to Manage what attendees see and the green room so event production stays with the right crew. The setting is a new meeting option applied when the event is set up. Expanding presenter visibility in “Manage what attendees see” Producers can resize and expand the presenter panel in Manage what attendees see, making it easier to view, manage, and switch between presenters while a live event is running. New layout when sharing content for Teams events Organizers and presenters who have access to production tools now see updated layout options when sharing content in the “Manage what attendees see” experience for Teams events. The available layouts are speaker focused, content focused, and content only. The new speaker focused layout prioritizes presenter video alongside shared content for greater visibility. Available for Teams events organizers on Teams for Windows desktop and Mac desktop. Fundamentals and Security Enhanced real-time alerting rule management in Teams admin center Administrators can now duplicate an existing alerting rule to create a similar configuration without rebuilding it, bulk upload users when creating or editing a rule, and delete rules directly from the management experience. These capabilities are available for in-progress meetings and calls rule types, and organizations can configure monitoring for up to 500 users across their real-time alerting rules. Security Detection Report in Teams admin center A new Security Detection Report in the Teams admin center gives admins a unified view of messaging security detections across signals such as impersonation, malicious URLs, and weaponizable file types. Admins can review detection activity in one place and export detailed data for further investigation, improving visibility into threats in Teams. Single pane for monitoring and troubleshooting meetings and calls (Windows) Administrators can monitor meeting and call health across the organization from one place, identifying recurring issues, uncovering trends, and proactively troubleshooting problems affecting people in both live and past meetings and calls. Meeting participant detail audit records in all participating tenants Admins can now access participant-level audit records for their own users in cross-tenant meetings, helping investigate incidents even when another organization hosted the meeting. Teams audit logging now shares meeting participant detail records with all participating tenants, not just the organizer tenant, and each record includes organizer information so admins can tell whether a meeting was organized inside or outside their tenant. Teams optimization for VDI now supports Teams Events (Windows) Attendees joining Teams Events from virtualized Windows desktops can offload audio and video to their local device, supporting high definition playback while easing load on the virtual desktop. Optimization works on Windows endpoints connecting to Azure Virtual Desktop, Windows 365, Citrix, Omnissa, or Amazon. Captions, DVR, reactions, streaming chat, and Q&A are all supported, as are first-party and third-party eCDNs. Teams Platform Real-time buying signals, now in Teams Sales Navigator for Microsoft Teams delivers real-time lead and account insights directly within Microsoft Teams. Sellers can stay on top of key buying signals, discover opportunities where they work, and take action while opportunities are most relevant. The integration helps teams move from insight to action faster by surfacing Sales Navigator intelligence in their daily workflow. Unified agent and app installation management across Microsoft 365 and Teams admin center (Windows) Administrators using the Microsoft 365 admin center and Teams admin center can apply app and agent installation changes once and have them enforced consistently across Teams, Outlook, and Microsoft 365 Copilot. Previously, installation changes made in the Microsoft 365 admin center applied only to Outlook and Microsoft 365, and changes made in the Teams admin center applied only to Teams. Identify custom Teams apps that need updates for private and shared channels Admins can view a list in Teams admin center of custom apps in their tenant that need updates to work in private and shared channels. The list helps admins identify impacted apps, understand which ones require developer action, and coordinate updates so people can keep using custom apps across all supported channel types. Prominent search for app and agent discovery in the Store Search now sits in the middle of the Store page, with improved type-ahead suggestions, a more informative results page, and natural language processing to surface the most relevant apps and agents. Add multiple steps when building a workflow from scratch When building a workflow from scratch, you can add several steps at once, so you can assemble multi-step automation without returning to edit it step by step, reducing repetitive setup work and simplifying the creation of more advanced automations. Collect information with List Form in Workflows A workflow can open with a form that gathers the details it needs up front, so automation runs on structured input rather than chasing information midway. Single-character keyboard shortcuts for focused message actions (Windows) Single-character shortcuts let you quickly take common messaging actions such as edit, delete, reply, forward, pin, save, mark unread, quote reply, and react when a message has keyboard focus. The shortcuts are a predefined messaging set, and they are discoverable and customizable in the keyboard shortcuts dialog. Certified devices EPOS IMPACT 1000 MS UC ANC WL USB-C+A On-ear Bluetooth® headset. Supplied with a BTD 900c dongle, a USB‑C to USB‑A adapter, and a USB‑C charging cable. Features ANC, EPOS BrainAdapt™ technologies, and EPOS AI™â€‘powered voice pickup and noise cancellation, ensuring your voice sounds natural and clear in any environment. EPOS IMPACT 1000 MS UC ANC WL USB-C+A Stand On-ear Bluetooth® headset. Supplied with a table stand for wireless charging, a BTD 900c dongle, a USB‑C to USB‑A adapter, and a USB‑C charging cable. Features ANC, EPOS BrainAdapt™ technologies, and EPOS AI™â€‘powered voice pickup and noise cancellation, ensuring your voice sounds natural and clear in any environment. EPOS IMPACT 1000 MS UC Mono WL / ANC WL Dongle-free Bluetooth® headsets available in monaural and binaural on-ear configurations. Supplied with a USB-C charging cable and a USB-C to USB-A adapter. Features EPOS BrainAdapt™ technologies and EPOS AI™-powered voice pickup and noise cancellation for clear, natural-sounding communication in any environment. The binaural ANC WL model also includes Active Noise Cancellation (ANC) to help reduce background distractions. EPOS IMPACT 1000 MS UC ANC WL Stand On-ear, dongle-free Bluetooth® headset. Supplied with a table stand for wireless charging, a USB‑C charging cable, and a USB‑C to USB‑A adapter. Features ANC, EPOS BrainAdapt™ technologies, and EPOS AI™â€‘powered voice pickup and noise cancellation, ensuring your voice sounds natural and clear in any environment. Q-SYS RoomSuite Collaboration Bar + Controller The Q-SYS RoomSuite Collaboration Bar and expansion devices provide a scalable AV solution for standard small-to-large meeting spaces. This Windows-based solution features built-in audio, video, and supports Microsoft Teams Rooms and bring-your-own-meeting conferencing. Includes a touch panel for control and allows for optional table microphones for extended audio coverage. Q-SYS RoomSuite Collaboration Bar + Controller + Expansion Mic The Q-SYS RoomSuite Collaboration Bar and expansion devices provide a scalable AV solution for standard small-to-large meeting spaces. This Windows-based solution features built-in audio, video, and supports Microsoft Teams Rooms and bring-your-own-meeting conferencing. Includes a touch panel for control and allows for optional table microphones for extended audio coverage. The Q-SYS RoomSuite Collaboration Bar can support up to 4 expansion mics. Shure IntelliMix Room Kit 30 | 50 | 70 | 80 Microsoft Teams Rooms-certified solutions for small, medium, and large meeting spaces. Shure IntelliMix Room Kits include a Windows-based Teams Rooms compute with Shure’s premium audio signal processing, an intuitive touch panel, an all-in-one ceiling array microphone and loudspeaker, and intelligent high-resolution video. Designed for streamlined deployment with zero-touch or low-touch setup, the kits provide high-quality audio and video experiences across a range of room sizes. Simply connect devices, power on, and sign in to get started. Shure IntelliMix™ Bar Pro Kit (Black) Clearly capture precise audio and video for AI-powered meetings in medium to large collaboration spaces with this powerful all-in-one Android based video conference bar. Enterprise ready with auto-setup and simple global management, IT managers can create meeting experiences focused on participants with reliable transcription for enhanced AI tools. Shure MXA925 Ceiling Array Microphone + MXP-6 Pendant Passive Loudspeaker + MXN-AMP PoE + IntelliMix P300 This Microsoft Teams–certified bundle combines the MXA925 ceiling array microphone, IntelliMix® P300 DSP, MXN‑AMP PoE+ multichannel amplifier, and MXP‑6 pendant loudspeakers to deliver a fully validated, end‑to‑end room audio solution for medium to large spaces. Designed to meet Microsoft’s performance and reliability requirements, it provides automatic, precise speech capture, enterprise‑grade echo cancellation, and evenly distributed sound reinforcement while simplifying deployment through networked audio, PoE+ power, and a single‑vendor ecosystem. Shure MXA925 Ceiling Array Microphone + MXP-5 Ceiling-Mount Passive Loudspeaker + MXN-AMP PoE + IntelliMix P300 This Microsoft Teams–certified bundle delivers a complete, scalable room audio solution by combining the MXA925 ceiling array microphone with IntelliMix P300 DSP, the MXN‑AMP PoE+ multichannel amplifier, and MXP‑5 ceiling speakers for clear speech capture and consistent sound coverage in medium to large meeting spaces. The MXA925 uses Automatic Coverage™ and advanced IntelliMix DSP to capture natural, intelligible speech without complex setup, while the P300 provides powerful echo cancellation, noise reduction, and USB connectivity to Teams Rooms systems. The MXN‑AMP and MXP‑5 speakers simplify installation with networked audio and PoE+ power, delivering balanced, room‑filling audio for both in‑room and remote participants. Shure MXA320 Table Array Microphone+MXN5-C Networked Loudspeaker + Intellimix P300 Audio Conferencing Processor The Shure MXA320 Table Array Microphone, MXN5‑C Networked Loudspeaker System, and IntelliMix P300 Conferencing Processor form a fully certified Microsoft Teams Rooms audio bundle designed for Medium meeting spaces. This integrated solution delivers clear, consistent, and intelligible audio through advanced DSP, Steerable Coverage™ technology, and optimized networked loudspeaker performance. The MXA320 captures voices with precision while minimizing ambient noise, the P300 enhances audio quality with powerful IntelliMix® processing, and the MXN5‑C ensures natural, room‑filling sound playback. Together, they provide a seamless, scalable, and easy‑to‑deploy conferencing experience that meets Microsoft’s stringent certification requirements for performance, reliability, and user experience. Shure MXA902 Ceiling Microphone & Loudspeaker + ANIUSB-MATRIX Audio Conferencing Ki High-quality, reliable meeting room audio is now easier than ever. Certified for Microsoft Teams, the Shure MXA902 Integrated Ceiling Array Microphone + Loudspeaker, paired with the ANIUSB-MATRIX Audio Network Interface, delivers a complete, easy to install, ready to use audio solution. Designed for small and medium sized spaces, it provides premium sound, full room coverage, and seamless connectivity. Shure MXW neXt 4&8 Wireless Microphone Systems with boundary microphone configuration + MXN5W-C Networked Loudspeaker This Microsoft Teams-certified solution combines MXW neXt wireless microphones, IntelliMix® DSP, and the MXN5W-C networked ceiling loudspeaker to deliver consistent speech capture and clear room audio for hybrid learning and collaboration spaces. With flexible wireless deployment, integrated signal processing, and cloud-based management, the solution simplifies installation while providing reliable audio performance for both in-room and remote participants. Shure MXW neXt 2 Wireless Microphone System with Boundary Microphone Configuration and MXN5W-C This Microsoft Teams certified bundle combines the MXW neXt 2 wireless microphone system with boundary microphones and the MXN5W-C networked ceiling loudspeaker to deliver clear speech capture and consistent room audio for classrooms and collaboration spaces. Easy to deploy and cloud enabled for remote management, the solution simplifies installation while providing reliable wireless performance for both in-room and remote participants. Logitech Zone Vibe Pro for Business Zone Vibe Pro for Business is certified for Microsoft Teams and offers the over-ear design that people love — purpose-built for open offices and wide deployment. Our AI-powered voice isolation uses machine learning to capture your voice clearly. Adaptive hybrid ANC minimizes distractions, while custom 40 mm drivers deliver vivid, true-to-life audio.
Meeting setup in teams Channel is not allowing me to update the Agenda and send updates
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.Introducing a new feature on Microsoft Teams: "Save this message"
Exciting news - alongside pinning your posts/messages, you can now save them too. All your saved messages will be neatly organized under the "Saved" menu within Teams, right below the "Followed Thread" section. Look out for a special icon marking your saved messages for easy reference. And the best part? You have the flexibility to unsave messages whenever you wish. Stay organized and never lose track of important information with this handy
Security loophole in Private Channels?
We came across an interesting use case in our organization today. We have a Team and a private channel within that Teams team. Within the private channel a subsite was created. I am not an owner or member of the Team nor am I a member or owner of the private channel. However during creation of the subsite I was able to be invited with unique permissions to the subsite and I was successfully able to access it. After the initial creation of the subsite, our admin was not able to add or remove or effect any additional permissions on that subsite. Is this a loophole? I expected that without being a member of the private channel I would have absolutely zero access to any items associated with the private channel and site. Which has remained true (when I go to the private channel URL I get denied access) except that I do have access to this specific subsite. My instinct is that the reason permissions cannot be changed after the fact is that this is a genuine loophole and permissions weren't intended by Microsoft to be able to be granted at all on the subsite. This is due to the fact it is under the private channel and permissions should only be able to be changed via the admin UI or from the Teams application. Has anyone come across this in their work? Any guesses or explanations for why the subsite access would be initially available? Is this just genuinely a loophole in the permissions architecture?
Teams unexpectedly ends calls with Anker PowerConf S3 A3302 over USB
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.
Running engagement pulse checks in Teams, how do you track trends over time?
My lead asked me to start doing monthly pulse checks across our team of 20. I've been using Forms and dropping the link in the channel. Response rate sits around 50% which I can live with, but the real problem is that every survey is its own isolated result set. I can see this month's numbers fine. Comparing them to three months ago means exporting everything to Excel and rebuilding the comparison by hand.Is Microsoft Teams a good Intranet?
Our company is fully on Microsoft 365, but employees still struggle to find basic information like policies, company updates, forms, department resources, and important links. Most of it is scattered across SharePoint sites, Teams channels, emails, and random folders. I want to turn Microsoft Teams into that hub where all of this lives, kind of like an intranet. Any suggestions?
