@John Wong Yek Hon Thanks for reaching out. For the Premium Tier Service Bus, the Geo-Disaster Recovery feature is designed to ensure that the entire configuration of a namespace (entities, configuration, properties) is continuously replicated from a primary namespace to a secondary namespace with which it is paired. This allows you to initiate a once-only failover move from the primary to the secondary at any time
If you don't initiate a pairing in advance, you cannot failover to an ad-hoc added secondary namespace later on. The pairing must be set up in advance to ensure that the secondary namespace is continuously updated with the primary namespace's configuration. This setup is crucial for the failover process to work correctly
When you initiate a failover, the alias name for the namespace is re-pointed to the secondary namespace, ensuring that the connection string remains unchanged for the clients
However, it's important to note that the Geo-Disaster Recovery feature only replicates the metadata (queues, topics, subscriptions, filters) and does not replicate the messages held in queues or topic subscriptions
Therefore, any dynamically created topics and subscriptions in the primary namespace will be replicated to the secondary namespace if the pairing is set up in advance
If you have any more questions or need further clarification, feel free to ask
For more information please refer: https://learn.microsoft.com/en-us/answers/questions/936332/azure-servicebus-paired-namespace
https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-geo-dr