Honoring Women Innovators: How Marisa Redd Is Expanding Childcare Access Through Technology
This International Women’s Day, we’re celebrating a leader who is using technology to open doors for families and strengthen her community. In Austin, access to childcare remains one of the biggest challenges facing working parents—and Marisa Redd, Senior Director at the Greater Austin YMCA, is helping reshape what’s possible. Reimagining Early Learning in Austin With Marisa's help, the YMCA introduced Tomorrow Academy, a forward‑thinking early learning model built to increase the availability of high‑quality, affordable childcare across the region. Supported by digital tools like Microsoft Teams, the organization has transformed how staff connect, coordinate, and share expertise. For the first time, teams across multiple centers can collaborate in real time, streamline program delivery, and scale services more efficiently bringing much‑needed childcare options to more families. Leadership That Moves Communities Forward Marisa’s work shows how technology, paired with mission‑driven leadership, can help solve complex community challenges. By modernizing communication and strengthening operational agility, she and her team are expanding opportunity for families who rely on accessible, dependable childcare. This International Women’s Day, we’re proud to recognize women like Marisa—leaders who are driving innovation, empowering communities, and creating lasting impact. To learn more about Marisa's story and the wonderful work of Greater Austin YMCA, please visit: Microsoft for Nonprofit LinkedIn.
App Validation Issue - Bot must send a proactive welcome message in personal scope
I'm working on a bot application for MS Teams using the Python SDK and encountered a challenge with app validation and the proactive welcome message requirement. What Happened: Initially, our bot handled the welcome message through on_installation_update, but app validation failed with the error: "Bot must send a proactive welcome message in personal scope." To satisfy validation, we added on_members_added_activity to send the welcome message for personal scope, which resolved the validation error. However, this created a new problem: on_members_added_activity is being triggered when we call the Graph API to query chats or users: {graph_url}/me/chats $filter=chatType eq 'oneOnOne' and installedApps/any(a:a/teamsApp/id eq '{teams_app_id}') {graph_url}/users/{user_id}/chats $filter=chatType eq 'oneOnOne' and installedApps/any(a:a/teamsApp/id eq '{teams_app_id}') According to a Stack Overflow discussion (https://stackoverflow.com/questions/57496329/proactive-messaging-bot-in-teams-without-mentioning-the-bot-beforehand), this appears to be a known issue: calling this API triggers a conversation update event even though there were no actual updates, resulting in duplicate events and duplicate welcome messages. Questions: What is the official/recommended way to handle known issue: calling this API triggers a conversation update event? Whats the recommended way to read personal chat history of a user? Should we be using a different approach for this app validation requirement? Any guidance or pointers to official documentation would be greatly appreciated!
Would Microsoft Teams SDK for Python (Preview) affect marketplace submission
Hi, I need to know if it's possible to publish a custom teams app and get validated to have the app in marketplace for public if it's developed using Teams SDK with python which is mentioned as still in preview. Teams SDK is now generally available for JavaScript and C#, supports Python in developer preview https://learn.microsoft.com/en-us/microsoftteams/platform/bots/overview https://learn.microsoft.com/en-us/microsoftteams/platform/resources/dev-preview/developer-preview-intro?tabs=new-teams-client https://github.com/microsoft/teams.py Thank you!
The Next Chapter of Microsoft Teams in Virtualized Environments
Virtual Desktop Infrastructure (VDI) has long been a critical deployment model for Microsoft Teams, especially for organizations that rely on centralized desktops for security, compliance, and scale. Over the past six years, Microsoft has invested heavily in improving the Teams experience in VDI—listening to customer feedback, addressing operational pain points, and rethinking how collaboration workloads should run in virtualized environments. That journey has now reached an important milestone: the legacy WebRTC based VDI optimization is being retired, and the new VDI optimization — built on top of a new media engine— is becoming the standard going forward. In this post, I want to explain why Microsoft is making this change, what customers gain with the new architecture, what’s coming next, and how IT teams can track adoption and progress. Why Microsoft Is Deprecating WebRTC-based optimization The WebRTC-based optimization (“Citrix HDX Media optimized” or “AVD Media optimized”) was designed in an earlier era of Teams, relying on WebRTC stacks bundled with the Remote Desktop client / Citrix Workspace app to offload audio/video/screensharing processing from the virtual desktop to the endpoint. While this approach enabled media optimization for the most common scenarios, it also introduced architectural limitations that became more pronounced as Teams evolved. Based on years of customer feedback, support cases, and operational learnings, several challenges consistently surfaced: Feature gaps between native Teams and VDI Longer call setup times Limited diagnostics and observability, making troubleshooting difficult for IT Operational complexity, including version-dependency on external components (like VDI Clients or VDI Hosts) and frequent infrastructure alignment issues. As Microsoft modernized the Teams client itself, it became clear that continuing to invest in the WebRTC based model would slow innovation and prevent VDI from reaching parity with physical desktops. This led to a full re-architecture of Teams in VDI, resulting in the new optimization in Q4 2024 (colloquially referred to as VDI 2.0). With the new optimization now broadly adopted, Microsoft is transitioning WebRTC into a legacy state, with defined End of Support and End of Availability milestones for Windows-based VDI environments that run on Azure Virtual Desktops, Windows 365 and Citrix (and only for these). What exactly is going to happen This change applies only to Windows-based endpoints connecting to Citrix and Azure Virtual Desktop (AVD) / Windows 365 environments and does not affect macOS, Linux, mobile, HTML5, or ChromeOS. It does not apply to Omnissa. Separate announcements will be made for those as soon as they hit General Availability. As announced in the Message Center Post 1239928, there will be two subsequent milestones in the deprecation, following the same pattern you saw in the transition from Classic to New Teams: End of Support October 1 st , 2026: WebRTC-based optimization will continue to work, but it is no longer officially supported by Microsoft and Citrix when connecting from Windows endpoints. Two months before this milestone, users will see dismissible banners upon application launch time alerting about the upcoming change. End of Availability April 1 st , 2027: WebRTC stops working; the new optimization is enforced. If Teams fails to optimize, it will fall back to server-side rendering (i.e. all multimedia is processed on the virtual machine, degrading the user experience). Two months before this milestone, users see a modal dialogue window alerting about the upcoming change. If the reason for not being optimized with the new stack is that the plugin is not installed, users are instructed to download the plugin from Microsoft’s website. Optimization Policies related to the legacy optimization (such as in Citrix Studio ) no longer take effect. The Benefits of the new optimization In a nutshell, the new architecture is using the same media engine as the native Teams desktop client. This alignment fundamentally changes what’s possible in virtualized environments. Customers that have migrated frequently report: A plethora of new features (Gallery View 3x3 and 7x7, Hardware Acceleration, 1080p, QoS, Custom and organizational backgrounds, Noise Suppression, HID, Advanced telephony features such as QoS, Media Bypass, and Location Based Routing) (These depend on the user’s endpoint platform and Teams license) Can significantly reduce call setup times (“a game changer”) Better Monitoring and Supportability (Teams Admin Center and Call Quality Dashboard-CQD-, and richer telemetry and diagnostics aligned with native Teams) Because the new architecture decouples from the VDI infrastructure and kept evergreen, Teams avoids mismatches between client versions and media stacks, and can reliability at scale. Additionally, this enables IT teams to proactively identify issues, analyze trends, and reduce mean time to resolution—capabilities that were limited or unavailable before. QuickStart Checklist and Common Pitfalls This quick‑start helps IT admins move from the legacy WebRTC-based optimization to the SlimCore-based optimization while reducing risk and improving visibility. Quickstart Tools/Actions What to look for 1 - Baseline Your Environment Use Teams Admin Center, Call Quality Dashboard and PowerBI Optimized vs Unoptimized users with both WebRTC and SlimCore (a.k.a VDI 2.0). ‘Inactive’ users (i.e. optimization disabled) 2 - Validate Prerequisites Read the VDI Article CWA/Windows App versions, MSIX GPOs on the endpoint, Networking requirements on the branch office 3 - Enable new Optimization -Check VDI Policy -Enable Citrix custom Virtual channels -Deploy Plugins Powershell Policy, Citrix Studio VC Allow List (allow MSTEAMS, MSTEAM1, MSTEAM2) 4 - Verify at User Level VDI Status Indicator It should say “Teams is [AVD]/[Citrix] SlimCore Media optimized” 5 - Monitor adoption Teams Admin Center (TAC) and Call Quality Dashboard (CQD) Use Teams Admin Center → Meetings → Best Practice Configurations Identify users still unoptimized Export impacted users Track improvements in CQD: Call setup success rate Media quality Reliability trends 6 - Prepare for VDI 1.0 Retirement Internal Comms Communicate timelines to Helpdesk and end users 7 - Operational Readiness Check Internal training, monitoring ready -Helpdesk trained on: VDI Status Indicator Teams Admin Center + CQD -No remaining dependencies on WebRTC-specific policies -Monitoring reflects new architecture Pitfall What Admins Observe Root Cause Impact Recommended Fix 1. New Teams installed, but users are still on WebRTC Teams shows ‘Not optimized’ or “Citrix HDX Media optimized” • Virtual channels not allowed (Citrix) • Teams plugin not deployed on endpoint Users never activate SlimCore and remain on legacy WebRTC • Verify Citrix virtual channel allow list • Confirm plugin presence and correct version on endpoints Upgrade CWA to 2508 (this version can auto-install plugins) 2. SlimCore never downloads (MSIX blocked) Silent fallback with no clear error. Endpoint GPOs or security tools (AppLocker?) blocking MSIX installs SlimCore cannot stage/provision and never activates Explicitly allow SlimCore MSIX staging and registration in endpoint policies 3. No monitoring after pilot rollout Some users work fine, others regress Rollout assumed complete after pilot Hidden pockets of unoptimized users persist Regularly review Best Practice Configurations dashboard and CQD 4. Helpdesk still troubleshoots like VDI 1.0 Long investigations and escalations Legacy runbooks and outdated mental models Higher MTTR and unnecessary escalations Retrain support on: • VDI Status Indicator • Teams Admin Center diagnostics • CQD-first troubleshooting Best Practice Configurations Dashboard In early 2026, Microsoft introduced a Best Practice Configurations dashboard in the Teams Admin Center that specifically highlights VDI optimization compliance, allowing admins to: Identify users and locations running unoptimized or legacy configurations Export impacted user lists for targeted remediation Track progress as tenants move fully to the new optimization This tool provides a clear, actionable path to measure migration progress and ensure a consistent Teams experience across virtualized environments. So… What’s Coming Next Microsoft continues to expand support across platforms and ecosystems on top of the new architecture. Upcoming and recently announced roadmap items include: Omnissa Horizon support for Windows endpoints using SlimCore-based optimization, rolling out in late February/early March (Public Tech Preview) Amazon WorkSpaces support, released this month, enabling optimized Teams experiences in AWS Continued expansion across endpoint types, including macOS, as platform capabilities mature. This is currently in Tech Preview! These investments reinforce Microsoft’s commitment to making VDI a first-class citizen, regardless of hosting provider or infrastructure choice. Looking Ahead The transition from the legacy WebRTC to the new optimization is more than a deprecation—it’s a platform shift. By aligning Teams in VDI with the native client architecture, Microsoft is enabling faster innovation, better reliability, and a more consistent collaboration experience for users who depend on virtual desktops every day. If your organization has not yet completed the upgrade, now is the time to assess your environment, validate optimization status, and plan for the retirement of the legacy WebRTC based solution. For additional guidance, please check our public documentation and read our previous blog posts (here, here and here).
