MS Teams SSO signin failure with resourcematch failed

[tharuds]

Discussion Type

Question

Discussion Content

Hi team,

I'm trying to implement single sign on for a simple bot app built using Teams SDK and I keep getting a 200 response with a sign in failure.

{
    "name": "signin/failure",
    "type": "invoke",
    "value": {
        "code": "resourcematchfailed",
        "message": "Resource match failed"
    }
}

I have checked the application ID URI, token exchange URL (in bot resource) and the manifest webApplicationInfo which matches the api://{azuread-client-id} going through the troubleshooting tips.

When I try to sign in from teams client the resource match failed keeps happening even if the troubleshooting checklist looks fine.
The Entra app is configured to support multiple entra ID accounts while the Azure bot resource is single tenant. I have also tried changing the Azure AD app supporting account types yet keep getting the same issue. I'm testing the bot app using the sandbox account created from the admin tenant that I used to configure azure resources, which has a different tenant id (domain - 250rr3.onmicrosoft.com).

I have also checked the jwt generated when testing the oauth connection (https://token.botframework.com/api/oauth/TestConnectionCallback) configured for the Azure bot resource and it works fine with graph endpoints.
Would be great to know what could be missing or if it could be a cache issue or an issue from the bot framework.

TIA

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐