Getting " Unable to reach app. Please try again." error when attempting to submit feedback via Teams

Hi Jay Shahi

Thanks for reaching out to Microsoft Q&A forum support

Based on your description, I understand that you're using a Microsoft Copilot App Studio bot within Teams to submit feedback using the new native feedback functionality. While reactions are successfully logged in Application Insights, the feedback itself is not recorded, and you're encountering the error message: "Unable to reach app. Please try again"

As far as I know, the issue you're experiencing is most likely related to a recent change in how authentication and app registration are handled for Copilot App Studio bots in Teams. Bots created in Copilot App Studio differ from traditional bot apps in that they rely on low-code configurations and Microsoft-hosted infrastructure. A common cause of this error is a misalignment between the bot’s authentication setup and the Teams environment, particularly if the bot’s Entra ID app registration is set to single-tenant or lacks proper Microsoft authentication configuration. Additionally, tenant-level policies such as disabling custom apps in preview can silently block bot responses, even if the bot previously worked as expected.

That said, from my perspective view, you can try the following workaround method to see of the issue still persists:

1. Go to https://copilotstudio.microsoft.com/, open your bot, and navigate to the Security tab. Ensure that “Authenticate with Microsoft” is enabled, then re-publish the bot.
2. In the Channels tab, verify that the App ID and environment URL are correctly configured for Teams.
3. Ask your Teams administrator to confirm that the policy “Let users interact with custom apps in preview” is enabled for your tenant.

Optionally, run /debug conversationid in Teams to verify whether the bot is reachable. If it fails to respond, this confirms a configuration or policy issue.

Due to the relatively complex nature of issues related to Teams Bot, please understand that the methods mentioned above are merely workaround solutions before seeking higher-level support.

If you have tried all of the above methods but the issue persists, and when run /debug conversationId - the bot still does not respond, please update the comment section so I can continue working with you to identify the problem and provide a solution. 

I am looking forward to hearing from you

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Hi. The authentication is running through Microsoft Entra and I republished just in case. I also checked with our sys admin to make sure the permissions have not changed, and this confirmed. I also ran /debug conversationid and I am getting a response. The bot is responding perfectly fine otherwise. The only time I get the error is when I try to submit the feedback via the thumbs up and thumbs down and enter the text in the modal that pops up.

I am still experiencing this issue at only the submission of the feedback.