An Azure service that provides an integrated environment for bot development.
Outlook message extension: Bot Framework token signed with kid not published in Bot Framework JWKS (IDX10503)
We have a search-based message extension (Microsoft 365 Agents SDK, .NET) that works in Teams but fails in Outlook.
Every request coming from Outlook is rejected by our JWT validation with:
IDX10503: Signature validation failed. The token's kid is: 'k5iiiMdxvvjRcJoIV4VrgnAsTBM',
but did not match any keys in TokenValidationParameters or Configuration.
Setup
- Azure Bot with the Microsoft 365 channel enabled.
- Incoming tokens are validated with ASP.NET Core JwtBearer: issuer https://api.botframework.com, signing keys from https://login.botframework.com/v1/.well-known/openidconfiguration (the same approach as in the Agents SDK samples).
Outlook token (header and claims, signature and IDs removed)
{"alg":"RS256","kid":"k5iiiMdxvvjRcJoIV4VrgnAsTBM","x5t":"k5iiiMdxvvjRcJoIV4VrgnAsTBM","typ":"JWT"}
{"serviceurl":"https://smba.trafficmanager.net/teams","iss":"https://api.botframework.com",
"aud":"<bot app id>","nbf":...,"exp":... (10-minute lifetime)}
Teams token for the same bot (validates fine)
{"alg":"RS256","kid":"JV67QS90ZeDkAs9lBb1jMh5kbcs","x5t":"JV67QS90ZeDkAs9lBb1jMh5kbcs","typ":"JWT"}
{"serviceurl":"https://smba.trafficmanager.net/jp/<tenant id>/","iss":"https://api.botframework.com",
"aud":"<bot app id>","nbf":...,"exp":... (1-hour lifetime)}
What we checked
- kid k5iiiMdxvvjRcJoIV4VrgnAsTBM is not present in https://login.botframework.com/v1/.well-known/keys. Checked repeatedly over several days, including within a minute of the token being issued. The set has 222 keys, 75 of them endorsed for "outlook" and 71 for "m365extensions".
- It is also absent from the Entra JWKS (common, organizations, consumers) and from the botframework.com tenant keys.
- The Outlook kid has not changed for several days. The Teams kid rotates normally and is always present in the Bot Framework JWKS.
- The issue reproduces with two independent bot registrations. Outlook tokens for both bots are signed with the same kid.
- Outlook tokens differ from Teams tokens: 10-minute lifetime and a generic serviceurl (/teams) instead of a 1-hour lifetime and a regional, tenant-specific serviceurl.
Questions
- Which key should be used to validate Bot Framework tokens sent for Outlook message extensions (Microsoft 365 channel), and where is it published?
- If the token service for Outlook signs with a key that is missing from the Bot Framework JWKS, can this be forwarded to the Bot Service / Teams platform team?