Skip to content

Commit bc028e5

Browse files
committed
remove note about failover availability
1 parent f9bb104 commit bc028e5

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

articles/storage/common/storage-designing-ha-apps-with-ragrs.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: tamram
77

88
ms.service: storage
99
ms.topic: conceptual
10-
ms.date: 01/14/2020
10+
ms.date: 04/08/2020
1111
ms.author: tamram
1212
ms.reviewer: artek
1313
ms.subservice: common
@@ -44,9 +44,6 @@ Keep in mind these key points when designing your application for RA-GRS or RA-G
4444

4545
* If the primary region becomes unavailable, you can initiate an account failover. When you fail over to the secondary region, the DNS entries pointing to the primary region are changed to point to the secondary region. After the failover is complete, write access is restored for GRS and RA-GRS accounts. For more information, see [Disaster recovery and storage account failover](storage-disaster-recovery-guidance.md).
4646

47-
> [!NOTE]
48-
> Customer-managed account failover (preview) is not yet available in regions supporting GZRS/RA-GZRS, so customers cannot currently manage account failover events with GZRS and RA-GZRS accounts. During the preview, Microsoft will manage any failover events affecting GZRS/RA-GZRS accounts.
49-
5047
### Using eventually consistent data
5148

5249
The proposed solution assumes that it is acceptable to return potentially stale data to the calling application. Because data in the secondary region is eventually consistent, it is possible the primary region may become inaccessible before an update to the secondary region has finished replicating.

0 commit comments

Comments
 (0)