Azure Service Bus has released AzureRM.ServiceBus PowerShell Module 5.3.0. With this version you can now configure your Geo-paired namespaces for Geo-DisasterRecovery. The cmdlets let you use the Alias and pair your primary and secondary namespaces. You can then failover to your paired namespace specified in your configuration. To learn more about Geo-DR feature for Service Bus, refer to the Azure Service Bus Geo-DR article.

The following script describes the steps of how this can be done.

Pre-requisites

Before you begin, you'll need the following:

• An Azure subscription. For more information about obtaining a subscription, see purchase options, member offers, or free account.
• Azure PowerShell. For instructions, see Get started with Azure PowerShell cmdlets.

Copy the following cmdlets into a text or .ps1 file. Use Window + X to open PowerShell command prompt with Admin rights. You can also open the PowerShell ISE as Admin and run the following script,

#Step 1 – Login to your Azure subscription
  Login-AzureRmAccount

# Optional – you need this if you do not have Event Hubs module already installed
  Install-Module AzureRM.ServiceBus

#Step 2 – following parameters are used while creating the resources
 $location1 = “East US”
 $location2 = “West US”
 $resourceGroup = “servicebusgeodr_resourcegroup”
 $primarynamespace = “servicebus_primarynamespace1”
 $secondarynamespace = “servicebus_secondarynamespace1”
 $aliasname = “servicebusalias1”

#Step 3 - Create Resource Group
 New-AzureRmResourceGroup -Name $resourceGroup -Location $location1

#Step 4 - Create Service Bus primary namespace
 New-AzureRmServiceBusNamespace – ResourceGroup $resourceGroup -NamespaceName $primarynamespace -Location $location1 -SkuName Premium

#Step 5 - Create Service Bus secondary namespace
 New-AzureRmServiceBusNamespace – ResourceGroup $resourceGroup – NamespaceName $secondarynamespace -Location $location2 -SkuName Premium

#Step 6 – Create an alias and pairs the namespaces
  New-AzureRmSeriviceBusGeoDRConfiguration -ResourceGroupName $resourcegroup -Name $aliasname -Namespace $primarynamespace -Namespace $secondarynamespace

#Optional – you can obtain the alias details using this cmdlet
 Get-AzureRmServiceBusGeoDRConfiguration -ResourceGroup $resourcegroup -Name $aliasname -Namespace $primarynamespace

#Optional – you can break the pairing between the two namespaces if you desire to associate a different pairing. Break pair is initiated over primary only
 Set-AzureRmServiceBusGeoDRConfigurationBreakPair -ResourceGroup $resourcegroup -Name $aliasname -Namespace $primarynamespace

#Optional – create entities to test the meta data sync between primary and secondary namespaces
#Here we are creating a queue
 New-AzureRmServiceBusQueue -ResourceGroup $resourcegroup -Namespace $primarynamespace -Name “testqueue1” EnablePrartitioning $True

#Optional – check if the created queue was replicated
 Get-AzureRmServiceBusQueue -ResourceGroup $resourcegroup -Namespace $secondarynamespace -Name “testqueue1”

#Step 7 – Initiate a failover. This will break the pairing and alias will now point to the secondary namespace. Failover is initiated over secondary only
 Set-AzureRmServiceBusGeoDRConfigurationFailOver -ResourceGreoup $resourcegroup -Name $aliasname -Namespace $secondarynamespace

#Step 8 – Remove the Geo-pairing and its configuration. This cmdlet would delete the alias that is associated with the Geo-paired namespaces
# Deleting the alias would then break the pairing and at this point primary and secondary namespaces are no more in sync 
 Remove-AzureRmServiceBusGeoDRConfiguration -ResourceGroup $resourcegroup -Name $aliasname

#Optional – clean up the created resoucegroup
 Remove-AzureRmResourceGroup -Name $resourcegroup

Enjoy this new tooling capability for Service Bus and please leave us your valuable feedback and comments!