Skip to content

Commit 694cb1c

Browse files
ferantiverockittel
andauthored
topic (docs): [diagrams] reinstate diagrams (#59)
* add ai solution architecture diagram * add workflow details * remove old diagrams * Apply suggestions from code review --------- Co-authored-by: Chad Kittel <chad.kittel@gmail.com>
1 parent b45618b commit 694cb1c

10 files changed

+4105
-0
lines changed

README.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,20 @@ The implementation covers the following scenarios:
2929

3030
Azure AI Foundry hosts Azure AI Foundry Agent Service as a capability. Foundry Agent service's REST APIs are exposed as an AI Foundry private endpoint within the network, and the agents' all egress through a delegated subnet which is routed through Azure Firewall for any internet traffic. This architecture deploys the Foundry Agent Service with its dependencies hosted within your own Azure subscription. As such, this architecture includes an Azure Storage account, Azure AI Search instance, and an Azure Cosmos DB account specifically for the Foundry Agent Service to manage.
3131

32+
![Diagram that shows a baseline end-to-end chat architecture that uses Azure AI Foundry.](docs/media/baseline-azure-ai-foundry.svg)
33+
34+
*Download a [Visio file](docs/media/baseline-azure-ai-foundry.vsdx) of this architecture.*
35+
36+
#### Workflow
37+
38+
1. An application user interacts with a chat UI. The requests are routed through Azure Application Gateway. Azure Web Application Firewall inspects these requests before it forwards them to the back-end App Service.
39+
1. When the web application receives a user query or instruction, it invokes the purpose-built agent. The web application communicates with the agent via the Azure AI Agent SDK. The web application calls the agent over a private endpoint and authenticates to Azure AI Foundry by using its managed identity.
40+
1. The agent processes the user's request based on the instructions in its system prompt. To fulfill the user's intent, the agent uses a configured language model and connected tools and knowledge stores.
41+
1. The agent connects to the knowledge store (Azure AI Search) in the private network via a private endpoint.
42+
1. Requests to external knowledge stores or tools, such as Wikipedia or Bing, traverse Azure Firewall for inspection and egress policy enforcement.
43+
1. The agent connects to its configured language model and passes relevant context.
44+
1. Before the agent returns the response to the UI, it persists the request, the generated response, and a list of consulted knowledge stores into a dedicated memory database. This database maintains the complete conversation history, which enables context-aware interactions and allows users to resume conversations with the agent without losing prior context.
45+
3246
### Deploying an agent into Azure AI Foundry Agent service
3347

3448
Agents can be created via the Azure AI Foundry portal, [Azure AI Persistent Agents client library](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/ai/Azure.AI.Agents.Persistent), or the [REST API](https://learn.microsoft.com/rest/api/aifoundry/aiagents/). The creation and invocation of agents are a data plane operation. Since the data plane to Azure AI Foundry is private, all three of those are restricted to being executed from within a private network connected to the private endpoint of Azure AI Foundry.
-53.3 KB
Binary file not shown.

docs/media/baseline-azure-ai-foundry.svg

Lines changed: 4091 additions & 0 deletions
Loading
689 KB
Binary file not shown.
-110 KB
Binary file not shown.
-118 KB
Binary file not shown.
-147 KB
Binary file not shown.
-141 KB
Binary file not shown.
-73 KB
Binary file not shown.

docs/media/openai-end-to-end.vsdx

-1.56 MB
Binary file not shown.

0 commit comments

Comments
 (0)