Skip to content

Commit 393f8b2

Browse files
committed
update
1 parent 520e9c9 commit 393f8b2

File tree

3 files changed

+2
-1
lines changed

3 files changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,9 +70,10 @@ The infrastructure that supports the Azure OpenAI architecture needs to be consi
7070
Organizations consuming the service through the Microsoft public backbone should consider the following design elements:
7171

7272
1. The Generative AI Gateway should be deployed in manner that ensures it's available in the event of an Azure regional outage. If using APIM (Azure API Management), this can be done by deploying separate APIM instances in multiple regions or using the [multi-region gateway feature of APIM](/azure/api-management/api-management-howto-deploy-multi-region).
73+
7374
1. A public global server load balancer should be used to load balance across the multiple Generative AI Gateway instances in either an active/active or active/passive manner. [Azure FrontDoor](/azure/traffic-manager/traffic-manager-routing-methods) can be used to fulfill this role depending on the organization’s requirements.
7475

75-
:::image type="content" source="../how-to/media/disaster-recovery/scaling.jpg" alt-text="Provisioned scaling diagram." lightbox="../how-to/media/disaster-recovery/scaling.jpg":::
76+
:::image type="content" source="../how-to/media/disaster-recovery/scaling.png" alt-text="Provisioned scaling diagram." lightbox="../how-to/media/disaster-recovery/scaling.png":::
7677

7778
### Designing for consumption through the private networking
7879

Binary file not shown.
206 KB
Loading

0 commit comments

Comments
 (0)