Office365 Outlook Send an Email (V2) - office35 is in the block list

(1) Share

Report

Posted on by dc7669

152

Hi,

I got the below error. I wonder how can I fixed it.

The strange thing is that when I used the same connection, same username on a new flow, it WORKED.

But, on the same Flow, when I created a New Step using Office365 Outlook Send an Email (V2) connector with the same username or other good username/password pairs, it will fail!

Where do I correct the "Token" expiration issue the message talks about?

Error from token exchange: Runtime call was blocked because connection has error status:
Enabled| Error, and office365 is in the block list.

Connection errors: [ParameterName: token, Error: Code: Unauthorized,
Message: 'Failed to refresh access token for service: aadcertificate.
Correlation Id=922d094d-ce9e-48c0-849a-2f516b2a412d, UTC TimeStamp=1/13/2022 4:35:06 PM,

Error: Failed to acquire token from AAD:
{"error":"invalid_grant",
"error_description":
"AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '2021-10-27T18:44:08.2941738Z' and the TokensValidFrom date (before which tokens are not valid) for this user is '2022-01-13T12:48:44.0000000Z'.\r\nTrace ID: 22d918b9-c35f-4096-b078-50ab9e52b400\r\nCorrelation ID: a0112549-df30-43f1-b680-d00c746366fd\r\nTimestamp: 2022-01-13 16:35:06Z","error_codes":[50173],"timestamp":"2022-01-13 16:35:06Z","trace_id":"22d918b9-c35f-4096-b078-50ab9e52b400","correlation_id":"a0112549-df30-43f1-b680-d00c746366fd","error_uri":"https://login.windows.net/error?code=50173"}']

Thanks.

Dchan

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (1)

dc7669 152 on at

Like (0)

Report

Hi,

Some additional information:
I wonder if the PowerApps trigger was causing the problem....

This is a Test I did for sending email. It worked. But, it was triggered by time.
dchan

Was this reply helpful? Yes No
Verified answer

dc7669 152 on at

Like (1)

Report

Hi all,

I think I just figured out WHY!
From previous experience, I think when the trigger is PowerApp, and when I use the Office 365 Outlook -Send an email (V2) connector, the sender will become the user who trigger PowerApp, regardless whose connection was used in the "Send an email (V2)" connector.
So, for this particular case, I think the user may be having password problems when she triggered the PowerApp. I have been working off that instance. Thus, I have been using bad credentials.
When I trigger this PowerAutomate myself, email was sent as it should be.
Another thing to note is that when I receive the email, it was from the person's connection I used for the Connector. This may be a "correction". I will need to monitor it to see if it is true.

So, I think my issue is solved!

dchan1

Was this reply helpful? Yes No