Migrate integration resources to global Azure

  • Article

Important

Since August 2018, we have not been accepting new customers or deploying any new features and services into the original Microsoft Cloud Germany locations.

Based on the evolution in customers’ needs, we recently launched two new datacenter regions in Germany, offering customer data residency, full connectivity to Microsoft’s global cloud network, as well as market competitive pricing.

Additionally, on Sept 30th, 2020, we announced that the Microsoft Cloud Germany would be closing on October 29th, 2021. More details are available here: https://www.microsoft.com/cloud-platform/germany-cloud-regions.

Take advantage of the breadth of functionality, enterprise-grade security, and comprehensive features available in our new German datacenter regions by migrating today.

This article has information that can help you migrate Azure integration resources from Azure Germany to global Azure.

Service Bus

Azure Service Bus services don't have data export or import capabilities. To migrate Service Bus resources from Azure Germany to global Azure, you can export the resources as an Azure Resource Manager template. Then, adapt the exported template for global Azure and re-create the resources.

Note

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

Important

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

Note

We recommend that you use the Azure Az PowerShell module to interact with Azure. See Install Azure PowerShell to get started. To learn how to migrate to the Az PowerShell module, see Migrate Azure PowerShell from AzureRM to Az.

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

Keys

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-AzServiceBuskey cmdlet with the optional parameter -Keyvalue to accept the key as a string. The updated cmdlet is available in Azure PowerShell Az module.

Usage example

New-AzServiceBuskey -ResourceGroupName <resourcegroupname> -Namespace <namespace> -Name <name of Authorization rule> -RegenerateKey <PrimaryKey/SecondaryKey> -KeyValue <string - key value>

New-AzServiceBuskey -ResourceGroupName <resourcegroupname> -Namespace <namespace> -Queue <queuename> -Name <name of Authorization rule> -RegenerateKey <PrimaryKey/SecondaryKey> -KeyValue <string - key value>

New-AzServiceBuskey -ResourceGroupName <resourcegroupname> -Namespace <namespace> -Topic <topicname> -Name <name of Authorization rule> -RegenerateKey <PrimaryKey/SecondaryKey> -KeyValue <string - key value>

Note

You must update your applications to use a new connection string even if you preserve the keys. DNS host names are different in Azure Germany and global Azure.

Sample connection strings

Azure Germany

Endpoint=sb://myBFProdnamespaceName.**servicebus.cloudapi.de**/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=XXXXXXXXXXXXx=

Global Azure

Endpoint=sb://myProdnamespaceName.**servicebus.windows.net**/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=XXXXXXXXXXXXx=

For more information:

Azure Logic Apps

Azure Logic Apps isn't available in Azure Germany, but you can create scheduling jobs by using Azure Logic Apps in global Azure instead. Although previously available in Azure Germany, Azure Scheduler is fully retired since January 31, 2022.

For more information:

Next steps

Learn about tools, techniques, and recommendations for migrating resources in the following service categories: