Organization-approved Outlook Actionable Message only renders for Test User

Question

Organization-approved Outlook Actionable Message only renders for Test User

Eliana Eras 0

Hello,

I am sending Outlook Actionable Messages with Adaptive Cards from a Power Automate flow using the Office 365 Outlook “Send an email (V2)” action.

The provider configuration is:

Scope: Organization - Status: Approved - Token type: AAD-PFAT - Power Automate scenario: Yes - Sender address: The same account registered in the provider - Target domain: The Power Automate environment.api.powerplatform.com domain - Adaptive Card version: 1.0 - Action type: Action.Http - hideOriginalBody: true

The card payload uses the Provider ID (originator) from the approved Organization registration.

The card renders correctly for me, but I was previously included in a separate Test Users registration. Other internal users only see the fallback HTML. They tested directly in Outlook on the web. The same result occurs for multiple users.

I also sent a minimal Adaptive Card containing only two TextBlock elements, without Action.Http buttons, inputs, ToggleVisibility, or complex content. Other users still received only the fallback HTML. Therefore, the issue does not appear to be caused by the card layout or actions.

Exchange Online configuration was checked and all these values are enabled:

ConnectorsEnabled: True ConnectorsActionableMessagesEnabled: True SmtpActionableMessagesEnabled: True

The Organization registration was approved more than 24 hours ago. Message headers confirm that both working and non-working messages:

Are sent from the registered sender - Are internal Exchange Online messages - Come from the same Power Automate flow and version - Are delivered without spam filtering differences

Is there another activation, propagation, tenant configuration, or AAD-PFAT requirement for an Organization-scoped provider? Could the existence of a separate Test Users registration for the same solution affect the Organization registration?

Thank you.

0 comments

1 answer

Your answer

Answer 1

Hi Eliana,

Thank you for sharing the details of your situation and the troubleshooting you have already completed.

Based on the behavior described, Power Automate appears to be successfully delivering the messages. Since the Adaptive Card renders for your account but other internal recipients receive only the fallback HTML, even when you use a minimal card, the issue may be more closely related to the Outlook Actionable Messages provider registration, originator validation, or Organization-wide activation.

Here are some steps you can try:

1/ Verify the Provider ID used in the card

Open the Adaptive Card payload in your Power Automate flow and locate the originator property. Confirm that its value exactly matches the Provider ID shown in the approved Organization registration, rather than the Provider ID associated with the separate Test Users registration.
If these registrations have different Provider IDs, update the payload with the Organization Provider ID, save the flow, and send a new test message.

2/ Confirm the actual sender identity

Open one of the test messages in Outlook on the web, select More actions (…) > View > View message details, and review the From field in the message headers. Confirm that the sender address shown there exactly matches one of the sender addresses registered for the Organization provider.
If the flow uses a shared mailbox, Send As, or Send on behalf, verify that the actual sender identity in the headers is the registered address, not only the address displayed in the message.

3/ Run an isolated test

Create a new test flow using:

The registered sender account
The approved Organization Provider ID
A minimal Adaptive Card containing only TextBlock elements
No actions, inputs, or dynamic content

Send the message to an internal user who has never been included in the Test Users registration, then check the result directly in Outlook on the web. This can help rule out any cached configuration or reference to the previous registration in the existing flow.

For reference, you may find these articles helpful:

If the Organization Provider ID and sender identity are correct, but the minimal card still renders only for the Test User, the issue may require service-side investigation. In this case, I recommend asking your organization’s IT administrator to open a support ticket with Microsoft Support through the Microsoft 365 admin center, so the appropriate support team can review the configuration and advise on possible next steps.

When opening the ticket, please provide the relevant Provider IDs, affected sender and recipient addresses, test timestamps, Internet Message IDs, registration screenshots, and Exchange Online settings.

For detailed guidance on how to open a support ticket with Microsoft Support, please refer to: Get support - Microsoft 365 admin | Microsoft Learn

I hope this information is helpful. Should you have any further questions or need additional assistance, please feel free to share them in the comment below. I'm very happy to help.

I look forward to hearing your thoughts on this.

If the answer is helpful, please click 'Yes' and kindly upvote it.

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

Eliana Eras 0 Reputation points

2026-09-10T21:24:37.5666667+00:00

Thank you . I completed the independent-flow test. I created a completely new Power Automate flow with a manual trigger, the registered sender connection, the approved Organization Provider ID, and a minimal Adaptive Card version 1.0 containing only two TextBlock elements. The same message was delivered to multiple individual internal recipients. My mailbox renders the Adaptive Card, but the other recipients see only the fallback HTML. My account was previously included in the separate Test Users registration; the affected recipients were never Test Users. Therefore, the behavior is recipient-dependent even though the sender, payload, flow, Provider ID, and message content are the same. This appears to confirm that the Organization-scoped provider is not being applied to users outside the former Test Users registration. Could this please be escalated for service-side investigation of the Organization provider provisioning? [Moderator note: Personally Identifiable Information removed]
Chris-D 1,260 Reputation points Independent Advisor

2026-09-10T21:54:59.6366667+00:00

Hi Eliana,

Thank you for completing the independent-flow test and sharing the screenshot.

The screenshot confirms that the affected recipient received the fallback HTML instead of the Adaptive Card. Combined with your previous confirmation that the same behavior occurs in Outlook on the web, the independent test results suggest that the Organization-scoped registration may not be applying as expected and may require service-side review.

As this is a user-to-user forum, I cannot access the backend provisioning status or directly escalate the registration. If available, please use the Registration not working? option in the Actionable Messages Developer Dashboard, or ask your organization’s IT administrator to open a support ticket with Microsoft Support through the Microsoft 365 admin center.

When submitting the request, please include the relevant Provider IDs, test timestamps, Internet Message IDs, registration screenshots, and independent-flow test results through the private support channel.

In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support

I hope this helps clarify the next step. If there is anything else I can help with, feel free to reach out.