undefined

(0) Share

Report

Posted on by nirishetty

Hi All,

Many thanks in advance, I am not even a learner when it come to Flows. So, please excuse me on the question.

One of our user has created a Flow which triggers an email using a shared mailbox email address. The issue is, when the Flow was configured it was configured to use shareda@domain.com but later it was decided that instead of shareda sharedb@domain.com to be used. So, the issue now is until shareda@domain.com was configured, flow would trigger mails, but the moment it was changed to sharedb flow would fail to trigger mails.

Checked the permission of user on sharedb whether the user is having send permissions, who was triggering the flow and found that the SendAs permission was not delegated, but later delegated, but still, flow was failing to trigger mails.

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (1)

ScottShearer 25,270 Most Valuable Professional on at

Like (1)

Report

@nirishetty

Can you confirm that the account used for the connection has appropriate permissions to send email from the shared email address.

Also, can you post a screen shot of the configuration of your Send from a shared mailbox action.

Was this reply helpful? Yes No
nirishetty 15 on at

Like (0)

Report

Hi Scott,
Thanks for the reply, yes the user who is testing the flow and the user under whose a connection is created in that flow also has permissions, but still it fails. Below is what the error says:

{
"statusCode": 404,
"headers": {
"Pragma": "no-cache",
"x-ms-request-id": "5ce2df13-d4db-4483-bcd7-98c6e883c854",
"Strict-Transport-Security": "max-age=31536000; includeSubDomains",
"X-Content-Type-Options": "nosniff",
"X-Frame-Options": "DENY",
"Timing-Allow-Origin": "*",
"x-ms-apihub-cached-response": "false",
"Cache-Control": "no-store, no-cache",
"Date": "Mon, 11 Nov 2019 10:35:25 GMT",
"Set-Cookie": "ARRAffinity=d0f0007dfc4c17851c7abd70ceaf6c0aff65f4f34f6d9c955062f139659f0f03;Path=/;HttpOnly;Domain=office365-we.azconn-we-01.p.azurewebsites.net",
"Content-Length": "243",
"Content-Type": "application/json",
"Expires": "-1"
},
"body": {
"status": 404,
"message": "Specified folder not found.\r\nclientRequestId: cd473ec3-0c7c-4d26-8ff0-3badc9b7ba27\r\nserviceRequestId: 5ce2df13-d4db-4483-bcd7-98c6e883c854",
"source": "office365-we.azconn-we-01.p.azurewebsites.net"
}
}

Was this reply helpful? Yes No
Verified answer

nirishetty 15 on at

Like (0)

Report

Hi All,
Thanks for looking onto this, I have realised that when we use the card "Send mail from SHared mailbox" in Flows, the user who has actually established the connection should not only suppose to have Send permissions on the shared mailbox, but also needs to possess Full access. So, after delegating this permission Flow worked successfully, not only by the user who ran the test, but the delegated owners of the flow as well.

So, the owner of the flow has connections established in the Flow and he needs to have Full-access as well as Send-As for thw Flow to trigger mails.

I felt, Full-access is fine, but this will end up adding the shared mailbox on End-user's Outlook, what I actually did was delegated the access over Powershell with the attribute -Automapping to be set to $False i.e., -Automapping:$False.
This will of-course not add the shared mailbox automatically, but if user tries to configure then it will be successful.

Can Microsoft work on this? Probably some better options for the Flow to work in the backend?

Was this reply helpful? Yes No