From 1e743b332b7dc6b5b0f89bdc8321c584887a352e Mon Sep 17 00:00:00 2001 From: Tao Chen Date: Wed, 13 May 2026 17:40:23 -0700 Subject: [PATCH] Fix README --- .../foundry-hosted-agents/responses/10_foundry_memory/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/python/samples/04-hosting/foundry-hosted-agents/responses/10_foundry_memory/README.md b/python/samples/04-hosting/foundry-hosted-agents/responses/10_foundry_memory/README.md index b0c4d62e0d..8659521885 100644 --- a/python/samples/04-hosting/foundry-hosted-agents/responses/10_foundry_memory/README.md +++ b/python/samples/04-hosting/foundry-hosted-agents/responses/10_foundry_memory/README.md @@ -117,6 +117,6 @@ When deploying, make sure `MEMORY_STORE_NAME` and `FOUNDRY_MEMORY_SCOPE` are set azd env set MEMORY_STORE_NAME "agent_framework_memory" ``` -If these are not set, running `azd ai agent init -m ` will prompt you to enter them interactively. +If these are not set, running `azd ai agent init -m ` will prompt you to enter them interactively. The deployed agent's Managed Identity needs **Azure AI User** on the Foundry project to read and write memories at runtime. Make sure you have run `provision_memory_store.py` against the same Foundry project before deploying — otherwise the agent will fail on the first turn when it tries to read from a non-existent store.