Migrate Integration Resources

This section contains information that you may find helpful as you migrate your Azure integration resources across Azure regions.

Service Bus

Azure Service Bus services don’t have data export or import capabilities. To migrate Service Bus resources across Azure regions, you can export the resources as an Azure Resource Manager template. Then, adapt the exported template for the target Azure region and re-create the resources.


Exporting a Resource Manager template doesn’t copy the data (for example, messages). Exporting a template only re-creates the metadata.


Change location, Azure Key Vault secrets, certificates, and other GUIDs to be consistent with the new region.

Service Bus metadata

The following Service Bus metadata elements are re-created when you export a Resource Manager template:

  • Namespaces
  • Queues
  • Topics
  • Subscriptions
  • Rules
  • Authorization rules


The preceding steps to export and re-create don’t copy the shared access signature keys that are associated with authorization rules. If you need to preserve the shared access signature keys, use the New-AzureRmServiceBuskey cmdlet with the optional parameter -Keyvalue to accept the key as a string. The updated cmdlet is available in the PowerShell Gallery release 6.4.0 (July 2018) or on GitHub.

Usage example

New-AzureRmServiceBuskey -ResourceGroupName <resourcegroupname> -Namespace <namespace> -Name <name of Authorization rule> -RegenerateKey <PrimaryKey/SecondaryKey> -KeyValue <string-keyvalue>
New-AzureRmServiceBuskey -ResourceGroupName <resourcegroupname> -Namespace <namespace> -Queue <queuename> -Name <name of Authorization rule> - RegenerateKey <PrimaryKey/SecondaryKey> -KeyValue <string-keyvalue>
New-AzureRmServiceBuskey -ResourceGroupName <resourcegroupname> -Namespace <namespace> -Topic <topicname> -Name <name of Authorization rule> - RegenerateKey <PrimaryKey/SecondaryKey> -KeyValue <string-keyvalue>


You must update your applications to use a new connection string even if you preserve the keys.

For more information:

Logic Apps

Azure Scheduler will retire on September 30, 2019. Use Logic Apps to create scheduling jobs in the target Azure region. For detailed steps on migrating from Scheduler to Logic Apps, see Migrate Azure Scheduler jobs to Azure Logic Apps.

For more information:

API Management

See API Management chapter of Migration Web Resources.