Outlook Actionable Messages – Action.Http fails in Outlook.com and some Microsoft 365 accounts (request never reaches server)

Hello,

We are currently implementing Outlook Actionable Messages (Adaptive Cards) for our product and are experiencing inconsistent behavior across different Outlook environments.

Our sender address ******@feebak.com has successfully completed Global Verification, and the approval is active in the Actionable Email Developer Dashboard.

However, we are encountering issues when users attempt to execute actions from the card.

Observed Behavior

1. Personal Outlook Accounts (Outlook.com / Hotmail / Live)

The Actionable Message renders correctly in the email.

When the user clicks the action button (Action.Http), Outlook displays the error:

“An error occurred. Please try again later.”

Our backend does not receive any HTTP request, which indicates the failure occurs inside Outlook / Microsoft services before the request is sent.

2. Microsoft 365 Business Accounts

Behavior differs depending on the Outlook client:

Outlook Web (OWA)

In some accounts, the Actionable Message card does not render at all.

Outlook Desktop App

The card renders correctly, but clicking the action button results in:

“Something went wrong. Please try again later.”

Again, no request reaches our server, suggesting the Action.Http operation is being blocked before execution.

Environment Details

Sender: ******@feebak.com

Global Verification: Completed and active

Action type: Action.Http

Action endpoint: Public HTTPS endpoint (reachable and tested independently)

The same card works correctly in one Microsoft 365 test mailbox, but fails in most personal Outlook accounts and some Microsoft 365 environments.

Questions

We would appreciate clarification on the following points:

Support for Consumer Outlook Accounts

Are Outlook Actionable Messages fully supported in Outlook.com / Hotmail / Live accounts?

  Even with **Global Verification**, are consumer accounts allowed to execute `Action.Http` actions?
  
  **Microsoft 365 Tenant Restrictions**
  
     Are there **tenant-level policies, security controls, or Outlook configurations** that could block:
     
           Rendering of actionable cards in **Outlook Web**
           
                 Execution of `Action.Http` in **Outlook Desktop**
                 
                 **Request Blocking Before Execution**
                 
                    If Outlook blocks the `Action.Http` request **before it is sent to the server**, how can developers **diagnose the reason for the failure**?
                    
                    **Fallback Mechanisms**
                    
                       Is there any supported way to provide a **fallback interaction** if `Action.Http` cannot execute?
                       
                          Can Outlook automatically **redirect to a fallback URL** or show a custom message?
                          

Additional Notes

The endpoint URL is public, HTTPS, and reachable.

When the action button is clicked in affected accounts, no request is logged on our server, confirming the request is blocked before reaching our backend.

Any guidance on limitations, configuration requirements, or troubleshooting steps for this scenario would be greatly appreciated.

Thank you for your support.

Best regards,

Mahi Al Akhnas