Fallback mechanism for Actionable Messages / Adaptive Cards not working in Personal Outlook and iOS

Hi Shibil C,

Thank you for posting your question in the Microsoft Q&A forum.

Based on my research, the Q&A Assist reply is directionally correct, but there are a few “gotchas” worth calling out so you can quickly validate why it works for some recipients/clients and not others.

First, Outlook Actionable Messages can be supported for Outlook.com mailboxes, but only when opened in a supported client. Microsoft states that actionable messages are available to mailboxes on Exchange Online or Outlook.com with a supported client.

At the same time, mobile client support has important developer constraints. While the support matrix shows Outlook for iOS as supported, Microsoft explicitly notes that (for developers) Outlook mobile supports Actionable Messages v1.4+ and Adaptive Cards v1.0 and below. If your card JSON targets a newer Adaptive Card version (e.g., 1.2/1.3/1.4) or uses elements outside Outlook’s supported subset, buttons may appear to do nothing or the experience may fall back. Also, actionable messages are not supported in Outlook on the web when accessed from a mobile browser, which can be mistaken for “mobile support” if users are opening Outlook.com/OWA via Safari/Chrome.

Second, regarding fallback / alternate experience: You can implement a practical fallback by always including a meaningful HTML body (for example, a “Complete this action on the web” link) so that users on unsupported clients still have a way to finish the workflow. Microsoft explicitly recommends keeping a good HTML body even if you plan to hide it, because the HTML body is the only thing unsupported email clients can display, and cards are not included when replying/forwarding (only the HTML body is).

One important detail: the Q&A Assist reply doesn’t explicitly mention that Outlook Actionable Messages provide an Outlook-specific property hideOriginalBody. When set to true, it hides the HTML body only in supported clients where the card renders, while leaving the HTML body available for unsupported clients (and for reply/forward). In other words, hideOriginalBody helps you separate the “card experience” vs. “HTML fallback experience” depending on client capability, but it is not a fallback mechanism by itself, you still need to author the HTML fallback content

Additional information about registration and scope (this is commonly overlooked and is especially relevant when recipients are “outside” your org):

• To send actionable messages beyond yourself, Microsoft indicates you must register using the Actionable Email Developer Dashboard and include the originator (provider ID) when sending to others, otherwise the card can be removed/not rendered.
• The dashboard scope matters: Organization scope is intended to enable actionable messages to users within your organization; Global scope is intended to enable for any Office 365 email user, and is subject to Microsoft’s approval process.

Because personal Outlook.com/Hotmail recipients are not “within your organization”, if your provider is only approved at Organization scope, it’s worth double‑checking whether your recipient scenario effectively falls “outside org” and whether your provider registration scope/approval aligns with that.

I hope the information above helpful.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".         

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

1. Support in personal Outlook accounts

Actionable Messages are available to all customer mailboxes on Exchange Online in Office 365 or Outlook.com with a supported client. This includes personal Outlook.com / Hotmail accounts, provided:

• The mailbox is on Outlook.com (consumer service), and
• The user is using a client listed as supporting actionable messages.

See the client support matrix below.

2. Support in Outlook for iOS

From the Outlook client support table:

• Outlook on iOS: Actionable messages supported? Yes*, Adaptive card supported? Yes*.
• For developers: Outlook on iOS supports Actionable Messages version 1.4 and above, and Adaptive Cards version 1.0 and below.

If actions are not working in Outlook for iOS, common causes include:

• Using Adaptive Cards features or versions not supported by Outlook (for example, elements or actions beyond Adaptive Cards 1.0, or Outlook-unsupported elements such as Action.Submit).
• Using Outlook-specific features that are only valid in the context of Actionable Messages and must follow the documented constraints (for example, Action.Http with an internet-accessible URL).

3. Fallback mechanisms / workarounds

The platform behavior when a client does not support actionable messages is:

• For users not on a required version of Outlook, or using another mail client, they receive an HTML email with links that take the user to the web portal (for example, Flow/Power Automate portal) to respond.

This is the primary, built‑in fallback: a non-interactive HTML experience with standard links.

Recommended practices:

• Always include clear HTML links in the email body that allow completing the action in a browser or web app.
• Ensure the target URLs are accessible from the internet (no localhost), which is also required for Action.Http actions.

4. Alternate experience (fallback link / web redirection)

Yes, an alternate experience can be provided by:

• Including standard HTML content in the email alongside the Adaptive Card, such as:
  • A “Complete this action on the web” link.
  • A link to a web form or application that performs the same operation as the card action.

When the client cannot render or execute the Adaptive Card actions, the user can still click these links in the HTML body.

Within the Adaptive Card itself for Outlook Actionable Messages:

• Use Action.Http for actions, ensuring the url is internet-accessible and that the service can handle the request.
• Avoid unsupported elements such as Action.Submit and Input.Time, which will not be displayed in Outlook Actionable Messages.

5. Configuration / registration for personal Outlook users

Actionable Messages must be enabled at the Microsoft 365 tenant level for users to receive them:

Get-OrganizationConfig | ft ConnectorsActionableMessagesEnabled,SmtpActionableMessagesEnabled

Both properties must be $true for actionable messages to work.

For personal Outlook.com users:

• No additional per-user registration is documented beyond the general Actionable Messages registration and configuration for the sending service.
• The service sending Actionable Messages must be registered and compliant with the Actionable Messages requirements (as covered in the training module on registration and security).

6. Cross‑client compatibility guidance

To maximize compatibility across Outlook.com, Microsoft 365, desktop, web, and mobile:

• Target Adaptive Cards 1.0 and Actionable Messages 1.4+ features that are explicitly supported by Outlook.
• Use Action.Http for actions; do not use Action.Submit or Input.Time in Outlook Actionable Messages.
• Ensure the action endpoint URLs are publicly reachable.
• Always include a non-card HTML fallback in the email with links to complete the action on the web.
• For users or clients where actionable messages are not supported, rely on the HTML + link experience as the fallback.

References:

• Designing Outlook Actionable Message cards with the Adaptive Card format
• Actionable messages in Outlook and Office 365 Groups
• Issues with flow approval emails in Outlook Desktop and Web
• Understand Actionable Messages in Outlook fundamentals