How to Remove Teams Chat Threads with PowerShell
Sometimes, Microsoft 365 tenants need to remove problematic Teams chat threads from user view. The usual reason is because someone posted some bad or objectionable content to Teams. This article covers how to use Microsoft Graph PowerShell SDK cmdlets to find chat threads, to check thread messages for targeted content, and to remove matching chat threads. The code can be run interactively by an administrator to clean up Teams. https://office365itpros.com/2026/06/15/delete-teams-chat-threads/Upcoming change: disabling Teams meeting recording expiration notification emails
UPDATE: Please see the updated post on this topic here: Update: You can now control Teams Meeting Recording expiration notification emails | Microsoft Commu… Hello, We wanted to share an important update regarding email notifications for expired Microsoft Teams meeting recordings. Based on valuable feedback from our community, we’ve decided to make a change to how notifications are handled. What’s changing: Starting June 1st, we will stop sending email notifications for expired Microsoft Teams meeting recordings. We are making this change due to complaints we received from many customers about the high volume of notifications which they deemed low value. This change allows us to respect your preferences while ensuring critical communications remain accessible. Recording expiration and deletion policies remain unchanged and items that expire will be deleted even when notifications are not being sent. How to keep receiving notifications: For those customers that would like to continue receiving email notifications, we will create a new setting and make it available before June 1st. This will be a per-tenant setting. We will send another message center post once this setting is available and update our documentation in this discussion and on our support page. After June 1st: If you didn’t change notification settings before the deadline, you can still re-enable them at any time by running the PowerShell command. Note: Our original message center post incorrectly asked recipients to fill out a survey and failed to include a link to the survey. We are committed to providing options that work for your organization, and we would like to hear from you. If you have questions or additional feedback about this change, please complete this survey and join the discussion: Teams Meeting Recording Notification Changes – Fill out form Thank you for being part of our community.
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.
Regarding Teams Meeting Media Transport Behavior in VDI Optimization Scenario
Hello Microsoft Teams Engineering Team, I am currently working on a Browser Content Redirection / media offload implementation for a VDI environment, where WebRTC media transport is handled through a local native component while the Teams application continues running inside the virtual desktop session. While testing, I observed that: 1:1 calls successfully receive audio and video media But in meetings auido / video RTP is never forwarded despite successful ICE, DTLS, and SRTP establishment DTLS ApplicationData traffic is present during meetings, suggesting DataChannel/SCTP activity Based on transport-level observations, it appears that Teams meetings may rely on SCTP/DataChannel communication for SFU video subscription management, while 1:1 calls do not require the same subscription flow. I wanted to ask whether: Teams meeting video forwarding depends on active bidirectional SCTP/DataChannel connectivity Meeting video subscriptions are expected to be coordinated over the WebRTC data channel/control plane Split ownership of media transport and control-plane transport could affect expected Teams meeting behavior in VDI optimization scenarios Thank you for your time and guidance. Best regards,Rajdev
Feature Request: Real-Time Multilingual Voice Translation in Microsoft Teams
Hello Microsoft Teams Community, I would like to suggest a feature for Microsoft Teams that could help multilingual users communicate more naturally during meetings. Feature Idea: Each participant can speak in their own native language, and Teams will automatically translate and play the speech audio in the listener’s selected language in real time. Example: Telugu speaker talks in Telugu Kannada user hears Kannada audio Hindi user hears Hindi audio English user hears English audio This would be more powerful than subtitles because users can continue conversations naturally in their mother tongue without needing to read captions constantly. Possible Technologies: Speech-to-Text AI Translation Text-to-Speech Real-Time Voice Streaming Benefits: Better communication in multilingual countries like India Improved accessibility Easier collaboration for global teams More inclusive meetings I believe this feature could significantly improve communication in international and regional meetings. Thank you.
New MTR devices unable to connect workplace
Hello collective im facing an issue with new Poly devices Poly X52 + Poly TC10 + Poly Trio 60 Poly X52 + Poly TC10 Both devices can not connect to M365. Error message: "Couldn't connect to Workplace Join. try again, or contact your admin." Firewall settings seems to be ok and devices are on the same VLAN. What is the workaround for this kind of issue or what should we check first? Best regardsUpdate to disabling Teams meeting recording expiration notification emails
Hello, Thank you to everyone who shared their thoughts and feedback regarding the planned Upcoming change: disabling Teams meeting recording expiration notification emails. After carefully reviewing the feedback from this discussion, survey responses, and support channels, we have decided to pause the rollout of this change. The updates originally planned for June 1st will not take effect on that date. What this means for you: - Email notifications for expired Teams meeting recordings will continue as they do today. - No action is required on your part. - Recording expiration and deletion policies remain unchanged. Your input along with ongoing, internal engineering discussions helped shaped this decision. We want to make sure that any changes we make to the notification experience truly work for your organizations, and the feedback we received made it clear that we need more time to get this right. We're still committed to improving the notification experience for Teams meeting recordings and will provide updates here and through the Message Center when we have more to share. In the meantime, please continue to share your thoughts in this discussion. Thank you for your patience and for being part of our community.
