small white window that opens during sharing in a meeting
Hi, I've Teams vers. 26120.3106.4722.3411. For some time when I access to a meeting and sharing the screen, a window or a presentation, a small white windows appears at the bottom right and I cannot close it. To close this window and to prevent it from opening again I need to disconnect to Teams also for 2-3 times. Well, how could I solve a such issue permanently? Thanks This is the window image that I can capture: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.Introducing a refreshed design, task chat, and more in Microsoft Planner
We’re excited to announce that a modernized user interface and new features are now rolling out to basic plans in both Planner in Teams and Planner for the web. The updated design offers enhanced navigation, responsive layouts, a new goals view for setting objectives and priorities, and task chat—one of your most requested features—to enable real-time collaboration and @ mentioning team members. This release aims to make planning easier for everyday users while preparing for future AI-powered capabilities. Our goal is to streamline planning by making it more intelligent and connected, so teams can concentrate on achieving results rather than managing tasks. What's new in Planner A refreshed design: With this rollout, users will be able to manage their plans in a cleaner, more modern interface that brings a more consistent planning experience across work. Planner’s new look was designed to feel simpler, allowing users to find what they need. It reduces visual clutter, improves layout and spacing, and creates a more focused workspace. Task chat with @ mentions: A new task chat is coming to basic plans, bringing real-time, threaded conversations directly into tasks, including @ mentions, rich formatting, emojis, and notifications to help keep decisions tied to the specific task at hand. Plan members who are @ mentioned in a task will receive a notification in their Teams Activity feed and via email and can select the notification which takes them directly to the task card for additional context. Note that previously, users received notifications for every task comment, but as a result of customer feedback, we now only send notifications to mentioned users. The ability to @ mention team members directly in a task has been a top request, and we’re excited to roll this out in a familiar, chat-based experience. Please note, premium plans will continue to utilize the existing task conversation experience. This will converge into the new experience at a later point in time. Goals view: Basic plans will now include a dedicated Goals view, allowing teams to set clear, well-defined objectives to help prioritize work. By connecting tasks to shared goals, teams achieve greater alignment, gain clarity on priorities, and track progress and outcomes—driving the plan forward together. Access to Goals view in basic plans requires either a Planner premium license or a Microsoft 365 Copilot license. Notes on availability Please note that not all users will see the new Planner interface at the same time. This refreshed interface, along with Task chat and Goals view, begins rolling out to basic plans today and will continue to roll out over the coming weeks. This is only the beginning This redesign lays the groundwork for many more improvements coming to Planner in the next few weeks and months, including: Project Manager agent in basic plans – to help with task execution and the creation of status reports. Custom templates. Planner in Outlook. Stay tuned for announcements regarding these updates and more aligned to our long-term vision for integrated work management. Feature availability, naming, and timelines are subject to change. Please refer to the Microsoft 365 Roadmap for the latest status. Addressing your feedback We heard your feedback about inconsistencies between basic and premium plans. This refresh starts closing those gaps, so features appear consistently across plans based on your license. For example, users with a Planner premium license will now see Goals in basic plans, and users with a Microsoft 365 Copilot license will soon have access to Project Manager Agent in basic plans as well. Tell us what you think about the new Planner interface, Task chat, and Goals view by selecting More (circled question mark icon) in the top right corner of the app, then selecting Feedback from the dropdown menu. We also encourage you to share any feature requests by adding your ideas to the Planner Feedback Portal. Your feedback helps inform our feature updates, and we look forward to hearing from you. Learn more Visit planner.cloud.microsoft to access Planner directly from your browser. Sign up to receive future communication about Planner. Learn more about Planner in our Frequently asked questions. Check out the Planner adoption page and Planner help & learning page to learn more about Planner. Visit the Microsoft 365 roadmap for feature descriptions and estimated release dates for Planner. Walk through the interactive demos for Project Manager Agent in Planner and Project Manager Agent skills in Teams meetings.
New enhancements in Private Channels in Microsoft Teams unlock their full potential
Private channels have long empowered focused collaboration among a subset of a team’s members. Whether you're managing sensitive projects, driving confidential initiatives, or simply need a space for more targeted discussions, private channels offer the control and privacy your team needs. Now, private channels are evolving to meet the needs of modern teams. In response to customer feedback, we are introducing enhanced flexibility, greater scalability, and streamlined compliance management. Read on to learn about these key enhancements and how to prepare. Why Private Channels Matter Private channels offer a dedicated space for conversations that benefit from added structure, persistence, and control. They’re especially valuable when navigating sensitive topics like budgets, HR discussions, managing project-specific workstreams, or collaborating with clients and vendors who require limited access .While chat are ideal for quick exchanges, private channels help keep discussions organized, make shared files easier to find, and help ensure conversations remain accessible over time, all while giving you more control over who can access. What’s Changing—and Why It Matters To support growing usage and help simplify compliance, private channels will now use a group mailbox (like shared channels) instead of storing messages in individual user mailboxes. This change unlocks several key benefits: 🚀 Expanded Limits Feature Current New Max private channels per team 30 1000 Max members per private channel 250 5000 Meeting scheduling ❌ ✅ Supported Simplified Compliance At a user level Group Helping to Simplify Compliance By aligning private channels with group-based storage, compliance policies (e.g., retention, legal hold, DLP, eDiscovery) can be applied at the team (Microsoft 365 group) level, helping to reduce complexity and driving consistency across channel types. For example, one retention policy can be applied to the team’s group, instead of managing a separate policy for private channels. Organizations with compliance policies (retention, legal hold, DLP, eDiscovery, Optical Character recognition) for private channels must ensure those policies are also applied to the team’s group scope before migration begins. Existing policies for user mailboxes will continue to apply; post-migration, new private channel data will be governed by policies of the group mailbox. What Compliance Admins Need to Do To enable a smooth transition and help maintain compliance coverage, follow the below: Microsoft Purview Hold and eDiscovery Before Migration: In Microsoft Purview compliance portal, update hold policies to include the team’s Microsoft 365 group mailbox in addition to user mailboxes. After Migration: New data will reside in the group mailbox. For full eDiscovery, search both user and group mailboxes. Note: Private channel message history (edits/deletes) in user mailboxes under an existing hold will remain in their preserved user library folder until the hold expires. Microsoft Purview Data Loss Prevention (DLP) Policies Before Migration: In Microsoft Purview compliance portal, update DLP policies to include team’s group. After Migration: Check that the DLP policies are scoped to the group mailbox for private channels. Microsoft Purview Retention Policies Before Migration: In Microsoft Purview compliance portal, go to solutions -> Data Lifecycle Management -> Retention policies Create Teams channel messages policy scoped to Teams having equivalent Retention type and duration similar to existing private channel retention policies. After Migration: Set retention policies for the parent team with all channels in the team in mind, including private channels. Microsoft policies for Optical Character Recognition Optical character recognition (OCR) is managed via Data Loss Prevention (DLP) policy. Before migration, modify the corresponding DLP policy that needs be applied for OCR to private channels and change locations to all users and groups. What’s Next This update helps make private channels more scalable, manageable, and compliant. It’s a big step forward for organizations that rely on Teams for secure, structured collaboration. Migration is scheduled to begin in early October 2025 and is expected to be completed by the end of December 2025 for the worldwide cloud. During this period, private channel data will gradually move from user mailboxes to the team’s group mailbox. Private channels can be used throughout the migration. Special cloud migration will happen in early 2026. Migration can start or end at different times for each tenant during the rollout period. To track progress, a new PowerShell command will be available for tenants to check whether their migration has started or is completed. The command will be - Get-TenantPrivateChannelMigrationStatus -TenantId <tenantId> We’ll be updating public documentation soon and will share links here.
How to find pictures/screenshots in a chat
HI All We use teams chat to share screenshots all the time, but it seems these shared screenshots are not saved in the file tab. It is very difficult to browse through the complete chat history to find them because I cant find a way to filter all the pictures, etc. Does anyone know the trick? Thanks
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
Adaptive Cards in Teams channel messages: fixed narrow width — request for width control
Hi Teams Platform team, We post structured status reports as Adaptive Cards into a Teams channel. The card consistently renders at a fixed width of 448 px on a 1080p display at 100% scaling with a maximized Teams desktop client — well below the available channel message stream width. Wide multi-column tables get truncated or wrapped, which significantly hurts readability. What we've tried No card-level `width` property exists in the Adaptive Cards schema. `msteams.width: "Full"` is documented to apply only to Stageview / task module / tab — silently ignored in channel messages (tested). Same payload via three delivery paths — Incoming Webhook, Logic App "Post adaptive card in chat or channel", and Microsoft Graph `POST /teams/{id}/channels/{id}/messages` — all render at the same narrow fixed width. The constraint is in the Teams channel-message renderer, not in any delivery layer. Minimal repro payload (7-column results table; all field names and values replaced with generic placeholders): { "type": "message", "attachments": [ { "contentType": "application/vnd.microsoft.card.adaptive", "content": { "$schema": "https://adaptivecards.io/schemas/adaptive-card.json", "type": "AdaptiveCard", "version": "1.5", "msteams": { "width": "Full" }, "body": [ { "type": "TextBlock", "text": "Pipeline Report — run-001", "weight": "Bolder", "size": "Medium" }, { "type": "Table", "gridStyle": "accent", "firstRowAsHeaders": true, "columns": [ { "width": 2 }, { "width": 1 }, { "width": 2 }, { "width": 1 }, { "width": 2 }, { "width": 1 }, { "width": 1 } ], "rows": [ { "type": "TableRow", "cells": [ { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "Col-1", "weight": "Bolder", "size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "Col-2", "weight": "Bolder", "size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "Col-3", "weight": "Bolder", "size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "Δ Col-3", "weight": "Bolder", "size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "Col-4", "weight": "Bolder", "size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "Δ Col-4", "weight": "Bolder", "size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "Status", "weight": "Bolder", "size": "Small" }] } ] }, { "type": "TableRow", "cells": [ { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "item-a", "size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "mode-x", "size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "0.000/0.000","size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "+0.00%", "size": "Small", "color": "Good" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "0.000/0.000","size": "Small" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "-0.00%", "size": "Small", "color": "Attention" }] }, { "type": "TableCell", "items": [{ "type": "TextBlock", "text": "✅ Pass", "size": "Small" }] } ] } ] } ] } } ] } `msteams.width: "Full"` is present but has no visible effect in the channel message context. Feature request Either of: Honor `msteams.width: "Full"` in channel-message context (not just Stageview/task module/tab), OR Add a card-level property (e.g. `msteams.channelWidth: "Full" | "Default"`) explicitly scoped to channel messages. Is this a known limitation with an existing tracking item, or should we also file it on the M365 Feedback Portal for upvotes? Thanks!
Custom App (Static Tab) with SharePoint URL stays blank on first load in Teams Desktop Client
Hello Teams Developer Community, We have deployed a custom Teams app (v1.25) that uses a Static Tab to display our company's SharePoint intranet portal. The contentUrl and websiteUrl point to our SharePoint site. [The Issue] When a user clicks the app for the very first time in the Teams Desktop Client (New Teams), the screen remains completely blank (white loading screen). However, if the user clicks away to another app (like Chat or Teams) and then clicks back to our custom app, the SharePoint page loads perfectly. [Observations] This issue does NOT happen on Teams Web Client (browser). It loads instantly there. Clearing the Teams Desktop cache does not solve the problem. It seems to be related to WebView2 authentication/SSO redirect loops inside the iframe. I tried adding "showLoadingIndicator": true in Developer Portal, but the schema automatically strips it out upon saving. [Question] Is there a specific parameter we need to append to the SharePoint URL, or specific domains we must add to "validDomains", to prevent this initial blank screen caused by auth delays in the Desktop Client? Any guidance on handling this WebView2 rendering delay would be greatly appreciated. Thank you.Oracle Eloqua integration for Teams webinars
Would like to see Microsoft add or support an integration with Oracle Eloqua for Teams Webinars, as our Marketing team needs this integration in order to fully migrate to Microsoft Teams for our customer facing events. They continue to use an antiquated (competitor) platform because it does have the Eloqua integration.
