Layots Logo
Cloud Computing

Azure Landing Zone Assessment — What to scope before your first workload migration

What to scope before your first workload migration for enterprise IT and procurement teams evaluating azure landing zone assessment.

Layots Editor
Layots Technologies
Share
Azure Landing Zone Assessment — What to scope before your first workload migration

Short answer: An Azure landing zone assessment decides the foundations your workloads will live on — identity, subscription structure, network topology, security baseline, governance policy, monitoring and cost controls — before the first server moves. Scope it around eight design areas, agree a naming and tagging standard, and confirm data residency and connectivity. Migrating first and fixing the foundation later is the most expensive sequence in cloud adoption.

Key takeaways

  • A landing zone is the pre-built environment that workloads land in: identity, network, policy, monitoring and cost guardrails.

  • The structure you choose on day one is difficult to change once production workloads sit inside it.

  • Decide subscription and management group topology before, not after, the first migration.

  • Tagging and naming standards are what make chargeback and cost control possible later.

  • Hybrid connectivity and data residency usually constrain the design more than the applications do.
  • What is an Azure landing zone?

    An Azure landing zone is a pre-configured environment with the platform services your workloads need, built to a repeatable pattern: management groups and subscriptions, identity and role assignments, network topology and connectivity, security baseline, governance policy, logging and monitoring, backup, and cost controls. Microsoft's Cloud Adoption Framework describes this as an enterprise-scale design, deployed through infrastructure as code so it can be rebuilt and extended consistently.

    The point is separation. Platform services are owned by a platform team; application teams receive their own subscriptions with guardrails already applied, so they can move fast without redesigning security for every workload.

    The design areas to assess

  • Identity and access — Key decisions: Entra ID tenant, hybrid identity, RBAC model, privileged access — Common mistake: Everyone an Owner on a shared subscription

  • Subscription topology — Key decisions: Management groups, subscription per environment or per workload — Common mistake: One subscription for everything

  • Network topology — Key decisions: Hub and spoke or Virtual WAN, address plan, firewall, DNS, private endpoints — Common mistake: Overlapping address space with on-premises

  • Security baseline — Key decisions: Defender for Cloud, encryption, Key Vault, secrets management — Common mistake: Security reviewed after go-live

  • Governance — Key decisions: Azure Policy, naming, tagging, allowed regions and SKUs — Common mistake: Policies written but never enforced

  • Management and monitoring — Key decisions: Log Analytics workspace design, alerting, patching, backup — Common mistake: Logs scattered across workspaces

  • Business continuity — Key decisions: Backup policy, recovery targets, region pairing — Common mistake: Recovery design assumed, not tested

  • Cost management — Key decisions: Budgets, tags, reservations, showback or chargeback — Common mistake: No tagging, so cost cannot be attributed
  • Identity comes first

    Decide how users will authenticate, how on-premises identity synchronises, and who gets which role at which scope. Use role-based access at resource group or subscription level rather than broad ownership, require multi-factor authentication for privileged roles, and separate the identity used for deployment pipelines from human administrators. If identity is wrong at the start, every access review afterwards becomes an archaeology exercise.

    Network and connectivity

    Plan the address space across on-premises and Azure before anything is deployed, including room for growth and for recovery regions. Then decide:

  • Hub and spoke with your own firewall and routing, or Virtual WAN for simpler multi-region and branch connectivity

  • How branches connect: VPN over internet, SD-WAN overlay, or private circuit. Hybrid Cloud Connectivity compares those options

  • Where DNS resolution lives for hybrid name resolution

  • Whether PaaS services are reachable only through private endpoints

  • Egress control: forced tunnelling, inspection, and what is allowed out to the internet
  • Governance, naming and tagging

    Agree a naming convention and a mandatory tag set before the first resource is created: environment, owner, cost centre, application, and data classification. Enforce them with Azure Policy rather than documentation, because an untagged resource created today becomes an unattributable cost next quarter. This is the single cheapest decision that makes later cloud cost optimisation possible.

    Data residency and DPDP considerations

    Decide which Azure regions you will use and record why. For many Indian businesses that means Central India and South India for primary and recovery, with a documented position on where data is stored, where it is processed and where backups live. Under India's Digital Personal Data Protection Act, you remain accountable for personal data processed in the cloud, so record the processing locations, retention periods and the deletion path in the landing zone design rather than discovering them during an audit.

    Workload discovery before migration

    The landing zone is the destination. The assessment should also cover what is moving:

  • Discovery of servers, applications, databases and their utilisation over a representative period.

  • Dependency mapping, so a migration wave does not break an undocumented integration.

  • Right-sizing based on measured usage rather than current on-premises specification.

  • Migration method per workload: rehost, replatform, refactor, replace or retire. For VMware estates, Azure VMware Solution is often the fastest path.

  • Licensing review, including hybrid benefit entitlements for Windows Server and SQL Server.

  • A costed estimate for the target state, compared honestly with the cost of staying put.

  • Wave planning with rollback criteria and business sign-off per wave.
  • Landing zone assessment checklist

  • Entra ID tenant structure and hybrid identity approach

  • RBAC model, privileged access policy and break-glass accounts

  • Management group hierarchy and subscription strategy

  • IP address plan across on-premises, Azure and recovery regions

  • Network topology, firewall, routing and DNS design

  • Private endpoint policy for PaaS services

  • Security baseline, encryption and key management

  • Azure Policy set, with naming and tagging enforced

  • Log Analytics workspace design and retention

  • Backup policy, recovery targets and region pairing

  • Budgets, cost alerts and chargeback model

  • Infrastructure-as-code approach and pipeline ownership

  • Data residency position and DPDP documentation

  • Workload inventory with dependencies and right-sizing

  • Migration wave plan with rollback criteria

  • Operating model after go-live: who runs what
  • Common mistakes

  • Migrating the first workload before the subscription and network design exists.

  • Overlapping IP ranges with the on-premises network, discovered at cutover.

  • Lifting and shifting at the current on-premises specification, then paying for idle capacity.

  • No tagging standard, so nobody can explain the monthly bill.

  • A single Log Analytics workspace decision made by default, then regretted at scale.

  • Treating backup and recovery as a later phase.

  • Building the landing zone by hand in the portal, so it cannot be rebuilt or audited.
  • Frequently asked questions

    What is the difference between a landing zone and a migration?
    The landing zone is the environment and its guardrails. The migration is the movement of workloads into it. Doing them in that order avoids retrofitting identity, network and policy later.

    How long does a landing zone assessment take?
    For a mid-sized estate, commonly two to four weeks including discovery, dependency mapping, design workshops and a costed target-state estimate.

    Do we need a landing zone for a small deployment?
    A scaled-down version, yes. Even two or three workloads benefit from a defined subscription structure, tagging, RBAC and monitoring. The effort is small now and large later.

    Which Azure region should we use?
    Usually the one closest to your users and compliant with your data residency position, paired with a second region for recovery. Record the reasoning, because auditors and customers will ask.

    Can we reuse our existing on-premises firewall policy?
    Partly. The intent carries over, but cloud-native controls, private endpoints and identity-based access replace a lot of traditional perimeter rules. Expect to redesign rather than copy.

    How do we control cost from day one?
    Mandatory tags, budgets with alerts per subscription, right-sizing based on measured usage, and a monthly review owned by a named person. Reservations and savings plans come after usage patterns are stable.

    Who should own the landing zone after go-live?
    A platform owner, either in your team or through a managed services partner, responsible for policy, identity, network and cost. Application teams own what runs inside their subscriptions.

    Scope your Azure landing zone with Layots

    Layots Technologies designs and deploys Azure landing zones for businesses in Chennai, Bangalore and Hyderabad: identity and governance design, hub-and-spoke or Virtual WAN networking, security baseline, infrastructure as code, workload discovery and dependency mapping, migration waves, and managed operations afterwards.

    Tell us your current estate and the first workloads you want to move. A solution architect reviews the requirement and comes back with a landing zone design and a costed migration plan, usually within one business day.

  • Book a 30-minute virtual meeting with a solution architect — request your free IT assessment

  • Call +91 99623 95939

  • WhatsApp the team for a quick requirement discussion
  • Related reading: Azure Migration Services in Chennai · Why Businesses Are Moving from On-Premises to Microsoft Azure · Cloud Cost Optimisation for Indian Businesses

    Ready to transform your IT?

    Speak with a Layots enterprise architect. Assessment, no obligation.

    Request IT Assessment →
    Free assessment

    Talk to Our Specialists

    Found this useful? Our architects can apply the same thinking to your environment.

    • A solution architect reviews your requirement
    • We respond, usually within one business day
    • You get a practical, costed recommendation

    Prefer to talk now?

    No obligation. By submitting, you agree to our Privacy Policy. We never sell your information.