Power Platform Community Forum Thread Details

Dear Community Team,

I am facing the subjected issue in my flow. Initially the flow owner is other person, later we have created a shared mail and transferred ownership to this common mail id.

Later, only in the HOD approval we have this issue. Kindly review and provide your feedback to rectify this issue.



Forbidden. The request failed. Error code: 'ApprovalConnectionOwnerNotEnabledInGraph'. Error Message: 'The Approvals connection owner was found in Graph, but the account is not enabled. Object Id: 'b550e59e-8a1c-4edd-b5d4-cb35f753ced1''.

Thanks.

Surendar.S

Categories:

Using flows

Hi SS-25021017-0,
The error you’re encountering seems to be related to Microsoft Power Automate permissions of the account that owns the Approvals connection in your flow.
Here are a few things to consider:

Account Not Enabled: The error message indicates that the account tied to the Approvals connection isn't enabled in Microsoft Graph. This could happen if the account has been disabled or if there are permission issues.
Ownership Transfer: Since you've transferred the flow ownership to a shared mail ID, the original owner's permissions may not have updated properly, which can lead to issues with the Approvals connection.
Approval Connection Issues: The connection for approvals might still be linked to the previous owner's account rather than the new shared mail ID.

Suggested Steps to Resolve:

Check Account Status: Verify that the account (Object Id: 'b550e59e-8a1c-4edd-b5d4-cb35f753ced1') is enabled and active in Azure Active Directory. If it’s disabled, you’ll need to enable it.
Update Approvals Connection: Look into your Power Automate flow and check the connections being used. If the Approvals connection is still associated with the old owner’s account, it would be best to delete that connection and re-add it while logged in as the shared mail ID.
Permissions Review: Ensure that the shared mail ID has the necessary permissions to perform approval actions within the flow. Double-check the permissions set in Azure Active Directory.

If you need any further assistance or guidance with these steps, feel free to reach out!
Best,