Outlook Actionable Messages: valid signed Adaptive Card fails server-side extraction

Summary

Outlook on the web fails to extract an Outlook Actionable Messages signed Adaptive Card, even though the provider registration and JWS are valid.

This may be owned by the Outlook Actionable Messages service rather than the AdaptiveCards renderer. If so, please route it internally to the appropriate team.

Observed behavior

Outlook Actionable Messages debugger reports:

Processing: Error
Error happened on card extraction for <1331238890.5.1785393170415@sdp-graph>
EntityExtractionSuccess: false
Error: EntityDocument does not exist.
CardEnabledForMessage: false

The card does not render in Outlook on the web; only the ordinary HTML fallback message appears.

Validation completed

• Provider scope: Test Users; status: Approved; token type: AAD-OBO
• The sender and recipient exactly match the provider configured sender and test-user address.
• The signed-card JWT originator exactly matches the approved provider originator.
• All Action.Http and Action.OpenUrl targets use the provider registered HTTPS target domain.
• The email contains the documented application/AdaptiveCard+json script wrapper with a SignedAdaptiveCard payload.
• The JWS is RS256 and was independently verified against the public key registered in the provider dashboard.
• The decoded payload contains an Adaptive Card v1.0 and renders correctly in the Adaptive Cards Designer configured for Outlook Actionable Messages.

This therefore does not appear to be malformed card JSON, an invalid JWS signature, a sender/originator mismatch, an unapproved provider, or an unregistered target domain.

Related issue

This resembles #5049, which was closed as external to the AdaptiveCards repository. The difference here is that the message and its signature have been verified end-to-end against the currently approved provider registration.

Request

Could the Outlook Actionable Messages team confirm whether this is a known server-side extraction/stamping issue or advise what additional diagnostic data they need? I can provide the redacted EML, full debugger output, and provider-registration details through a private support channel.

No repository file or test is identified; start with the Outlook Actionable Messages debugger output, provider registration, signed-card JWS, and related issue #5049. Done would be confirmation that the failure is owned by the appropriate service team or clear diagnostic requirements for further investigation.