Deploying to Foundry

The demonstration program discussed (and used) in the previous blog posts ran entirely locally as a console application. This week I set out to migrate it to Foundry. To do so, I enlisted the help of Bruno Capuano and Jon Galloway, both of Microsoft, and, of course, Copilot, as documented in these videos (part 1 and part 2).

The change log is here. The architectural design can be found here. The complete demonstration solution is here.

The tl;dr is that we created projects for each of the four agents and deployed them individually to Foundry. The rest of the code stayed on the local machine. Each agent is independently deployed and each has its own managed compute and its own Entra ID, exposing an OpenAI-compatible /responses endpoint (as explained in the architectural design document).

The demonstration program will continue to evolve, but this marks a significant milestone… let’s call it version 3.0 (1.0 was LangChain/Python, 2.0 was the port to Microsoft Agent Framework/C#)

Note: The initial draft of this post was written by BlogWriter and then edited by Jesse Liberty
Illustrations by Copilot. Caution: LLMs make mistakes; this post is offered as is.

Unknown's avatar

About Jesse Liberty

Jesse Liberty has three decades of experience writing and delivering software projects and is the author of 2 dozen books and a couple dozen online courses. Liberty is a Senior AI Engineer at the University of Pittsburgh Medical Center, and was a Team Lead and Senior Software Engineer for various corporations, a Senior Technical Evangelist for Microsoft, a Distinguished Software Engineer for AT&T, a VP for Information Services for Citibank and a Software Architect for PBS. He is a 21 year Microsoft MVP.
This entry was posted in AI. Bookmark the permalink.