Overview of migration guidance for Azure Germany

The articles in this section were created to help you migrate your workloads from Azure Germany to global Azure. Although the Azure migration center provides tools that help you migrate resources, some of the tools in the Azure migration center are useful only for migrations that occur in the same tenant or in the same region.

The two regions in Germany are entirely separate from global Azure. The clouds in global Azure and in Germany have their own, separate Azure Active Directory (Azure AD) instances. Because of this, Azure Germany tenants are separate from global Azure tenants. This article describes the migration tools that are available when you migrate between different tenants.

The guidance on identity / tenants is intended for Azure-only customers. If you use common Azure Active Directory (Azure AD) tenants for Azure and Microsoft 365 (or other Microsoft products), there are complexities in identity migration and you should first read the Migration phases actions and impacts for the Migration from Microsoft Cloud Deutschland. If you have questions, contact your account manager or Microsoft support.

Azure Cloud Solution Providers need to take additional steps to support customers during and after the transition to the new German datacenter region. Learn more about the additional steps.

Migration process

The process that you use to migrate a workload from Azure Germany to global Azure typically is similar to the process that's used to migrate applications to the cloud. The steps in the migration process are:

Assess

It's important to understand your organization's Azure Germany footprint by bringing together Azure account owners, subscription admins, tenant admins, and finance and accounting teams. The people who work in these roles can provide a complete picture of Azure usage for a large organization.

In the assessment stage, compile an inventory of resources:

• Each subscription admin and tenant admin should run a series of scripts to list resource groups, the resources in each resource group, and resource group deployment settings.
• Document dependencies across applications in Azure and with external systems.
• Document the count of each Azure resource and the amount of data that's associated with each instance you want to migrate.
• Ensure that application architecture documents are consistent with the Azure resources list.

At the end of this stage, you have:

• A complete list of Azure resources that are in use.
• A list of dependencies between resources.
• Information about the complexity of the migration effort.

Plan

In the planning stage, complete the following tasks:

• Use the output of the dependency analysis completed in the assessment stage to define related components. Consider migrating related components together in a migration package.
• (Optional) Use the migration as an opportunity to apply Gartner 5-R criteria and to optimize your workload.
• Determine the target environment in global Azure:
  1. Identify the target global Azure tenant (create one, if necessary).
  2. Create subscriptions.
  3. Choose which global Azure location you want to migrate.
  4. Execute test migration scenarios that match your architecture in Azure Germany with the architecture in global Azure.
• Determine the appropriate timeline and schedule for migration. Create a user acceptance test plan for each migration package.

Migrate

In the migration phase, use the tools, techniques, and recommendations that are discussed in the Azure Germany migration articles to create new resources in global Azure. Then, configure applications.

Validate

In the validation stage, complete the following tasks:

1. Perform user acceptance testing.
2. Ensure that applications are working as expected.
3. Sync the latest data to the target environment, if applicable.
4. Switch to a new application instance in global Azure.
5. Verify that the production environment is working as expected.
6. Decommission resources in Azure Germany.

Terms

These terms are used in the Azure Germany migration articles:

Source describes where you are migrating resources from (for example, Azure Germany):

• Source tenant name: The name of the tenant in Azure Germany (everything after @ in the account name). Tenant names in Azure Germany all end in microsoftazure.de.
• Source tenant ID: The ID of the tenant in Azure Germany. The tenant ID appears in the Azure portal when you move the mouse over the account name in the upper-right corner.
• Source subscription ID: The ID of the resource subscription in Azure Germany. You can have more than one subscription in the same tenant. Always make sure that you're using the correct subscription.
• Source region: Either Germany Central (germanycentral) or Germany Northeast (germanynortheast), depending on where the resource you want to migrate is located.

Target or destination describes where you are migrating resources to:

• Target tenant name: The name of the tenant in global Azure.
• Target tenant ID: The ID of the tenant in global Azure.
• Target subscription ID: The subscription ID for the resource in global Azure.
• Target region: You can use almost any region in global Azure. It's likely that you'll want to migrate your resources to West Europe (westeurope) or North Europe (northeurope).

It's a good idea to bookmark the source and target portals in your browser:

• The Azure Germany portal is at https://portal.microsoftazure.de/.
• The global Azure portal is at https://portal.azure.com/.

Next steps

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

• Compute
• Networking
• Storage
• Web
• Databases
• Analytics
• IoT
• Integration
• Identity
• Security
• Management tools
• Media