Power Platform Community Forum Thread Details

Hi,

I'm trying to migrate Outlook Actionable Messages from EAT tokens to Microsoft Entra authentication and I'm running into a very strange issue.

My setup is as follows:

Actionable Message Provider registered in the Outlook Actionable Messages Dashboard

Provider status = Approved

Sender address matches the registered sender address

App Registration created in Microsoft Entra ID

Expose an API configured

Application ID URI configured

Scope created

Authorized Client Applications configured

Adaptive Card sent from Power Automate

Action endpoint uses a Power Automate "When an HTTP request is received" flow

Flow trigger is configured with Who can trigger the flow = Anyone

The behavior is extremely inconsistent:

Scenario 1 - No originator

If I send an Adaptive Card without an originator:

{
  "type": "AdaptiveCard",
  "version": "1.0",
  "body": [
    {
      "type": "TextBlock",
      "text": "Hello World"
    }
  ],
  "actions": [
    {
      "type": "Action.Http",
      "title": "Click me",
      "method": "POST",
      "url": "https://default311..."
    }
  ]
}

then:

Action.Http works
Request reaches Power Automate
Outlook generates a valid non-zero connectorSenderGuid

However, the card is only visible/rendered correctly for me and not for other users in the organization

Scenario 2 - Using the approved Provider Originator

If I add the Originator from my approved Actionable Message Provider:


{
  "type": "AdaptiveCard",
  "version": "1.0",
  "originator": "<Provider-ID>",
  ...
}

then:

The card is rendered correctly for other users in the organization
The Action.Http button stops working
The request never reaches my Power Automate flow
Outlook returns errors such as:
- "Unsupported token type"
- HTTP 403 Forbidden

Most importantly, in the Outlook diagnostics payload I always see:

"connectorSenderGuid":"00000000-0000-0000-0000-000000000000"

When originator isn't set via JSON then "connectorSenderGuid" is same as registered originator, otherwise guid is 00000.

My first Provider was created with:

Is this a Power Automate scenario? = No

I have now created a second Provider with:

Is this a Power Automate scenario? = Yes

and I'm waiting for approval to test whether that changes the behavior.

Has anyone encountered a similar issue?

Categories:

Building flows

Community site session details

Actionable Messages Outlook + Power automate

Scenario 1 - No originator

Scenario 2 - Using the approved Provider Originator

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Winners!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to the June Top 10 Community Leaders!

Leaderboard > Power Automate

Featured topics

Product updates

Community site session details

Actionable Messages Outlook + Power automate

Scenario 1 - No originator

Scenario 2 - Using the approved Provider Originator

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Winners!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to the June Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Power Automate

Featured topics

Product updates