LSI26004 - Adaptive Cards connector - actionable messages not working

Incident Report for TALXIS

Monitoring

Update summary:
We are currently testing and monitoring the behavior after approving the application. It seems that the change has not fully propagate yet into the Exchange Online. We will keep monitoring the behavior.

Next steps:
We will wait and report again with new findings.
Posted Jul 13, 2026 - 17:12 CEST

Update

Update summary:
We just got an update from Microsoft and our application TALXISAdaptiveCards is now approved. It needs an approval by a Global Administrator as well, please see the TALXIS documentation for details: https://docs.talxis.com/en/customizer-guide/required-application-consent/#aad-admin-consent

Follow this link to see the applications for approval in your tenant: https://outlook.cloud.microsoft/actionablemessage/oam/admin/aad-consent

Action needed:
Global Administrator has to approve the app at https://outlook.cloud.microsoft/actionablemessage/oam/admin/aad-consent, more details in TALXIS docs: https://docs.talxis.com/en/customizer-guide/required-application-consent/#aad-admin-consent

Feel free to reach to our team in case you need any help.
Posted Jul 13, 2026 - 13:48 CEST

Identified

Adaptive cards actions are not working with the message SOMETHING WENT WRONG. PLEASE TRY AGAIN LATER.

The bug was likely introduced by a change from Microsoft few days ago.

Root cause:
"Actionable Messages use Microsoft Entra ID–based token authentication. The transition from legacy (EAT) authentication completed on June 8, 2026. Legacy authentication is no longer supported."

Current status:
We implemented the change, we are currently waiting for Microsoft to approve the new connector. Customers will then need to provide AAD admin consent to the app registration for Adaptive Cards, app ID: be92c4a0-8512-4ee8-8292-34b4f1305ca1

Is there a workaround?:
Users can use the link for the adaptive card to work with the card instead, the actions are working there.

What's next?:
We will update the status page once we get an update from Microsoft. (it can take about 7-14 days)


We apologize for the inconvenience.
Posted Jul 09, 2026 - 12:39 CEST
This incident affects: TALXIS (Integration).