Service bus namespaces supports geo-replication. This feature is currently in preview and has many limitations that will not work for many customers with their current or planned implementation. I think it is still a useful rule to have and we have to adjust it over time when more functionality becomes available.
The geo-replication feature ensures that the metadata and data of a namespace are continuously replicated from a primary region to one or more secondary regions.
The secondaries act as hot stand-by regions and must be promoted to be used.
The following will be replicated:
Queues, topics, subscriptions, filters.
Data, which resides in the entities.
All state changes and property changes executed against the messages within a namespace.
Existing rule
No response
Suggested rule
Service bus namespaces supports geo-replication. This feature is currently in preview and has many limitations that will not work for many customers with their current or planned implementation. I think it is still a useful rule to have and we have to adjust it over time when more functionality becomes available.
The geo-replication feature ensures that the metadata and data of a namespace are continuously replicated from a primary region to one or more secondary regions.
The secondaries act as hot stand-by regions and must be promoted to be used.
The following will be replicated:
Pillar
Reliability
Additional context
https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-geo-replication