You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-foundry/agents/overview.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: aahill
7
7
ms.author: aahi
8
8
ms.service: azure-ai-agent-service
9
9
ms.topic: overview
10
-
ms.date: 06/25/2025
10
+
ms.date: 09/26/2025
11
11
ms.custom: azure-ai-agents
12
12
---
13
13
@@ -116,6 +116,20 @@ Start with the [environment setup](environment-setup.md) and [quickstart](quicks
116
116
1. After you create a project, you can deploy a compatible model such as GPT-4o.
117
117
1. When you have a deployed model, you can also start making API calls to the service using the SDKs.
118
118
119
+
## Business Continuity and Disaster Recovery (BCDR) for Agents
120
+
121
+
To support service resilience, the Azure AI Foundry Agent service relies on customer-provisioned CosmosDB accounts. This ensures that your agent state can be preserved and recovered in the event of a regional outage.
122
+
123
+
### Use your own CosmosDB account
124
+
125
+
* As an Azure Standard customer, you provision and manage your own single-tenant CosmosDB account. All agent state is stored in your CosmosDB.
126
+
* Backup and recovery rely on CosmosDB’s native capabilities, which you control.
127
+
* If the primary region becomes unavailable, the agent will automatically become available in the secondary region by connecting to the same CosmosDB account.
128
+
* Since all history is preserved in CosmosDB, the agent can continue operation with minimal disruption.
129
+
130
+
### Current guidance
131
+
132
+
We recommend customers provision and maintain their CosmosDB account and ensure appropriate backup and recovery policies are configured. This ensures seamless continuity if the primary region becomes unavailable.
0 commit comments