Skip to content

Commit 41c0f0e

Browse files
committed
remove border
1 parent 03d7df1 commit 41c0f0e

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/app-service/tutorial-multi-region-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ To complete this tutorial:
4242

4343
The following architecture diagram shows the infrastructure you create in this tutorial. It consists of two identical App Service apps in separate regions. The first web app is in the active region. It's the _primary_ app responsible for processing incoming traffic. The second app is in the _standby_ region and waits on the availability of the primary app. Azure Front Door attempts to route traffic to the primary web app. When the primary region is unavailable, traffic routes to the standby web. In the diagram, the dotted line represents traffic routing based on region status. Access restrictions are configured so block direct access to the apps from the internet.
4444

45-
:::image type="content" source="./media/tutorial-multi-region-app/multi-region-app-service.png" alt-text="Diagram that shows the architecture of a multi-region App Service.":::
45+
:::image type="content" source="./media/tutorial-multi-region-app/multi-region-app-service.png" border="false" alt-text="Diagram that shows the architecture of a multi-region App Service.":::
4646

4747
Azure provides various options for load balancing and traffic routing. Azure Front Door is selected for this tutorial because it involves internet-facing web apps hosted on Azure App Service deployed in multiple regions. If your configuration differs from the example in this tutorial, see [Choose a load balancing solution for your scenario](/azure/architecture/guide/technology-choices/load-balancing-overview#choose-a-load-balancing-solution-for-your-scenario).
4848

0 commit comments

Comments
 (0)