Migrate management tool resources to global Azure

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.

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 management tools from Azure Germany to global Azure.

Traffic Manager

Azure Traffic Manager can help you complete a smooth migration. However, you can't migrate Traffic Manager profiles that you create in Azure Germany to global Azure. (During a migration, you migrate Traffic Manager endpoints to the target environment, so you need to update the Traffic Manager profile anyway.)

You can define additional endpoints in the target environment by using Traffic Manager while it's still running in the source environment. When Traffic Manager is running in the new environment, you can still define endpoints that you haven't yet migrated in the source environment. This scenario is known as the Blue-Green scenario. The scenario involves the following steps:

  1. Create a new Traffic Manager profile in global Azure.
  2. Define the endpoints in Azure Germany.
  3. Change your DNS CNAME record to the new Traffic Manager profile.
  4. Turn off the old Traffic Manager profile.
  5. Migrate and configure endpoints. For each endpoint in Azure Germany:
    1. Migrate the endpoint to global Azure.
    2. Change the Traffic Manager profile to use the new endpoint.

For more information:

Backup

You can't migrate Azure Backup jobs and snapshots from Azure Germany to global Azure.

For more information:

Scheduler

Azure Scheduler is being retired. To create scheduling jobs, you can use Azure Logic Apps in global Azure instead.

For more information:

Network Watcher

Migrating an Azure Network Watcher instance from Azure Germany to global Azure isn't supported at this time. We recommend that you create and configure a new Network Watcher instance in global Azure. Then, compare the results between the old and new environments.

For more information:

Site Recovery

You can't migrate your current Azure Site Recovery setup to global Azure. You must set up a new Site Recovery solution in global Azure.

For more information about Site Recovery and to learn how to migrate VMs from Azure Germany to global Azure, see How to use Site Recovery.

Refresh your knowledge by completing these step-by-step tutorials:

Azure policies

You can't directly migrate policies from Azure Germany to global Azure. During a migration, the scope of assigned policies usually changes. It's especially true when the subscription is different in the target environment, as it is in this scenario. However, you can preserve policy definitions and reuse them in global Azure.

In the Azure CLI, run the following command to list all policies in your current environment.

Note

Be sure to switch to the AzureGermanCloud environment in the Azure CLI before you run the following commands.

az policy definition list --query '[].{Type:policyType,Name:name}' --output table

Export only policies that have the PolicyType value Custom. Export policyRule to a file. The following example exports the custom policy "Allow Germany Central Only" (short version: allowgconly) to a file in the current folder:

az policy definition show --name allowgconly --output json --query policyRule > policy.json

Your export file will look similar to the following example:

{
  "if": {
    "not": {
      "equals": "germanycentral",
      "field": "location"
    }
  },
  "then": {
    "effect": "Deny"
  }
}

Next, switch to the global Azure environment. Modify the policy rule by editing the file. For example, change germanycentral to westeurope.

{
  "if": {
    "not": {
      "equals": "westeurope",
      "field": "location"
    }
  },
  "then": {
    "effect": "Deny"
  }
}

Create the new policy:

cat policy.json |az policy definition create --name "allowweonly" --rules @-

You now have a new policy named allowweonly. The policy allows only West Europe as the region.

Assign the policy to the scopes in your new environment as appropriate. You can document the old assignments in Azure Germany by running the following command:

az policy assignment list

For more information:

Next steps

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