MTR - Microphone drops during calls. Speaker works.
Dear experts, I'm using Microsoft Teams Rooms (Rally/Rally Plus + Logitech tap cat5e) with the latest version on Windows 11 25H2, and I'm experiencing the following issue: Problem: microphone drops during calls. Speaker works. Symptoms: - You hear occasional glitches or unexpected noise (such as clicking or popping) in the audio stream. - You might also see momentary visible glitches in a video stream. - and occasionally a USB audio or video device might stop working. Workaround - Unplug the device, and then reattach it to the computer. - If step 1 doesn't work, restart the computer. Kinda points me to a windows problem or a driver problem and not a teams problem, but still unclear on the cause I followed the steps described in this topic, but the issue still persists. https://learn.microsoft.com/en-us/troubleshoot/windows-client/setup-upgrade-and-drivers/usb-audio-video-devices-malfunction?source=docs#resolution Has anyone experienced the same issue? If so, could you please help me resolve it? Thank you in advance.
How to receive app mentions only from a channel, while having the consent to read user messages?
We're building a Teams bot (Azure Bot + Entra app) that a customer adds into a standard Teams channel. Members @mention the bot and it replies in the same thread. To make replies useful, when the bot is mentioned we want to read recent messages in that thread for context, including messages where the bot was not mentioned. We have two requirements that appear to be in tension, and we'd like your guidance on the best-supported way to satisfy both: a. Delivery: we want Teams to send our bot only the activities where it is @mentioned (not every channel message), to avoid unnecessary inbound load and Bot Framework rate-limit pressure in busy channels. b. Context read: on those mention turns, we want to read recent thread messages via Microsoft Graph (/teams/{team}/channels/{channel}/messages/{id}/replies). We've identified two approaches, each with their drawbacks: a. RSC (ChannelMessage.Read.Group) - all channel messages; team-scoped & consented by team owner at install (low friction) Concern: RSC forces delivery of every channel message; heavy backend filtering + bot framework rate-limit risk b. App permission (ChannelMessage.Read.All) - @mention-only; tenant-wide consent; tenant-admin consent Concerns: setup friction (admin consent URL, per app per tenant); read grant spans all standard channels, including ones the app isn't a member of Our core question: Option 1 gives the delivery we don't want but the scoping we like; Option 2 gives the delivery we want but a tenant-wide read grant we'd prefer to avoid. Specifically: Is there any supported way to keep @mention-only delivery and a channel-scoped (RSC-style) read grant, i.e. decouple RSC's message delivery from its read authorization? Can the tenant-wide read in Option 2 be narrowed to specific teams/channels (e.g., via a Teams application access policy or any resource-scoping mechanism), so the app can only read where it's intended to operate? Given our two requirements, which approach does Microsoft recommend, and is there any option we've missed? TIA!
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?Is Teams especially the class notebook being very slow?
Has anyone else noticed Teams being slower this last two weeks? What about class notebooks? Ours are taking more than an hour to distribute a simple page. Is that just us, or is anyone else experiencing that? What can you suggest to make it faster, how it was previously? Thank you.Unable to Add Website tab to a Team Channel
Hello Crew! Yesterday I was surprised to discover that I can no longer add a "website" tab to a Teams channel. For detail, in the past I have set up a channel with a website tab to an online survey that allows the users to report details on how the job went. I call that survey "PTR". As of yesterday, however, when I hit the + button, I am only able to add certain apps. See below. Searching for "website", or "link" doesn't yield good results. Does anyone know how to post a website tab? I'm thinking that the process has changed and I just don't know how. I hope I've been specific enough. Here's a screenshot with information redacted of what I used to apply to a channel:
Team Custom Tag usage in a Private Channel
Hello! I am having an issue attempting to use a Custom Team Tag in a Private Channel. Below is a screenshot of a Team I am an Owner of called "COPS - DEV Project Automation". I created a custom tag with two Members: I then created a Private Channel called "Test Private Channel USING tag" under the same Team. The channel has the same members as the "BSA Placeholder Tag" tag. When I attempt to "@BSA Placeholder Tag", the tag does not appear. When I use a Power Automate Cloud Flow to utilize the Tag, the post says there are zero members in it. Would a Tag created within a Team be accessible in a Private Channel under that same Team? Any help or clarifiaction on this behavior would be greatly apperciated
