User Profile
Prasad_Das-MSFT
MicrosoftJoined Jul 01, 2021
User Widgets
Recent Discussions
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.Re: Deleting AutoAttendants and CallQueue
You cannot force-delete Auto Attendants or Call Queues in Microsoft Teams if they are still referenced by endpoints or other resources. The error "Can't remove the Auto Attendant. Auto Attendant is still referenced by Endpoints Ids" means there are still dependencies. Azure/Teams Best Practices: Ensure all resource accounts, endpoints, and references (including Calling IDs and assigned numbers) are fully removed or unassigned before deletion. Wait for Azure AD/Teams backend to sync changes; sometimes it takes several hours for references to clear. For Call Queues, ensure all settings (like minimum queue time) meet requirements before deletion. Recommended Steps: Double-check all resource accounts and endpoints are unassigned from the Auto Attendant/Call Queue. Remove any assigned phone numbers or Calling IDs. Wait for backend sync (up to 24 hours). Try deletion again via Teams Admin Center or PowerShell.Re: Failed-Delete Message: Initiator (8:orgid:**) is not allowed to delete message
Hi johnjohn-Peter, thanks for raising your issue. Are you trying to delete bot messages? If yes, could you please refer below documentation and lets us know if it helps? Manage messaging policies in Teams - Microsoft Teams | Microsoft Learn
