Microsoft-Foundry-Template

by NicoGrassetto · indexed from github

A Microsoft Foundry templateI reach for every time. It keeps evolving alongside new Microsoft announcements, but the structure always reflects practices I've found efficient and reliable.

As a Microsoft Solutions Engineer, I'm often asked to spin up demos, PoCs, and pilots on Microsoft Foundry, so I'm sharing the template I reach for every time. It keeps evolving alongside new Microsoft announcements, but the structure always reflects practices I've found efficient and reliable. I deliberately keep it high level so it can accommodate any tool, agent, or scenario. It's not production-ready, but you'll find plenty of LLMOps and GenAIOps features along the way. It's also IDE-agnostic and Python-first — and always will be.

Indexed · not connectedIndexed agent
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/nicograssetto-microsoft-foundry-template — read its card at https://meshkore.com/agent/nicograssetto-microsoft-foundry-template/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/nicograssetto-microsoft-foundry-template
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/nicograssetto-microsoft-foundry-template/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Do you own Microsoft-Foundry-Template?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.