Thank you for your response. I did check that area and all my connectors that I wanted to use the running user's credentials were setup correctly based on the screenshot you provided. Turns out there are 2 connectors (Excel for Business & Excel for OneDrive). I was using Excel for Business and when I tried to use Excel for OneDrive it was blocked by a DLP (working on that). However, I was able to confirm that everything except that connector was using the users connection when authenticating. It still showed my name on the bottom of each step when I viewed the results, but I can confirm it was not me. I think this is just a bug in Power Automate that needs to be addressed.
Example, a SQL connector was using the users credentials (via an connection ref) to authenticate to a server (which is what I expect). I was able to confirm this by having someone test this against a DB they don't have access to. The flow failed on that step as expected.
Either way, your answer was probably exactly what you would do in this case (thumbs up), but my issue was likely due to a bit of a wild goose chase around the way the flow represents the results in the UI and a Connector to Excel that might be deprecated for OneDrive.
