User Profile
Sayali-MSFT
MicrosoftJoined 5 years ago
User Widgets
Recent Discussions
Re: Bot configuration config/fetch returns same channel ID when switching channels within same team
Hello rasharab, Thank you for your patience! We were able to reproduce the issue. We have reported this as a bug for further investigation. We will keep you updated as soon as we receive further information. Thank you for bringing this to our attention!Re: Users on iOS can't write to group chat with a bot
Hello Yannick_Malins , We are pleased to inform you that the bug has been fixed! The fix has been verified in the following versions: Mobile (iOS)Teams Version [7.20.77.2025203102/1113] Please verify on your end and confirm if everything is working as expected. If you encounter any further issues, feel free to reach out. Thank you for your patience!Re: Issue with Teams Tab App
Hello achebrol, Intermittent connectivity issues in a Teams tab app—especially when hosted on AKS—typically stem from network routing, DNS delays, or transient connectivity failures rather than actual app downtime. Because retries usually succeed, the app is likely healthy, but some requests fail to reach it. Troubleshooting should start with checking detailed error messages and network traces in Teams to identify whether the failure is due to DNS, TLS, or HTTP routing issues. Common causes include DNS resolution delays, certificate or TLS problems, ingress or load balancer instability, and client-side proxy or network constraints within Teams. To diagnose the issue, review AKS ingress and application logs, test DNS resolution, examine ingress health, verify SSL/TLS configuration, and use network tracing tools. Potential fixes include lowering DNS TTL, adjusting ingress timeouts, ensuring proper health probes, validating Teams manifest domain entries, and using Azure Front Door or Traffic Manager to improve reliability.Re: Issue with Teams Tab App
Hello achebrol,Thank you for bringing this issue to our attention. To assist you better, could you please provide the following details? Reproduction Steps: Please share the steps you took to encounter the issue. Documentation Links: Any specific documentation you followed that relates to your problem. Teams Client Version: What version of the Teams client are you using? Code Snippets: Relevant code snippets that illustrate the issue. Manifest Package: If applicable, please share the manifest package for your app. This information will help us better understand the situation and provide a more accurate response.Re: Bot creation failed
Hello Kamen, We have tested the scenario on both the Old and New Developer Portals, and it is working as expected from our end. https://github.com/user-attachments/assets/50e94b1b-bd44-4e24-ace3-6bdb65462104 https://github.com/user-attachments/assets/9f185254-7292-4b3b-986c-ee046527655d The portal gets stuck if it cannot create the bot registration or link it to an Azure AD app, often due to tenant restrictions, missing permissions, or backend service issues. Sometimes, the portal does not surface the actual error (often a 403 or service principal creation failure).Re: Call Event when one user calls another user so that Bot can be added to call
Hello debumodi1, When one user calls another directly (a peer-to-peer call) in Microsoft Teams, your compliance-recording bot won’t receive a notification or automatically join. That’s normal—this scenario is handled not by your bot, but by Microsoft's compliance recording architecture via certified third-party solutions. If you want all one-on-one calls between users to be recorded: You'll need a compliance recording solution, not just a media bot. This requires: Becoming a certified compliance-recording partner. Using the compliance recording APIs and policies. Configuring admin-driven settings to automatically route all P2P calls to your bot. This is why your bot isn’t getting P2P call events—it’s not registered as part of the compliance recording framework. Reference Document- 1.Bots for Teams Calls and Online Meeting - Teams | Microsoft Learn 2.Introduction to Microsoft Teams third-party compliance recording - Microsoft Teams | Microsoft LearnRe: Bot creation failed
Hello integrationsn, This error means the Teams Developer Portal is trying to create a bot registration (service principal) in your tenant, but the backing Azure AD application is not in your local tenant. Microsoft recently tightened tenant restrictions for bot creation. Previously, the Developer Portal allowed bot registrations even if the backing Azure AD app was not in the same tenant. This behavior has now changed — Microsoft requires the app to be created and registered within the same tenant where the bot is being deployed.Re: callRecord.id no longer matches call.callChainId — how to link live calls to call records?
Hello You're right—Microsoft Graph’s callRecord object doesn’t include the callChainId or correlationId, so there’s no direct way to link a live call to its recorded data using those fields. The callRecord only provides its own unique id, along with details like start and end times, organizer, participants, and a join link. Since callChainId isn’t stored under another name, the only option is to try matching live calls to call records by comparing properties like time, organizer, and participants. This approach isn’t guaranteed, and it's a known limitation in Microsoft Graph. Your feedback is important to us. Please rate us: 🤩 Excellent 🙂 Good 😐 Average 🙁 Needs Improvement 😠 PoorRe: how to achieve private stage view for custom team app in meeting
Hello VivekPenthota, Thank you for bringing this issue to our attention. Unfortunately, Teams does not currently support a private stage view in meetings. The “Share to stage” button is mandatory for broadcasting content, and there is no API or manifest setting to bypass the side panel and open a popout directly. --------------------------------------------------------------------------------------------------------------------- Thank you for your suggestion! To better achieve your requirements, we recommend submitting this feature request through the Teams Feedback Portal. This is the best way to ensure your idea is considered for future updates. We appreciate your input and encourage you to share any additional thoughts!Re: app.Context.channel.displayName not working
Hello MithunK2165 -We are pleased to inform you that the bug has been fixed! The fix has been verified in the following versions: Desktop-Microsoft Teams version 25261.500.3967.9466. Please verify on your end and confirm if everything is working as expected. If you encounter any further issues, feel free to reach out. Thank you for your patience!Re: callRecord.id no longer matches call.callChainId — how to link live calls to call records?
Hello Hello daraA, You’re correct: the behavior changed recently, and what used to work (matching call.callChainId from the live call to callRecord.id) no longer holds. Previously: callRecord.id often matched the callChainId from the live call object, so you could link them easily. Now: callRecord.id is its own unique identifier and does not equal callChainId or call.id. This is by design; the API team decoupled these IDs as part of recent updates to the callRecords API. Is there a stable property you can use? 1. callChainId still exists in both the live call and the call record, but it’s no longer the primary key. Instead, it’s now intended as a correlation identifier for related calls (e.g., transfers, consults, or meetings with multiple legs). 2. The callRecord resource includes id (unique per record) and still exposes callChainId for grouping. So you can: Capture call.callChainId during the live call. When you receive a callRecord notification or query /communications/callRecords, filter or match on callChainId instead of id. Reference Document- 1.callRecord resource type - Microsoft Graph v1.0 | Microsoft Learn 2.Microsoft Graph Call Records API FAQ - Microsoft Graph | Microsoft Learn callChainId is not guaranteed to be globally unique—it’s unique per chain of related calls, not per individual call leg. If you only need to link “this live call session” to its record, and you know there’s no transfer/merge scenario, it’s safe enough. If you need absolute uniqueness, you’ll have to maintain your own mapping table keyed by call.id → callChainId → callRecord.id once the record arrives. Meeting URL (joinWebUrl) is unreliable for recurring meetings, as you noted.
Groups
