Merge pull request #7296 from aahill/agents-bcdr

BCDR for Agents

Author: prmerger-automator[bot]

articles/ai-foundry/agents/overview.md

@@ -8,7 +8,7 @@ ms.author: aahi
 ms.service: azure-ai-foundry
 ms.subservice: azure-ai-foundry-agent-service
 ms.topic: overview
-ms.date: 06/25/2025
+ms.date: 09/26/2025
 ms.custom: azure-ai-agents
 ---
 
@@ -117,6 +117,20 @@ Start with the [environment setup](environment-setup.md) and [quickstart](quicks
 1. After you create a project, you can deploy a compatible model such as GPT-4o.
 1. When you have a deployed model, you can also start making API calls to the service using the SDKs.
 
+## Business Continuity and Disaster Recovery (BCDR) for Agents
+
+To support service resilience, the Azure AI Foundry Agent service relies on customer-provisioned Cosmos DB accounts. This ensures that your agent state can be preserved and recovered in the event of a regional outage.
+
+### Use your own Cosmos DB account
+
+* As an Azure Standard customer, you provision and manage your own single-tenant Cosmos DB account. All agent state is stored in your Cosmos DB.
+* Backup and recovery rely on Cosmos DB’s native capabilities, which you control.
+* If the primary region becomes unavailable, the agent will automatically become available in the secondary region by connecting to the same Cosmos DB account.
+* Since all history is preserved in Cosmos DB, the agent can continue operation with minimal disruption.
+
+### Current guidance
+
+We recommend customers provision and maintain their Cosmos DB account and ensure appropriate backup and recovery policies are configured. This ensures seamless continuity if the primary region becomes unavailable.
 
 ## Next steps