User Profile
Prasad_Das-MSFT
MicrosoftJoined Jul 01, 2021
User Widgets
Recent Discussions
Re: Add Teams Chat Member API call inexplicably Failing
Hey AutomatonSolutionsRDE , we completely understand your concern. We have raised a bug for this issue and highlighted to concerned engineering team. We will contact you once we get any update from engineering team or if we need more details. Thanks!Re: All Teams Bots Not Working At All
Hi DasunDaDev , thanks for raising your issue. If all your Teams bots stopped working at the same time (while the Web Channel still works and your endpoints are not being hit), this is very likely due to a Microsoft Teams platform/API outage or incident affecting the Teams channel specifically. What you should do: Check Microsoft 365 Service Health: Go to the Microsoft 365 Service Health Dashboard and look for any active incidents related to Microsoft Teams, Teams Bots, or Teams APIs. Check Microsoft Teams Developer Status: Visit Teams Developer Platform Status or Azure Bot Service status.Re: How to create an audio calling bot for the Marketplace?
Here’s a clear summary of the current (January 2026) best-practice approach for building an audio calling bot for Teams Marketplace that can be installed in multiple customer tenants: 1. Frameworks & Tools to Use Microsoft Bot Framework SDK Still supported for Teams bots, including calling/meeting bots. Use Bot Framework v4 with Node.js or C#. Microsoft Graph Communications API Use Microsoft Graph Comms SDK for call control, media access, and signaling. Required permissions: Calls.AccessMedia.All, Calls.Initiate.All, Calls.JoinGroupCall.All, etc. Azure Bot Service Host your bot in Azure Bot Service for scalability and compliance. Teams App Manifest Package your bot as a Teams app using the Teams App Manifest schema. Specify bot endpoints, permissions, and capabilities. 2. Multi-Tenant Support Bot Framework bots can be made multi-tenant by registering as a multi-tenant Azure AD app. In your Azure AD app registration: Set “Supported account types” to “Accounts in any organizational directory (Any Azure AD directory - Multitenant)”. Grant required Graph permissions (Calls.AccessMedia.All, etc.) as application permissions. When publishing to Teams Marketplace, your app must be multi-tenant and consentable by customer admins. 3. Packaging for Teams Marketplace App Manifest: Include your bot’s Azure AD app ID, endpoints, and required permissions. List the bot in the bots section of the manifest. Specify webApplicationInfo for SSO if needed. Permissions: Teams app manifest does not directly grant Graph permissions; those are handled via Azure AD app registration. Customers must grant admin consent for Graph permissions after installing your app. Marketplace Submission: Follow Microsoft Teams Store submission guidelines. Ensure your app passes validation for multi-tenant use and permissions. 4. Limitations & Notes Microsoft 365 Agents SDK is not GA until at least March 2026; do not use for production Marketplace bots yet. Graph Comms SDK is still the standard for calling bots. Azure Communication Services Call Automation does not support direct bot-to-Teams user calling for Marketplace bots as of now. App Manifest permissions: Only Azure AD app registration controls Graph permissions, not the Teams manifest. Thanks, Prasad Das ------------------------------------------------------------------------------------------ If the response is helpful, please click "**Mark as Best Response**" and like it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.Re: Unsupported card when using Outlook card sharing of card created with Workflows
Hi Someone-somewhere , thanks for raising your issue. Could you please provide more details or clarify the issue you are experiencing such as detailed description of the steps you took to encounter the issue? Are you using below option to send the card to Outlook after its posted by Workflow?Re: Issue with Teams RSC Permission TeamMember.Read.Group
RSC permissions only work for standard channels. To manage private/shared channel members, you must use broader Graph permissions with admin consent. This is a platform limitation, not a configuration issue. Why doesn’t ChannelMember.ReadWrite.Group work for private/shared channels? RSC permissions (like ChannelMember.ReadWrite.Group) are designed for standard (public) channels only. Private channels and shared channels have separate membership and stricter security boundaries. The RSC model does not grant bots/applications access to manage or read members of private/shared channels, even if the app is installed at the team level. The error messages you see are expected: For private channels, you need Directory-wide or Group-wide permissions (e.g., ChannelMember.ReadWrite.All, Group.ReadWrite.All), which are not RSC and require admin consent. For shared channels, the app must be installed in the specific channel, and even then, management is limited.Re: MS Teams Bot Applications – Major Message Delivery Delays
Hi Tatsiana1808 , thanks for raising your issue. Could you please refer this documentation and let us know if it helps? Manage a long-running operation - Bot Service | Microsoft Learn Also, it would be great if you share your bot and tenant details along with request id and timestamp of delays for further investigation.
