What you need to know
A successful read from a geo-redundant secondary can combine changes that have not yet arrived in their original order.
Potentially affected
Applications using read-access geo-redundant Azure Storage secondary endpoints.
DSE recommendation
Define acceptable handling of stale or inconsistent related records before enabling secondary reads.
Source facts
Azure Storage asynchronously replicates primary-region transactions to the secondary. Replication is eventually consistent and does not guarantee that transactions appear there in their original order. Related records can therefore temporarily disagree even when each read succeeds.
A primary update can also succeed before an outage prevents it reaching the secondary, leaving a later secondary read stale. The secondary copy is read-only; redirecting reads does not make it a destination for update requests. Microsoft Learn.
Applicability
Review the application’s actual replication option, selected service and secondary-read path. Identify relationships between records that users expect to remain consistent, not only whether individual objects are readable.
DSE recommendation
DSE recommends agreeing with the application owner how to handle missing, stale or contradictory related records during secondary operation. Decide which views can be shown with a warning and which actions must wait. Keep the policy for writes explicit so a successful read is not presented as proof that normal transactional operation has resumed.
Verification
Use an approved test that creates identifiable related updates and exercises the secondary-read handling path. Validate the application’s response to an intentionally incomplete or inconsistent set of records without claiming to have forced a particular service replication order. Check user messaging and blocked or deferred updates independently. Preserve the known update sequence and observed results so the review distinguishes endpoint availability from application-level consistency.
Official references
Microsoft Learn: Use geo-redundancy to design highly available applications. Source retrieved September 9, 2026.
Review the official source
Use geo-redundancy to design highly available applications - Azure Storage | Microsoft Learn · Verified September 9, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE