How can I cross utilize agents or wrokflow between microsoft agent framework and new microsoft foundry?

[arunskrishnan99-ops]

How can I cross utilize agents or wrokflow between microsoft agent framework and new microsoft foundry? Microsoft foundry docuemnattion says it support agent fraemwork but not mentioned how.

[huimiu]

Hi @arunskrishnan99-ops, could you please share more details about your needs? And if you can provide the document you mentioned, that would be great.

[arunskrishnan99-ops]

@huimiu Please find the documentation link below.
https://learn.microsoft.com/en-us/azure/ai-foundry/agents/overview?view=foundry.

Also attached the screenshot for the reference. I just want to confirm that whether i can use the agents or workflows from any of the agentic frameworks (Langgraph, MAF, etc.) in new microsoft foundry other than a A2A agent or a hosted agent? Also want to understand, what is the exact meaning/logic for the highlighted part in the shared screenshot.

[huimiu]

Hey @arunskrishnan99-ops, sorry for the late reply. To answer your questions:

Can I use LangGraph / MAF / CrewAI agents in Azure AI Foundry without A2A or hosted agents?

A: Yes. You can build agents or workflows using LangGraph, LangChain, CrewAI, Semantic Kernel, or Microsoft Agent Framework (MAF) and run them outside Foundry Agent Service (for example in App Service, Container Apps, AKS, or locally), while still using:

• Foundry / Azure OpenAI models
• Foundry observability (tracing, logs, evaluation)
• MCP / OpenAPI tools
• Foundry security & governance

A2A and Foundry-hosted agents are optional, not required.

What does the “Development frameworks and toolkits” box actually mean?

A: It means Azure AI Foundry is framework‑agnostic and integrates with these ecosystems, not that all of them must run inside Foundry Agent Service.

Specifically:

• You can build with your preferred framework
• Use Foundry models, tools, observability, and safety
• Optionally deploy to Foundry Agent Service for managed hosting
• Optionally use A2A for cross‑agent / cross‑runtime collaboration

[github-actions]

Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking 'reopen issue' button below the comment box. We will get back to you as soon as possible.