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
Clarification regarding the URL change for 0365 connectors and E.T.A for supporting MessageCards
Clarification regarding the URL change Hi , I noticed the shift from the old URL format to the new URL format for old Office 365 Connectors. After the transition to new URL format in O365 connectors it looks like this : New URL format for 0365 connectors : https://companyadmin.webhook.office.com/... In new MS teams workflows the URL format is this : https://prod-256.westus.logic.azure.com:443/workflows/... We want to differentiate between the O365 connector URLs and new MS Teams Workflow URLs currently if we observe the URLs we can see that for 0365 connectors we have webhook term in the URL and for new MS Teams Workflow URLswe have workflows term in the URL . So that we can use MessageCard or AdaptiveCard accordingly in the mean time for O365 connector and MS Teams Workflows respectively. Can we rely on this logic to differentiate between the O365 connector URLs and new MS Teams Workflow URLs . Will this pattern of using "webhook" for old connectors and "workflows" for new MS Teams Workflow URLs continue to be followed in the future, allowing us to differentiate between legacy and new integrations? Regarding the MessageCard support in new MS Teams Workflows In this https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ it is mentioned that We are currently developing a method for webhooks in the Workflow app to support the following scenarios and will share more details before March 30, 2025. Could you provide a specific ETA or date for when MessageCard support in the Workflow app will be fully available? We understand more details are expected by March 30, 2025, but we’re looking for a clearer timeline.
