Skip to content

Commit 5291f8c

Browse files
committed
add bcdr
1 parent d7c37bc commit 5291f8c

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

articles/ai-foundry/openai/how-to/business-continuity-disaster-recovery.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,18 @@ The additional benefit of this architecture is that it allows you to stack Stand
6161

6262
:::image type="content" source="../how-to/media/disaster-recovery/scaling.jpg" alt-text="Provisioned scaling diagram." lightbox="../how-to/media/disaster-recovery/scaling.jpg":::
6363

64+
## BCDR for agents
65+
66+
To support service resilience, the Agents 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.
67+
68+
1. As an Azure Standard customer, you provision and manage your own single-tenant CosmosDB account.
69+
1. All of the agent state is stored in your CosmosDB.
70+
1. Backup and recovery rely on CosmosDB’s native capabilities, which you control.
71+
1. If the primary region becomes unavailable, the agent will automatically become available in the secondary region by connecting to the same CosmosDB account.
72+
Since all history is preserved in CosmosDB, the agent can continue operation with minimal disruption.
73+
74+
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.
75+
6476

6577
## Supporting Infrastructure
6678

0 commit comments

Comments
 (0)