Bot in Teams Doesn't Recognize Existing Participants When Joining an Ongoing Call
Hello, I'm working on a bot for Microsoft Teams, and I've run into an issue with how the bot behaves when joining calls. Here is the specific problem: var statefulCall = await this.Client.Calls().AddAsync(joinParams, scenarioId).ConfigureAwait(false); If there are already participants in the call, the bot doesn’t recognize them as being present. It seems like it only detects participants who join after the bot is already in the call. I want the bot to: Join the call only after a new participant joins. Record that participant for a specific duration (this part is already implemented). Leave the call afterward. Questions: Is there a way to make the bot recognize participants already in the call when it joins late? Alternatively, is there a mechanism to have the bot trigger its join only when a new participant joins the call? I am currently monitoring the call state and participant changes using the event handlers, but they don’t seem to reflect participants already in the call at the time of joining. Any guidance or suggestions on how to resolve this would be greatly appreciated. Thank you!
Cannot delete unsolicited group chat from a group from which I removed myself
Since 2022 I have intermittently attempted to remove an unsolicited group chat message sent to me when I was added to a group chat I did not desire to join. During my most recent efforts I posted this thread to answers.microsoft.com. There a Microsoft Agent/Moderator recommended I post a discussion here, to "see if any of the Teams experts can come up with some ideas." I have attempted to delete this group chat message using the Teams Windows app, mobile app, and the Teams web app. None of these were successful. I have uninstalled the Teams Windows app from my laptop and have run Revo Uninstaller. But when I reinstall the Teams app, the group chat is still there. I am unfamiliar with what data having to do with my chats is synced with the cloud, but I suspect that is the source of this problem. But I can find no means of deleting any chats that are synced to the cloud. If there is a means to do so, I'd like to try that. In any case, I am open to any solutions those here at techcommunity.microsoft.com can offer. To sum up: In 2022 I was added by "Unknown User" to a group chat that I did not desire to be part of. I removed myself from the chat but immediately found I could not actually remove the chat from Teams. As you can see in the image below, there's nothing in the left-hand Chat pane that I can use to delete the chat. I can find no other link, menu, or other tool with the Teams UI to delete the chat. I have deleted the local cache at %userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams I have uninstalled and reinstalled the Teams application. I have uninstalled using Revo Uninstaller and then reinstalled the Teams application. In all instances, this group chat message remains.What’s New in Microsoft Teams | December 2024
The end of the calendar year is almost here, and Microsoft Ignite is now in the rear-view mirror. By the way, WOW, was it an exciting one! If you missed our last blog that listed everything for Teams that we announced at Ignite, here it is! There’s been a lot of buzz around features like the recently released “workplace presence”, that helps you connect with colleagues when you’re in the office. Although we announced so many powerful new features last month, there are still a few more coming! This will be a short blog, but we still have some updates that can make Teams an even more integral part of your workday. Read on for all the details, and I hope you have an excellent end to 2024! Meetings Take control during screensharing on web client This update enables meeting participants using the Teams web app to use the "take control" function to request control while another person is screen-sharing. Webinars and Town Halls Download Transcription and view RTMP-In 708 captions for Town hall and webinar Event organizers can now download transcripts for their town hall or webinar instances. This update also adds support for displaying RTMP-In 708 captions in transcription. RTMP-In 708 captions are a closed captioning standard that provides enhanced captioning capabilities, including improved compatibility with modern digital video formats Teams Rooms and Devices Whiteboard enhancements on Teams Rooms on Android You can use the whiteboard in a meeting, or when you’re collaborating offline with colleagues. When using the whiteboard outside of meetings, your content is retained even when a meeting begins. The whiteboard's contents are preserved and shared with remote participants instantly. You can also use the ‘Follow me’ function to guide participants as you navigate, and collaborative cursors let you see everyone working in real-time. Find certified for Teams devices for all types of spaces and uses ataka.ms/teamsdevices. Cisco Room Navigator The Cisco Room Navigator for panels is designed to be easy to deploy, scalable, and user-friendly in a modern workplace. It displays room availability, integrates with calendars, and allows for instant bookings. Featuring a 360° multicolor LED and a durable touch screen, it works seamlessly with the Microsoft Teams Panel app or other reservation systems. Learn more Yealink Room Panel E2 The Yealink Room Panel E2 is a compact touch screen designed for mounting outside meeting spaces. It displays meeting details and allows for on-the-spot reservations via Teams or Microsoft 365 calendar applications. With features like an RGB LED light bar, Wi-Fi, Bluetooth, ambient light and human presence sensors, as well as enhanced microphones and speakers, it meets the needs of modern workspaces. Learn more Maxhub XCore Kit Pro MAXHUB XCore Kit Pro is a Microsoft Teams Rooms conferencing solution intended for medium to large meeting rooms. It includes an 11.6-inch touch-screen control panel and a mini-PC with a 12th gen Intel Core i5 processor running Microsoft Teams Rooms. It supports 4K wired content sharing and dual-screen display capabilities, providing a comprehensive conferencing experience. Learn more Poly Studio X72 + TC10 The Poly Studio X72 all-in-one video bar is designed to optimize hybrid meetings, no matter the room size. With AI-enhanced video and audio technology, it offers the scalability and flexibility needed to join various cloud video calls effortlessly. The Poly TC10's 10-inch high-resolution touch display provides clear and accessible control options, making it easy to start and manage video calls. Learn more Poly Studio X72 Experience seamless hybrid meetings with the Poly Studio X72 video bar. Featuring advanced AI-enhanced video and audio technology, this versatile device ensures crystal-clear communication and effortless connectivity to virtually any cloud video call. Discover the scalability and flexibility that make the Poly Studio X72 the perfect addition to your meeting room setup. Learn more Poly Studio G62 The Poly Studio G62 conferencing system features easy setup, seamless integration, and customization options. It includes powerful collaboration tools, advanced audiovisual options, and a flexible setup. This system allows you to tailor large conference rooms to your specific needs. By connecting Poly peripherals and controllers, the Poly Studio G62 video conferencing system offers a modular solution designed for streamlined versatility. Learn more Poly Studio V72 The Poly Studio V72 Bar is designed to offer reliable, high-quality audiovisuals for your meeting room. Customize your PC-based or BYOD conference room setup effortlessly with this adaptable USB video bar. Integrate Poly peripherals with the Poly Studio V72 bar for consistent audiovisual performance that enhances your meetings. Learn moreTeams Presence Issue
For our Exchange On-prem Users we are seeing the below. We have a full hybrid exchange server setup. This used to work fine. Exchange 2016 CU23 build 15.1.2507.39. Only recent change was updating the Exchange server. Anyone experienced this issue? For some users (doesn’t seem to be affecting all users), their Outlook Out of Office status is not showing in their Teams status/Presence. Even after a few days. For all users who I have tested with if they have a meeting in their diary and the free/busy information of the meeting is set to “Show as Busy” this is not updating their Teams Presence to Busy/In a Meeting. In the Teams Calendar Connectivity Tester Testing if the specified user mailbox REST API endpoint is marked as discoverable by the Teams middle-tier service. The user mailbox REST API endpoint is marked as undiscoverable by the Teams middle-tier service. I can see in the rest api logs DispatchException=Microsoft.Exchange.Services.OData.ODataResponseException: The value 'serveraddress/api/v2.0/me/MailboxSettings/automaticRepliesSetting' of parameter 'Resource' is not supported. at Microsoft.Exchange.Services.OData.Model.SubscriptionFactory.GetBrokerSubscription(INotifiableResource notifiableResource Subscription template Boolean requiresBrokerProxy) at Microsoft.Exchange.Services.OData.Model.SubscriptionProvider.Create(Subscription template) at Microsoft.Exchange.Services.OData.Model.CreateSubscriptionCommand.InternalExecute() at Microsoft.Exchange.Services.OData.ODataCommand`2.<Execute>b__9_0() at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase`1.TrackLatency[TResult](Enum latencyMetadata Func`1 method) at Microsoft.Exchange.Services.OData.Web.RequestBroker.<>c__DisplayClass2_0.<Execute>b__0() at Microsoft.Exchange.Services.Diagnostics.ServicesPerformanceTracker.RunOperationWithTrackingADAndRpcPerformance(Action method Enum adCount Enum adLatency Enum rpcCount Enum rpcLatency) at Microsoft.Exchange.Services.OData.Web.RequestBroker.Execute(ODataRequest request) at Microsoft.Exchange.Services.OData.Web.RequestBroker.Dispatch(HttpContextBase httpContext AsyncCallback asyncCallback CheckpointTracker checkpointTracker ServiceModel serviceModel IComponentConfiguration`1 configuration);
call details with devce info and participant join,leave time
i am working on teams integration project when i run grap api it does not show data for device and participant timing details graph api for extacting data for call including { "call_id": "004998be-da70-40f6-999a-3c84484c98b1", "start_date_time": "2024-12-17T11:53:14.9897859Z", "end_date_time": "2024-12-17T12:16:55.6045446Z", "participants": [ { "participant_name": "Surbhi Yadav", "join_time": "Unknown", "leave_time": "Unknown" },Graph API: Meeting Attendance Details Organizer and Participant Join/Leave Times
Hi Teams Developer Community, I hope this message finds you well. I am currently working on fetching meeting attendance details, specifically the join and leave times of the organizer and participants, using the Microsoft Graph API. Could you please provide guidance on the following points: Endpoints to Use: What are the exact Graph API endpoints for obtaining meeting attendance details, including the join and leave times of all participants? Required Permissions: What permissions are necessary to access these attendance details? Are there any specific configurations needed in Azure AD? JSON Response Format: Below is the JSON format I am aiming to achieve. Could you confirm if this is correct and provide any additional fields or structures that might be useful? { "value": [ { "emailAddress": "abc", "totalAttendanceInSeconds":, "role": "Organizer", "identity": { "id": "", "displayName": ", "tenantId": }, "attendanceIntervals": [ { "joinDateTime": "2021-10-05T04:38:27.6027225Z", "leaveDateTime": "2021-10-05T04:43:49.7702391Z", "durationInSeconds": 322 } ] }, { "emailAddress": "abc", "totalAttendanceInSeconds": 314, "role": "Presenter", "identity": { "id": "57caaef9-5ed0-48d5-8862-e5abfa71b3e9", "displayName": "Lisa Adkins", "tenantId": null }, "attendanceIntervals": [ { "joinDateTime": "2021-10-04T23:13:43.3776519Z", "leaveDateTime": "2021-10-04T23:18:57.5639338Z", "durationInSeconds": 314 } ] } ] }
New Teams optimization for VDI now Generally Available in Citrix environment
Today Microsoft is pleased to announce that our collaboration with Citrix on the new Teams optimization architecture based on the Slimcore media engine has reached 100% availability. This is a major milestone for both companies, solidifying Microsoft Teams as a mission-critical application in Citrix DaaS and Citrix Virtual Apps and Desktops. Microsoft’s collaboration with Citrix goes back to over a decade, from the good ole’ days of the Lync Optimization Pack, evolving to Skype for Business and culminating into Teams. In this blog, I want to summarize all the info you will need as an Admin to shift gears in 2025 and start rolling out the new solution, bringing dozens of new features, improved performance, quality and reliability. I call this the 4-3-2-1 approach, a tactical and strategical breakdown of the deployment (and yes, I take this from soccer!) The 4 Components The new optimization (currently available on Windows endpoints only) relies on these components, which operate in unison to deliver the new user experience. Virtual Channel: our solution relies on 3 custom virtual channels hence it is critical you whitelist/allow them in Citrix Studio (machine-wide policy). This is a one-time configuration but easily missed by IT Admins. Plugin:the brains behind the operation – this is a small DLL (220 KB) that is installed on the same folder as CWA and is responsible for the client-side virtual channel establishment and subsequent downloading of the new media engine, SlimCore. There are multiple ways you can deploy the plugin: CWA installer, Global App Config Service, Plugin Download Manager -ideal for BYOD- and even via Intune/SCCM. CheckCTX691425 for more info. New Teams:make sure you are on the latest version (24295.605.3225.8804, and client version 24110115722, as seen in Settings > About Teams). This is not only critical for the feature to work, but it will play a vital role in the future because the media engine (SlimCore) will beauto updated based on the version of Teams in the VDA SlimCore:the heart of the solution. This is essentially the same media engine that native Teams desktop client for Windows uses, carved out as a ~50 MB MSIX package and kept up to date by the plugin, without user or admin intervention. Whenever Teams is updated, SlimCore will get updated. The list is in increasing order of importance – once you take care of the Studio policy and plugins are deployed, you are halfway there. Plugins are not designed to be upgraded every month – Microsoft will make every effort to not modify them, and they are backwards and forward compatible with Teams and SlimCore versions. Having said that, there will be scenarios where a new plugin is needed (a new feature that required a modification, a security / CVE fix, or simply an end-of-support timeline reached for old plugins). If #1 and #2 are met, new Teams will try to open the virtual channel in the background, while you are still optimized with the old WebRTC stack (“CitrixHDX Media Optimized”, as seen inSettings>About Teams). If successful, it will instruct the Plugin to download (also in the background) a specific version of SlimCore from Microsoft’s public CDN. The next time the user restart Teams, it will be optimized with the new stack (“CitrixSlimcore Media Optimized, as seen inSettings>About Teams). The 3 Recommendations There are three main recommendationswe always make to VDI customers that are starting the rollout of the new optimization Update cadence of the components Policies Network It is imperative you craft an internal strategy/process that can keep Teams up to date – older versions are out of support after 90 days (clock starts ticking from the moment there is a newer version), and by extension so is SlimCore on the endpoint/thin clients. A healthy update cycle will guarantee you are getting all the fixes and improvements that Microsoft releases continuously, while also delivering the best reliability and performance. Both Teams and SlimCore are MSIX packages, hence governed by a certain set of GPOs/AppLocker/WDAC policies that allow/prohibit MSIX provisioning (seehere). A single Teams Admin Center PowerShell policy can enable/disable the new optimization for your entire ORG, so you can then target specific user groups progressively. Lastly, make sure you have a conversation with your Networking team about the new solution, the importance of allowing UDP traffic and direct egress at the branch office. We laid out the IP requirementshere – and tell them you come bearing gifts: Quality of Service can now be applied to Teams traffic at the endpoint/thin client based on UDP source ports. The 2 Systems After you start the rollout, it is time to focus on the progression. Monitoring and Preventive Maintenance Reactive Maintenance A balanced approach, combining both preventive and reactive strategies, ensures that VDI systems with Microsoft Teams run efficiently, security risks are minimized, and the organization can swiftly address any unexpected challenges. In order to give Admins visibility, we have revamped Teams Admin Center,Call Quality Dashboard and PowerBI VDI templates to expose all the necessary information about ongoing calls, past meetings and trends/monthly reports. If you don’t have access to these portals, make sure you engage with your Teams Admin counterpart and get the proper RBAC that matches your profile. For example, with CQD you could create custom reports like this: "Show me Poor Appsharing sessions by Total Stream Count for Last Month AND where one of the participants was optimized with SlimCore”. We have documented extensively around troubleshooting, exposing information on a variety of logs, Event Viewer entries, known issues and (very soon, look for MC Post MC923415) in the Teams UI itself! The 1 Goal for the New Optimization A delightful User Experience is Microsoft’s and IT Admins’ number one goal. We have added dozens of new features (full list here) that almost close the gap between a VDI and native Teams. Our monitoring tools can give you unprecedented details on the meeting and endpoint performance (CPU, Wifi signal, Peripherals used, etc). Soon we'll be updating the Teams UI with a tooltip that indicates to the user if they are optimized with WebRTC or optimized with the new SlimCore stack. We made drastic improvements in call set up times, meeting join reliability, codecs and overall quality. An IT Admin that understands the 4 components, implements the 3 recommendations and adopts the 2 systems as part of their strategy is fully equipped to deliver the best Teams user experience possible in a virtual desktop. Happy holidays – from the entire VDI group here at Microsoft Teams!
Enhance meeting security with Teams Premium’s email verification for external meeting participants
We are thrilled to announce a new feature in Microsoft Teams that enhances the security and trustworthiness of your meetings through email verification for external participants joining Meetings. Meeting organizers can now require external participants to verify their email addresses with a verification code before joining the meeting. Once verified, participants will appear in the meeting with the ‘Email verified’ label, offering a more reliable way for organizers to manage external participants. This enhancement gives organizers greater confidence about who is joining their meetings. Who is this functionality intended for? When inviting an external participant to join Teams meetings, it is common that the participant may not have a Microsoft work, school, or personal account for sign-in. Currently, Teams supports users joining meetings as 'unverified' participants. If your organization does not want unverified participants to be able to join meetings , you will benefit from a new capability that allows for participants to join the meeting by verifying their email without signing up for a Teams account. This enables an organizer to verify all participants and provides the ability to track those who join your meetings after verifying their email addresses. How can your organization enable this? This capability is available to meeting organizers with a Teams Premium license. Admin controls: Admins managing tenant policies will have a new meeting policy labeled ‘Anonymous users can join Teams meetings after verifying by email code’ as shown in the screenshot below. This new meeting policy complements the existing meeting policy where tenant admins already have the control to enable ‘anonymous users to join the meeting unverified’. When admins can choose to turn on both the meeting policies for the users in the organizations, and leave the choice of requiring email verification to the meeting organizers via a new meeting option that will be available for them. Meeting Organizer Controls: When scheduling meetings, meeting organizers will now have a new meeting option labelled ‘Unverified participants can join the meeting’ that will be set to default on for the cases where the admin had enabled unverified joins as shown in the screen below: Organizers can choose to require participants to verify themselves by turning off this meeting option as shown in the screenshot below: Participant Experience: When organizers choose to disallow unverified participants from joining meetings, participants will be required to authenticate themselves upon attempting to join the meeting. If they possess a work account, school account, or personal Microsoft account, they can use these credentials for authentication. Participants without any of these Microsoft accounts will need to verify by entering their email address, which will receive a one-time passcode for verification. Participants who verify the same email address that the meeting invitation was sent to will be allowed to join the meeting directly if the 'lobby bypass' setting permits invited participants. Conversely, participants verifying with a different email address will be placed in the lobby and labeled as 'Email verified'. Based on the ‘Lobby Bypass’ settings, if the setting is set to allow invited participants to bypass the lobby, then email verified participants that were invited for the meeting will be allowed to bypass the lobby. For email verified participants that were not invited for the meeting, they will be placed in the lobby. The ‘email verified’ tag and the email address they entered for verification will be shown on the profile card of the participant in the lobby, meeting roster, and meeting chat. Why should your organization use this feature? Enhanced security and trust: By verifying the identity of external attendees, we reduce the risk of unauthorized access to meetings. Meeting organizers can trust external participants more as they now have the email address of the participants, which is not feasible for unverified joins. Improved engagement: Organizers can gather additional attendee information for follow-up and engagement, which can improve overall meeting effectiveness. Availability This feature will be available as part of Teams Premium and will be released for public preview in early 2025. Organizations can enhance the security and user experience for external participants joining Microsoft Teams Meetings. Stay tuned for more updates and detailed documentation on how to enable and use email verification for external participants in Teams Meetings.
Microsoft Teams Direct routing and external contacts
When external contacts are added or synced they are shown as telephone numbers instead of the name associated with it. Amongst others this is the case under quick dial. If you go to recent calls it's shown as the name. Tested on an xcover totally locked down, teams in a work profile on another android device. This is not the case on an iPhone SE 3 with company portal with teams. There under quick dials and contacts it's shown as the name of the external contacts. As you might imagine this is going to pose quite the hassle to our users that have to call with non organisation external contacts. Please advice :-)
