How to set Chat tab as default when starting teams
Good morning. I'm an IT contractor with M365 admin access at all of my clients who use it. I started using the new MS Teams because I am able to log into multiple accounts at once, but when I switch between clients they each default to different tabs. One defaults to chat, another defaults to teams which, for that client is a blank screen, and I wait for it to load then I realize I'm on the wrong tab (every single time, so annoying,....) I switched back to classic teams and I noticed that when I started Teams for these two clients they default to those same respective tabs when loading. This is better because I am able to load that other client once and switch to the chat tab and just keep it open, but new teams keeps loading the Teams Tab. I'm hoping that if I can change the default tab in classic Teams it'll change it in new Teams. Why are these two clients different and is there any way to change it? Thanks!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/Update: You can now control Teams Meeting Recording expiration notification emails
Hey Teams community, We've heard the feedback. For admins and users managing a high volume of meetings, TMR expiration emails can pile up fast. We've been working on giving you control, and that control is now here. What's new Tenant admins can now use a PowerShell cmdlet to suppress Teams Meeting Recording expiration and deletion notification emails across their organization. Notifications stay on by default (no change if you do nothing), but if you'd like to turn them off, here's how. Prerequisites Latest version of SharePoint Online Management Shell (download here). Note, it's Windows-only, so you'll need a Windows machine or Azure Virtual Desktop SharePoint Admin or Global Admin permissions Steps 1. Connect to your tenant powershell Connect-SPOService -Url https://<your-tenant>-admin.sharepoint.com 2. Check the current value powershell Get-SPOTenant | Format-List *Recording* False = notifications currently on (default). True = notifications suppressed. 3. Suppress notifications powershell Set-SPOTenant -DisableTeamsMeetingRecordingDeletedNotification $true You'll see a confirmation prompt — enter Y to proceed. 4. Verify powershell (Get-SPOTenant).DisableTeamsMeetingRecordingDeletedNotification True means you're all set. No more expiration emails for your tenant. Want to turn them back on later? Just run the same command with $false. What doesn't change Recordings still expire and delete on the same schedule No per-user settings, no UI changes. This is purely a tenant-level admin toggle We'll keep monitoring feedback, and as always, drop your questions below.
Microsoft Teams transcription language settings
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 ?
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!Architectural Limitation: Move LBR from Gateway to Voice Routes for Shared Trunks
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. https://imgur.com/a/RzTE4nu 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
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.
