Hi @Hayes3d ,
It seems that your permissions are satisfactory, and you have passed the Graph Explorer test.
From your configuration, it may be that the PowerApps button you use as a trigger has caused such problems.
When using the PowerApps button as a trigger, the context will change. The user info obtained in the Flow is the user who triggered the Flow(the user who clicks the PowerApps button), so the user info here changes dynamically. Maybe the current user does not have sufficient permissions to obtain the file.
Please check this similar thread:
https://powerusers.microsoft.com/t5/General-Power-Automate/Breaking-access-role-inheritance-error-with-access-denied/td-p/315972
You can try to use the Manual button as a trigger first, and then configure the fixed credentials in the HTTP action to see if similar issues still exist.
Best Regards,