Skip to content

Commit 9a9617b

Browse files
committed
Fix blocking issue
1 parent 6f666ba commit 9a9617b

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/sap/workloads/high-availability-zones.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ manager: ericl
66
ms.service: sap-on-azure
77
ms.subservice: sap-vm-workloads
88
ms.topic: concept-article
9-
ms.date: 02/09/2026
9+
ms.date: 02/10/2026
1010
ms.author: juergent
1111
ms.custom:
1212
- references_regions
@@ -113,7 +113,7 @@ This deployment architecture is called active/active because you deploy your act
113113

114114
A simplified schema of an active/active deployment across two zones could look like this:
115115

116-
![The schema for an active-active SAP application deployment across two zones.](./media/sap-ha-availability-zones/active_active_zones_deployment.png)
116+
![Diagram that shows the schema for an active-active SAP application deployment across two zones.](./media/sap-ha-availability-zones/active_active_zones_deployment.png)
117117

118118
The following considerations apply for this configuration:
119119

@@ -139,7 +139,7 @@ If you can't find a configuration that mitigates the potential differences in SA
139139

140140
The basic layout of the architecture looks like this:
141141

142-
![The schema for an active-passive SAP application deployment across two zones.](./media/sap-ha-availability-zones/active_passive_zones_deployment.png)
142+
![Diagram that shows the schema for an active-passive SAP application deployment across two zones.](./media/sap-ha-availability-zones/active_passive_zones_deployment.png)
143143

144144
The following considerations apply for this configuration:
145145

0 commit comments

Comments
 (0)