Secure, enterprise-ready landing zone for deploying AI agent applications on Microsoft Foundry.
Note
GPT-RAG has evolved into Agent Landing Zone. Same project, new name and broader scope: infrastructure and application layers for enterprise agents on Azure.
Documentation: Agent Landing Zone docs. Old links such as aka.ms/gpt-rag redirect there.
Choose one of two options:
| Option | Guide | What you get |
|---|---|---|
| Full stack | Deploy full stack | Infrastructure, a chat UI and an orchestrator agent, with an optional ingestion Container App. |
| Infrastructure only | Deploy infra only | Provision the foundation with azd provision without deploying application images. |
The orchestrator agent runs in Microsoft Foundry by default, or in Azure Container Apps with the classic topology. Fresh environments use native Foundry IQ Blob ingestion without the ingestion Container App. Existing environments keep their ingestion selection. Native source ingestion does not provide chat attachment uploads. See ingestion selection.
To deploy your own application, select its app-definition.json before the first provision. See Custom applications and the examples in samples/custom-app.
Prerequisites, network-isolated deployment, and configuration are covered in the central documentation.
Component versions for this release are pinned in manifest.json.
| Component | Repository | Version |
|---|---|---|
| UI | Azure/agent-app-ui | see manifest.json |
| Orchestrator | Azure/agent-app-orchestrator | see manifest.json |
| Ingestion (optional) | Azure/agent-app-ingestion | see manifest.json |
The full documentation lives in the Agent Landing Zone section of the AI Landing Zones documentation site.
See CONTRIBUTING.md, SECURITY.md, and SUPPORT.md. Release history is in CHANGELOG.md.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos is subject to those third-party's policies.