Increased Queue API Latency After Migrating Storage Account from GRS to RA-GRS

Question

Increased Queue API Latency After Migrating Storage Account from GRS to RA-GRS

Zhuomin Hao 0 Microsoft Employee

Hello Storage Account team,

We recently migrated a storage account (Account A) to a new storage account (Account B). After the migration, we observed higher latency, particularly for queue-related APIs (e.g., PutMessage / GetMessage), on Account B.

So far, the only configuration difference we have identified between the two accounts is the replication setting:

Account A: Geo-redundant storage (GRS)

Account B: Read-access geo-redundant storage (RA-GRS)

According to the documentation, write operations should be served from the primary region for both GRS and RA-GRS, and therefore no additional write latency is expected between the two replication options.

Given this, we would like to ask:

Could RA-GRS have any impact on Queue service write latency in practice?

Are there any known internal behaviors, throttling, replication side effects, or other factors we should investigate when seeing increased Queue latency after such a migration?

Any guidance or pointers on where to continue troubleshooting would be greatly appreciated.

Thank you for your help.

Vallepu Venkateswarlu 4,095 Reputation points Microsoft External Staff Moderator

2026-02-04T23:54:34.3133333+00:00

Hi @ Zhuomin Hao,

Welcome to Microsoft Q&A Platform.

Could RA-GRS have any impact on Queue service write latency in practice?

RA-GRS itself doesn’t add latency to queue write operations, so the slowdown is likely caused by other factors.

Enabling RA-GRS on Azure Queue Storage does not have a practical impact on write operation latency. Writes are committed in the primary region first, and the replication to the secondary region happens asynchronously, so the write operation is not delayed by the geo-replication process. The architecture is designed to ensure high availability and durability without affecting write performance.

Ref: Use geo-redundancy to design highly available applications and Reliability in Azure Queue Storage

Are there any known internal behaviors, throttling, replication side effects, or other factors we should investigate when seeing increased Queue latency after such a migration?

Please check that your app is using the primary endpoint, confirm the new account’s region and performance tier match the old one, review network/firewall rules, and monitor Azure Storage metrics for throttling or server delays.

Please "upvote" if the information helped you. This will help us and others in the community as well.

Your answer

Vallepu Venkateswarlu 4,095 Reputation points Microsoft External Staff Moderator

2026-02-04T23:54:34.3133333+00:00

Hi @ Zhuomin Hao,

Welcome to Microsoft Q&A Platform.

Could RA-GRS have any impact on Queue service write latency in practice?

RA-GRS itself doesn’t add latency to queue write operations, so the slowdown is likely caused by other factors.

Enabling RA-GRS on Azure Queue Storage does not have a practical impact on write operation latency. Writes are committed in the primary region first, and the replication to the secondary region happens asynchronously, so the write operation is not delayed by the geo-replication process. The architecture is designed to ensure high availability and durability without affecting write performance.

Ref: Use geo-redundancy to design highly available applications and Reliability in Azure Queue Storage

Are there any known internal behaviors, throttling, replication side effects, or other factors we should investigate when seeing increased Queue latency after such a migration?

Please check that your app is using the primary endpoint, confirm the new account’s region and performance tier match the old one, review network/firewall rules, and monitor Azure Storage metrics for throttling or server delays.

Please "upvote" if the information helped you. This will help us and others in the community as well.

Share via

Increased Queue API Latency After Migrating Storage Account from GRS to RA-GRS

Your answer