Unanswered

Standard Approval Errors

(3) Share

Report

Posted on by DG-17061532-0

Hello,

I am reaching out regarding an issue we are experiencing with our approval flow that sends out standard approvals via Outlook emails. While the flow has been functioning well previously, we have recently encountered a problem where approvers receive an error message stating, "The remote endpoint returned an error (HTTP '403'). Please try again later."

Interestingly, even though the approvers can still approve the items directly through Power Automate, the error prevents them from doing so via Outlook. I've double-checked all permissions from SharePoint and Power Automate, and they are set up correctly, so I'm puzzled as to what might be causing this issue.

Could this be related to tenant permissions for Outlook? I would greatly appreciate any insights or feedback you might have on how to resolve this issue so that approvers can seamlessly approve requests via Outlook once again.

Thank you for your assistance and support.

Categories:

Using connectors

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @DG-17061532-0

Hmm I have seen this with Guest accounts, not internal accounts as long as they have M/O365 license(s) and Power Automate Licenses

any chance licenses have lapsed, or people were mistakenly taking out of the environment (as in someone created a security group instead of leaving it open) and those people are NOT in the newly assigned security group for the environment?

Maybe some security group that was being used for the SharePoint site was accidentally removed... or they were from it.

Was this reply helpful? Yes No
DS-08071332-0 3 on at

Like (0)

Report
Copy link

Link copied!

I am facing the same issue with my approval flow. For some colleagues it works as usual, but some are getting the HTTP 403 Error message. All have the same license.

Was this reply helpful? Yes No
Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

hi @DG-17061532-0 @DS-08071332-0

Did you resolve this issue? If so can you share what you did?

I was also going to ask, if you could go into the Power Platform Administrator. Go to Users, find one of the persons having this issue, because this certainly seems like it would have been an Issue writing back to the tables, which would be a dataverse/power platform role issue.

Just curious if you resolved it?

Was this reply helpful? Yes No
devsam 19 on at

Like (0)

Report
Copy link

Link copied!

I was getting the same issue and here's how I fixed - I reconnected the connection and save the automation.

In my case, the automation was shared with me as a co-owner which I guess necessitated that I reconnect the connection.

Hopefully, this helps in your case

Was this reply helpful? Yes No