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.
Stop Automatic Calling when Screensharing
I screenshare a lot in my position; I call the coworker (Phone/Headset) and train them on what I need them to look at. I am in a large office building, and the automatic calling of the receivers' PC is disruptive, as I do not was the whole office to hear my conversation or have people hear my trainee. I see no way to disable the team auto-call once I start to screen share or in the Options. All my coworkers feel this frustration as well. I do use the computer microphone/speaks aspect when working from home, but would disable it totally, if it would stop the auto-call. I do not want it to affect meeting invites to others, as others around the country can use their PC speak/microphone, if they want. Please advise.Teams is unable to access your calendar
I started the below error on a lot of computers today. My co-worker did not get the error UNTIL he updated to the same version of Teams as me You have Microsoft Teams version 25072.1609.3541.7814. You've got the latest version. It was last checked on 4/7/2025. The issue is with multiple windows 11 users and their local teams installation. Brand new issue and trust me I'm the admin there were no changes by me. (in Exchange or Teams) I've run the Exchange connectivity test (ok) The MS remote connectivity test fails with this error Make sure user has Exchange Web Services EWS and REST API protocols enabled. The Microsoft 365 Teams Calendar App diagnostics referenced in the link requires a Microsoft 365 admin account to be executed This worked Friday, it does this today. What changed?
Teams calls reporting as potentially scams incorrectly
Hey Teams Community, In the past 5 days I am seeing callers from external tenants that are trusted and in mto showing as suspected scam callers when they call me. They see.me as a suspected scam also when I call. These tenants are all trusted and most of them are.members of the same MTO. This only started happening in the last 7 days. What is causing this? Does anybody else see this happening recently with a similar setup?
Teams feedback function does not work
Additional issue – Teams feedback function does not work Microsoft’s support documentation currently directs users to submit feedback and report technical problems directly through the Teams application. I have attempted to follow this recommended procedure using the Microsoft Teams app on an iPhone in Sweden. However, the feedback function does not work. When attempting to submit feedback through the Teams iOS application, the application displays the error message: “Something went wrong.” As a result, I am unable to submit the bug report through the feedback function that Microsoft itself recommends. This appears to be an additional technical issue with the Teams feedback functionality, at least when using the Teams mobile application on iOS in Sweden. Furthermore, the feedback interface does not provide me with a usable way to select an existing image from my photo library to document the error. The instructions appear to suggest taking a screenshot, but in this particular case that does not adequately document the problem because the relevant error occurs within the feedback interface itself. I therefore have two related issues when attempting to report this problem: Microsoft’s recommended in-app feedback function fails with “Something went wrong.” The feedback interface does not provide a practical option to attach an existing screenshot from the iPhone photo library. I would therefore like Microsoft to investigate not only the original Teams meeting and multi-device synchronization issue, but also why the recommended feedback mechanism is not functioning correctly on the Teams iOS application. Please note that I am reporting this based on my experience using Microsoft Teams in Sweden on an iPhone on August 21, 2026.
Teams Freezes ~90 seconds into a 1:1 Mac OSX
Teams video and audio starts freezing 90 seconds into a 1:1 call, and then it comes back to normal and wont happen again. This started about 3 weeks ago and it happens only during 1:1 calls wont happen when there are more then 2 people in a call. Mac OSX 26.5.1 (25F80) Teams Version 26149.1804.4788.5681Teams black and green lines when sharing screen and recording impact
When sharing screen on mac osx the screen share sometimes goes black with green and white lines all scrambled. Also the recording gets impacted while screen sharing is totally fine during the meeting. This started in the last 1-2 weeks. Teams Version 26149.1804.4788.5681
Mouse pointer lag or delay or shaky
Hi, there is an issue when joining a Teams meetings leading to a significant lag or delay of mouse pointer speed. This happens across devices (notebooks, workstations); this is affecting a novel Logitech device connected via BT and Teams joining via web-interface, but also for Teams App. IMO this is a fundamental issue (either PHY or MS level), why a software (Teams) is suddenly "interfering" with the mouse pointer (speed). Internet bandwidth is fine at > 50 mbit. Once I logout of the meeting, the pointer is "released". Additionally, the lag is immediately "released", once another users starts sharing (taking over). Note that the lag is there before sharing anything from main-user side. Does anyone experience this "phenomena"? Are there any reports, which are known to the MS Teams dev team. Are there any ideas or concrete solutions to this issue? I consider "go to settings" not the answer, this seems to be some be internal or "layers below the surface". RegardsAnyone Else Having Issues?
Hello! My company uses Teams as our main communication channel. For the past two or three weeks we have had significantly more issues than usual with Teams. Messages will sit and not send for sometimes over an hour. We have tried the standard troubleshooting methods and are still facing this problem. Is it just us or is this a bug? If so, is Microsoft working on a solution? Thank you!
