Ability to take Personal Notes on Interactions in TEAMS
I have a lot of situations where I would like to take and keep personal notes associated to a specific TEAMS interactions. I don't want to have to keep my notes in a separate place like OneNote or Outlook. Requests Don't make the notes public for all of the participants (possibility to add a private tab to the interaction window in TEAMS Access the notes directly through the window in TEAMS for the Chat, phone call, or meeting
Best External Access configuration
I’m looking for guidance on the best Microsoft Teams configuration for the following goal: Objective Prevent random external domains from: Looking up users in Teams Sending 1:1 chats Making direct audio/video calls At the same time: External users invited to Teams meetings should not appear as AnonymousMicrosoft Teams updates : Two presenters can share their screens
Summary Starting in late November 2026, Microsoft Teams will support simultaneous screen sharing by two Microsoft Teams will allow two presenters to share screens simultaneously in meetings starting late November 2026. This feature enhances collaboration by displaying both shared contents at once. Tenant admins can control this setting, and meeting organizers can enable or disable it per meeting. No compliance issues identified. Rollout Schedule: General Availability (Worldwide): We will begin rolling out in late November 2026 and expect to complete by mid-December 2026. Impact on Your Organization: This capability will be enabled for all meetings by default, allowing a second presenter to start sharing without requiring the first presenter to stop. When enabled, participants can see both shared content streams at the same time, creating a more seamless experience for scenarios such as comparing documents, presenting complementary information, or collaborating across multiple sources. Meeting organizers will also have a meeting option to control whether multiple presenters can share simultaneously in an individual meeting. Action Required/Recommendations: Organizations will have tenant-level admin control to determine whether simultaneous sharing is available to their users. Review your organization's sharing policies and inform users and support teams about the new experience.Microsoft Teams update: QR code protection for messages from external users
Microsoft Teams is adding extra security to protect users from phishing and fraud. QR code images sent by external users will be hidden by default. Users can choose to reveal the image before viewing or scanning the QR code. Rollout schedule Targeted Release: Beginning in October 2026 General Availability (Worldwide): Beginning in late October 2026 Impact on your organization Who is affected Organizations that allow communication with external users in Microsoft Teams. Users who receive Teams messages from external senders. Teams administrators and support teams that manage external collaboration policies. QR code images sent by external users will be blurred by default in Teams messages. Users can reveal the image if they trust the sender and want to scan the QR code. A blurred image does not mean the QR code has been identified as malicious. This protection will be applied automatically to QR codes received from external users. No admin configuration or policy changes are required. The feature will be enabled by default during the rollout. Action required and recommendations No admin action is required before rollout. Inform users that QR code images from external senders may appear blurred by default. Remind users to verify the sender before revealing or scanning QR codes. Review existing user education materials related to phishing awareness, QR code safety, and external collaboration. Update internal help desk documentation to reflect the new user experience. https://www.linkedin.com/feed/update/urn:li:activity:7520938452184408065/Report Hypes Attacks Through Teams Federated Chat
A report by a security company described how 30% of “monitored organizations” experienced an attack by a spurious IT worker over Teams federated chat. These kinds of social engineering attacks do happen, but Teams includes an array of defensive features that Microsoft 365 tenants can use to resist this kind of activity. The interesting question is just how prevalent these attacks are in the wider Teams installed base and how many of the tenants who are successfully attacked use features like an external access allow list. https://office365itpros.com/2026/10/28/federated-chat-attack/
Planner task comments no longer send email notifications – critical regression
This change removed a previously existing core functionality without providing an adequate replacement. With the new Planner experience, task comments no longer trigger automatic email notifications to assigned users. This breaks a critical communication mechanism that many teams relied on for reliable task coordination. As a result, assigned users are no longer consistently informed about updates, introducing a high risk of missed information and operational issues in day-to-day work. There is currently no supported or enforceable alternative to ensure users are notified. Previous behavior: Task comments triggered automatic email notifications Assigned users were reliably informed Communication was traceable and consistent Current behavior: No automatic email notifications No configuration to restore this @mentions required (manual, error-prone, not enforceable) Microsoft Support has confirmed that this is by design and cannot be reverted. From an enterprise perspective, this is not just a design change, but a regression of critical functionality without an equivalent replacement. Request: Please restore automatic email notifications for task discussions or provide a reliable, enforceable alternative for notifying assigned users. Question to the community: How are you handling this change in real-world scenarios? Switching tools? Enforcing @mentions? Moving communication out of Planner? Would appreciate hearing how others are dealing with this.
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!
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 Enables Easier File Sharing in Federated Chat
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/
Is there any rate limiting on inbound messages through bot framework?
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?
