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

Question

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

Abdulla Sabith 5

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,
Abdulla Sabith

0 comments

1 answer

Your answer

Answer 1

Actionable Messages with Action.Http are supported in both Microsoft 365 and consumer Outlook (Outlook.com/Hotmail/Live), but they depend on several prerequisites and can be blocked at multiple layers before the HTTP request is sent to the service.

From the provided information, only the following points are supported:

Tenant-level enablement for Microsoft 365 accounts
For Microsoft 365 tenants, Actionable Messages must be enabled at the organization level. If they are disabled, cards may not render or actions may not execute:
```
   Get-OrganizationConfig | ft ConnectorsActionableMessagesEnabled,SmtpActionableMessagesEnabled
```
Both ConnectorsActionableMessagesEnabled and SmtpActionableMessagesEnabled must be $true for users in that tenant to receive and act on Actionable Messages. If these are not enabled, symptoms can include:
- Card not rendering in Outlook on the web.
- Card rendering but actions not being processed.
Client-side issues in Outlook Desktop (rendering/execution)
Outlook Desktop relies on the Autodiscover V2 service to locate the Actions protocol endpoint used to process Actionable Messages. If Autodiscover V2 is disabled, the card may render incorrectly or actions may fail before any HTTP call is made to the external service. Outlook uses this GET request:
```
   https://outlook.office365.com/autodiscover/autodiscover.json/v1.0/<user email address>?protocol=actions
```
If this fails (for example, because Autodiscover V2 is disabled on the client), Outlook cannot connect to the actions protocol endpoint and Actionable Messages will not function correctly. To fix this on affected Windows clients:
1. If the computer is domain-joined and Autodiscover is controlled via Group Policy, ensure the Disable the Autodiscover V2 service option is not enabled in the Disable Autodiscover policy.
2. On the client, run regedit.
3. Navigate to: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover
4. Either set the DisableAutodiscoverV2Service DWORD to 0 or delete this value.
5. Delete Autodiscover cache files:
  - %LocalAppData%\Microsoft\Outlook\<any partial file name> - Autodiscover.xml
  - %LocalAppData%\Microsoft\Outlook\16\<any file name>.xml
  - %LocalAppData%\Microsoft\Outlook\16\<any file name>.json
6. Restart Outlook.
If Autodiscover V2 was disabled, this can explain why the card renders but Action.Http never reaches the backend.
Diagnosing failures before the HTTP request is sent
When Outlook blocks Action.Http before sending the request, the recommended diagnostic tool is the Actionable Messages Debugger for Outlook. This add-in:
- Adds a button in Outlook Desktop and Outlook on the web.
- Shows diagnostic and error information for the currently viewed message.
- Helps identify common causes of Actionable Message issues (including validation, policy, or client-side problems).
Installing and using this debugger is the primary supported way to see why an Actionable Message is not executing, even when no request reaches the service.
Known issues and client/feature limitations
- Users not on supported Outlook versions or using non-Outlook clients (for example, Mail.app) will receive a plain HTML email with links instead of an actionable card.
- Some Outlook experiences (e.g., certain mobile scenarios) may not yet fully support all Actionable Message behaviors; in those cases, the HTML fallback is used.
Fallback behavior and error reporting from the service
For Action.Http actions that do reach the service:
- On success, the service should return HTTP 200.
- On failure, the service should return an HTTP 4xx status and include a CARD-ACTION-STATUS HTTP header with a custom error message. Outlook will display this message to the user when the action fails.
This mechanism only applies once Outlook has sent the request. If Outlook blocks the action earlier (policy, validation, or client issues), the service cannot control the message shown to the user. There is no documented mechanism in the provided material for Outlook to automatically redirect to a custom fallback URL when Action.Http is blocked before execution. The supported fallback is the HTML content with links that users can click when the card or action is not available.
Additional troubleshooting guidance
- Verify that the affected Microsoft 365 tenants have ConnectorsActionableMessagesEnabled and SmtpActionableMessagesEnabled set to $true.
- On affected Outlook Desktop clients, verify Autodiscover V2 is not disabled and clear the Autodiscover cache as described above.
- Use the Actionable Messages Debugger in Outlook Desktop and Outlook on the web to inspect the problematic messages and obtain detailed diagnostics.

The context provided does not include further details about consumer (Outlook.com/Hotmail/Live) policy controls or additional tenant-level switches beyond the organization configuration flags above.

References: