What tool do you recommend for my Microsoft Foundry agent to reliably (that's key) store a data file and provide a download link?

Michael Barnett 40 Reputation points
2026-01-08T17:29:51+00:00

We have had problems using an OpenAPI tool in Microsoft Foundry to reliably (that's key) store a data file and provide a download link. Specifically, when multiple calls are made to the tool, some calls do not complete, return an 'in_progress' status, causing the agent to fabricate non-working download links. This occurs even with this system prompt (added to the existing prompts):

What do you recommend for a more robust tool and approach?

4. **Multiple Files - SEQUENTIAL CALLING REQUIRED**
   • **CRITICAL**: When generating multiple CSV files, you MUST call the SaveCSVFile function **ONE AT A TIME** in sequence
   • **DO NOT make concurrent/parallel function calls** - this causes timeout errors
   • **WAIT for each function call to complete successfully** before starting the next call
   • **Workflow for multiple files**:
     1. Call SaveCSVFile for first file
     2. Wait for response with status "success": true
     3. Store the download link from the response
     4. Only then call SaveCSVFile for second file
     5. Repeat until all files are generated
   • Present all valid download links together after all files are stored
   • If any individual call fails, report which file failed and provide the successful links for others
Azure AI Bot Service
Azure AI Bot Service

An Azure service that provides an integrated environment for bot development.


Answer accepted by question author
Anshika Varshney 15,620 Reputation points Microsoft External Staff Moderator
2026-01-08T18:25:33.7566667+00:00

Hi Michael Barnett,

If you’re working with Microsoft Foundry, you need to try this approach is to leverage the Foundry Tools catalog and related services that make building and extending AI agents easier. Here are some practical options:

1. Use Foundry Tools Catalog

  • Foundry provides a central hub of tools (including Model Context Protocol – MCP servers) that you can integrate into your agents for tasks like:
    • Data integration (connectors for SAP, Salesforce, HubSpot, etc.)
    • Multimodal capabilities (speech, vision, document intelligence)
    • Custom tool extensibility via APIs and Azure Logic Apps
  • You can also create a private tools catalog for organization-specific tools. Learn more about Foundry Tools

2. Foundry Agent Service

  • If your goal is orchestrating AI agents, Foundry Agent Service offers:
    • Pre-built connectors to 1,400+ enterprise systems
    • Secure orchestration and deployment of agents
    • Integration with frameworks like LangChain or Microsoft Agent Framework Details on Agent Service

3. SDK & Developer Tools

  • For code-first development:
    • Use the Foundry SDK (available in Python, Java, TypeScript, C#)
    • Integrate with Visual Studio, GitHub, and Copilot Studio for streamlined workflows Quickstart guide

4. Integration Patterns

  • Foundry supports:
    • Low-code connectors (Power Platform, Logic Apps)
    • Direct REST API calls for full control
    • API gateway mediation via Azure API Management for governance Integration guide

Start with the Foundry portal for quick prototyping and then scale using SDKs and orchestration services. This gives you flexibility to build declarative or code-first agents and integrate advanced tools as needed.

Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

Thankyou!

Was this answer helpful?


1 additional answer

Sort by: Most helpful
  1. Michael Barnett 40 Reputation points
    2026-01-12T15:23:33.1033333+00:00

    Thanks Anshika Varshney, those are the technologies we're using in the tool we prepared and, as further information, the problem we experienced was due to the agent ignoring the URL returned by the tool. The agent was changing the timestamp portion of blob names (likely rounding or reformatting?), then using the SAS tokens with the wrong blob names, causing "Signature did not match" errors. More tweaks to the system prompts fixed the issue.

    We are learning that robust agents result from extensive prompt adjustments.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.