
Here some options:
Option 1 – Power Automate Flow wrapper (recommended)
Wrap the Foundry agent call in a Power Automate Flow using the Azure AI Agent Service REST API. The flow handles the call, parses the JSON, and returns typed output variables back to CS. This solves both problems: you get full variable control and nothing is displayed automatically.
Option 2 – Custom Connector
Same concept as above but via a Custom Connector in Power Platform. More reusable if you plan to call the Foundry agent from multiple topics/agents. Still requires handling the async run/polling pattern (run → polling → completed).
Option 3 – Check system variables
After the Agent node fires, inspect whether CS exposes anything via system variables (e.g. System.Activity or similar). Unlikely to be clean, but worth a quick check before building a full workaround.
Bottom line: The native Agent node isn't ready for complex workflows yet. Power Automate Flow is your best bet today — Microsoft will likely add output properties in a future update, but the gap is real right now.
Hope this helps!
Paolo
✅ Did this solve your issue? → Accept as Solution
👍 Partially helpful? → Click "Yes" on "Was this reply helpful?" or drop a Like!
Want more tips on Power Platform & AI? Follow me here:
🔗 LinkedIn: https://www.linkedin.com/in/paoloasnaghi/
▶️ YouTube: https://www.youtube.com/@BeyondThePlatforms
📸 Instagram: https://www.instagram.com/beyond_the_platforms/
🌐 Website: https://www.beyondtheplatforms.com/