Handle Teams Invoke `signin/failure`

[tracyboehrer]

Unclear repro steps. But guidance from Teams in the past has been:

The "Resource match failed" error usually means there's a mismatch between the resource you're trying to access and your Azure app registration or bot settings. Here are some things to check:

Make sure the Application ID URI in your Azure app registration matches exactly with the one used in your bot's OAuth connection. It should be in the format api://botid-{appid}.
Verify that the Token Exchange URL in your OAuth connection settings is set to https://token.botframework.com/.auth/web/redirect.
Ensure your Teams app manifest file includes the correct webApplicationInfo section. This section should have the id set to your Azure AD app ID and the resource set to your Application ID URI.
Check that the necessary permissions and scopes are granted in your Azure app registration. This includes permissions for Microsoft Graph and any other APIs your bot needs to access.
Ensure the redirect URI is correctly configured in your Azure app registration. For bots, this typically includes the URL where your bot is hosted, such as https://<your_ngrok_domain>/api/messages.
Verify that ngrok is running correctly and forwarding requests to your local bot. Ensure the ngrok URL is correctly set in your bot's configuration.

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

Activity.Value in this case is the same object as Microsoft.Agents.Models.Error

[MattB-msft]

Tagging for error link related docs.