User Profile
Sayali-MSFT
MicrosoftJoined Nov 01, 2021
User Widgets
Recent Discussions
Re: Get all AA/CQ with Resource Accounts
Hello JFM_12, To identify Auto Attendants (AA) and Call Queues (CQ) that do not have Resource Accounts assigned, you must correlate voice apps, resource accounts, and their associations using Microsoft Teams PowerShell. This involves retrieving all Auto Attendants, Call Queues, and Resource Accounts, mapping them using Get-CsOnlineApplicationInstanceAssociation, and exporting the results to identify any missing assignments. Since neither Microsoft Graph nor the Teams Admin Center currently provides this relationship in bulk, PowerShell remains the only supported method for performing this type of tenant-wide audit. You must use: Get-CsOnlineApplicationInstanceAssociation Reference Document- 1. Manage resource accounts for service numbers - Microsoft Teams | Microsoft Learn 2. PowerShell cmdlet reference for Auto attendants and Call queues - Microsoft Teams | Microsoft Learn 3. Get-CsOnlineApplicationInstanceAssociation (MicrosoftTeams) | Microsoft Learn 4. Get-CsAutoAttendant (MicrosoftTeams) | Microsoft LearnRe: Issue with Teams 'Add a User to Group Chat' API call?
Hello AutomatonSolutionsRDE, The request fails due to two issues: first, the @odata.type value was misspelled, causing Microsoft Graph to stop processing and return a misleading schema error. Second, an incorrect property was used instead of user@odata.bind. Correcting both issues resolves the problem. The proper request body must include the correct @odata.type, roles array, and the user@odata.bind reference to the target user. { "@odata.type": "#microsoft.graph.aadUserConversationMember", "roles": [], "user@odata.bind": "https://graph.microsoft.com/v1.0/users('USER_ID')" }Re: [iOS] Custom App Icon still renders as white square
Hello XianYunTang, We were able to reproduce the issue in the [Mobile (iOS)] Teams version [7.22.77.2025223902/1219]. 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: 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.
Groups
