Deploy a migration landing zone

Migration landing zone is a term used to describe an environment that has been provisioned and prepared to host workloads being migrated from an on-premises environment into Azure.

Deploy the first landing zone

Before you use the migration landing zone blueprint in the Cloud Adoption Framework, review the following assumptions, decisions, and implementation guidance. If this guidance aligns with the desired cloud adoption plan, the Migration landing zone blueprint can be deployed using the deployment steps.

Assumptions

This initial landing zone includes the following assumptions or constraints. If these assumptions align with your constraints, you can use the blueprint to create your first landing zone. The blueprint also can be extended to create a landing zone blueprint that meets your unique constraints.

  • Subscription limits: This adoption effort isn't expected to exceed subscription limits.
  • Compliance: No third-party compliance requirements are needed in this landing zone.
  • Architectural complexity: Architectural complexity doesn't require additional production subscriptions.
  • Shared services: There are no existing shared services in Azure that require this subscription to be treated like a spoke in a hub and spoke architecture.
  • Limited production scope: This landing zone could potentially host production workloads. However, it is not a suitable environment for sensitive data or mission-critical workloads.

If these assumptions align with your current adoption needs, then this blueprint might be a starting point for building your landing zone.

Decisions

The following decisions are represented in the landing zone blueprint.

Component Decisions Alternative approaches
Migration tools Azure Site Recovery will be deployed and an Azure Migrate project will be created. Migration tools decision guide
Logging and monitoring Operational Insights workspace and diagnostic storage account will be provisioned.
Network A virtual network will be created with subnets for gateway, firewall, jumpbox, and landing zone. Networking decisions
Identity It's assumed that the subscription is already associated with an Azure Active Directory instance. Identity management best practices
Policy This blueprint currently assumes that no Azure policies are to be applied.
Subscription design N/A - Designed for a single production subscription. Create initial subscriptions
Resource groups N/A - Designed for a single production subscription. Scale subscriptions
Management groups N/A - Designed for a single production subscription. Organize and manage subscriptions
Data N/A Choose the correct SQL Server option in Azure and Azure Data Store guidance
Storage N/A Azure Storage guidance
Naming and tagging standards N/A Naming and tagging best practices
Cost management N/A Tracking costs
Compute N/A Compute options

Customize or deploy a landing zone

Learn more and download a reference sample of the Migrate landing zone blueprint for deployment or customization from Azure Blueprint samples.

For guidance on customizations that should be made to this blueprint or the resulting landing zone, see the landing zone considerations.

Next steps

After deploying your first landing zone, you are ready to expand your landing zone