Unable to Trigger my Logic Apps Flow through AI Foundry Models

Question

Hi Team,

I have a issue connected with my AI Foundry Models.

My Requirement is to develop an Voice Based Agent, through Voice Live API connected to Logic Apps Flow.

1. Initially as a part of testing, of a chat based agent (Later Trying with Voice Based feature), I am getting the following error: I have taken HTTPS Trigger Link from my Logic Apps from Azure and passed it to my AI Foundry Agent through "Action". But I am unable get replies, but received attached error. The same model works well without the "Action" added to it.
2. Also, Once I developed any Voice Agent through Voice Live API, I am unable to save my progress, i.e., each and every time on my login, I am each and every time giving the instructions and Avatars. How can I save it, so that every time I don't need to give instructions and Avatar.

Please help me on these 2 issues.

Thanks in Advance!

Answer 1

Hello Ashwath Bala S,

Thank you for posting your question in the Microsoft Q&A forum. 

The integration between AI Foundry's Voice Live API and Azure Logic Apps presents two key issues: failed HTTPS triggers when using the "Action" feature and non-persistent agent configurations. For the Logic Apps problem, verify the POST endpoint accepts JSON payloads and check for CORS or authentication errors in the run history. The configuration persistence issue likely stems from unsaved session data explore AI Foundry's template export features or consider storing settings in Azure Cosmos DB. 

Testing the text-based functionality before implementing voice features helps isolate integration problems. Detailed error logs and network traces will clarify why Logic Apps requests fail when routed through AI Foundry. Meanwhile, saving agent instructions and avatars externally ensures they persist across sessions. 

Microsoft's Logic Apps troubleshooting guide and Cosmos DB documentation provide relevant solutions. Resolving these issues will create a stable foundation for the voice-based agent while improving usability through saved configurations. 

Some Microsoft reference documentation you may review:

https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-diagnosing-failures?tabs=consumption

https://learn.microsoft.com/en-us/azure/cosmos-db/

If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated.