Azure Landing Zone Architect

Remote • Posted 24 minutes ago • Updated 24 minutes ago
Contract W2
8 Months
No Travel Required
Remote
Depends on Experience
Company Branding Image
Fitment

Dice Job Match Score™

🔢 Crunching numbers...

Job Details

Skills

  • Enterprise-scale Azure Landing Zone architecture and implementation
  • Management groups
  • subscriptions
  • and resource organization
  • Microsoft Cloud Adoption Framework (CAF) and Landing Zone design principles
  • initiatives
  • exemptions
  • Azure Policy
  • RBAC
  • Virtual Networks
  • subnets
  • VNet peering
  • Hub-and-spoke architecture
  • Azure Firewall
  • Network Security Groups
  • User-defined routes (UDRs)
  • network segmentation
  • ExpressRoute
  • VPN connectivity
  • Azure DNS
  • Private DNS Zones
  • private endpoints
  • Access Control
  • Analytics
  • Budget
  • Cloud Computing
  • C
  • Cloud Security
  • Customer Facing
  • DNS
  • Dragon NaturallySpeaking
  • Roadmaps
  • MSP
  • Microsoft Azure
  • Workflow
  • Terraform
  • Testing
  • Network Security
  • Microsoft
  • Onboarding
  • Encryption
  • DevOps
  • Data Collection
  • Gap Analysis
  • IP
  • GitHub

Summary

Job Title: Azure Landing Zone Assessment, Architecture, Implementation & Governance

Location: 100% Remote (Preferred TX candidates)

Interview Process: Video

Work Schedule: 100% Remote

Job Description:

1. Role Purpose

Lead the assessment, architecture, engineering, implementation, and technical delivery of an enterprise-scale Azure Landing Zone across the planned workstream.

This is a client-facing, hands-on technical leadership role responsible for evaluating the existing Azure environment, identifying infrastructure and governance gaps, developing the target-state Landing Zone architecture, and implementing the approved Azure platform foundation.

The individual will work closely with Customer cloud, network, security, infrastructure, and operations teams, as well as Azure engineers, to establish a secure, scalable, governed, and operationally sustainable Azure environment.

The role requires ownership of technical decisions, implementation planning, engineering guidance, platform configuration, validation, and delivery documentation.

2. Key Responsibilities

A. Azure Landing Zone Assessment

Conduct a comprehensive assessment of the existing Azure environment, including:

Azure tenants, management groups, and subscription hierarchy.

Existing resource groups, resources, and regional deployments.

Azure governance, security policies, and compliance controls.

Identity, RBAC, privileged access, and administrative boundaries.

Network topology, virtual networks, peering, routing, and connectivity.

ExpressRoute, VPN, DNS, firewalls, and hybrid connectivity dependencies.

Azure Monitor, Log Analytics, diagnostic settings, and alerting.

Defender for Cloud configuration and security posture.

Resource tagging, cost management, budgets, and ownership.

Existing infrastructure-as-code practices and deployment pipelines.

Review existing Azure architecture against Microsoft Cloud Adoption Framework (CAF) and Azure Landing Zone design principles.

Identify gaps, risks, configuration inconsistencies, security weaknesses, and governance limitations.

Evaluate existing subscriptions and determine their suitability for onboarding into the target Landing Zone.

Review workload placement, regional requirements, network dependencies, and operational ownership.

Identify technical dependencies, implementation prerequisites, and Customer-owned activities.

Produce an assessment report with findings, recommendations, risks, remediation priorities, and implementation roadmap.

B. Target-State Azure Landing Zone Architecture

Develop the enterprise target-state Azure Landing Zone architecture based on assessment findings and Customer requirements.

Define the management-group hierarchy, subscription organization, and platform/workload separation.

Establish the subscription strategy for:

Management and monitoring.

Connectivity and networking.

Identity and shared services.

Production and non-production workloads.

Application-specific or business-unit subscriptions.

Define regional placement and Azure service deployment standards.

Establish naming conventions, resource tagging, resource organization, and ownership standards.

Define RBAC roles, group-based access, administrative boundaries, privileged access, and break-glass procedures.

Design Azure Policy initiatives, assignments, exemptions, and governance enforcement mechanisms.

Define the target architecture for scalability, availability, security, compliance, and operational management.

Present architecture decisions and obtain Customer approval before implementation.

C. Azure Management Groups, Subscription and Governance Implementation

Implement the approved management-group hierarchy and subscription organization.

Configure subscription placement, ownership, and access delegation.

Implement RBAC assignments and least-privilege access controls.

Configure privileged access management and emergency access procedures, where approved.

Implement Azure Policy definitions, initiatives, and assignments.

Configure governance policies for:

Allowed Azure regions and resource types.

Resource naming and tagging.

Security configurations and encryption.

Network exposure and public endpoint restrictions.

Diagnostic settings and logging requirements.

Resource deployment and compliance enforcement.

Configure policy exemptions and exception-management procedures.

Establish subscription-level governance and compliance reporting.

Validate policy enforcement and identify non-compliant configurations.

D. Azure Network and Connectivity Assessment & Implementation

Assess existing Azure networking, IP address allocation, virtual networks, subnet structures, peering, and routing.

Develop the target network architecture, including hub-and-spoke or an approved equivalent topology.

Define IP addressing and subnet allocation aligned with Customer campus and enterprise network standards.

Implement approved Azure virtual networks, subnets, and virtual network peering.

Configure Azure routing, route tables, network security groups, and network segmentation.

Design and implement Azure Firewall and associated security rules, where included in scope.

Define DNS architecture, including Azure DNS, Private DNS Zones, DNS forwarding, and hybrid name resolution.

Configure private endpoints and private connectivity for agreed Azure services.

Assess and coordinate ExpressRoute and VPN integration requirements.

Validate connectivity, routing, DNS resolution, and security boundaries.

Coordinate with Customer network teams for ExpressRoute provisioning, campus-side routing, IP allocation, DNS, firewall, and other dependencies.

Document connectivity requirements, implementation responsibilities, and testing evidence.

E. Azure Security and Compliance Baseline

Establish the Azure security baseline using Microsoft Cloud Security Benchmark and approved Customer security requirements.

Configure Microsoft Defender for Cloud plans and security posture management, as applicable.

Implement approved security recommendations and baseline configurations.

Configure Azure Policy controls for security and compliance enforcement.

Define identity and access security standards, including RBAC and privileged access.

Establish encryption, key-management, network-security, and resource-protection requirements.

Configure security monitoring and alerting for the platform.

Define security exception handling, risk ownership, and remediation procedures.

Assess Microsoft Sentinel applicability, data sources, onboarding requirements, and integration dependencies. A full Sentinel deployment is not assumed unless separately approved.

F. Monitoring, Logging and Operational Management

Design and implement the Azure monitoring and logging foundation.

Configure Log Analytics workspaces and agreed workspace architecture.

Configure Azure Monitor, diagnostic settings, activity logs, and resource logs.

Establish log retention, archival, and data collection requirements.

Configure platform-level alerts, action groups, and notification routing.

Define monitoring coverage for network, platform, security, and critical shared services.

Integrate Defender for Cloud alerts and recommendations into the operational process.

Define incident ownership, escalation procedures, and operational responsibilities.

Validate monitoring coverage and alert functionality.

G. Subscription Vending and Automation

Design and implement a standardized subscription-vending process.

Define subscription request, approval, provisioning, and lifecycle workflows.

Establish subscription vending standards for:

Management-group placement.

RBAC and access assignments.

Azure Policy inheritance.

Network connectivity and DNS integration.

Logging and monitoring configuration.

Resource tagging and cost-center allocation.

Security baseline enforcement.

Develop reusable automation using approved Bicep or Terraform modules.

Integrate provisioning workflows with Azure DevOps or GitHub Actions, as approved.

Implement automated validation, deployment controls, and configuration checks.

Document subscription onboarding, ownership transfer, and decommissioning procedures.

H. Infrastructure as Code and DevOps Implementation

Establish the infrastructure-as-code approach for Landing Zone deployment and ongoing management.

Develop reusable Bicep or Terraform templates for:

Management groups and subscriptions.

Azure Policy and governance assignments.

RBAC and role assignments.

Virtual networks, subnets, and peering.

Azure Firewall and network configurations.

DNS and private endpoints.

Log Analytics and monitoring.

Defender for Cloud and security configurations.

Configure deployment pipelines using Azure DevOps or GitHub.

Implement source control, code reviews, deployment approvals, and environment separation.

Establish parameterization, reusable modules, and version-control standards.

Validate deployment consistency and repeatability across environments.

Document IaC repositories, deployment procedures, and maintenance processes.

I. Platform Validation, Testing and Implementation Closure

Develop and execute Landing Zone validation and testing plans.

Validate management-group and subscription hierarchy.

Test RBAC, privileged access, policy enforcement, and governance controls.

Validate network connectivity, routing, DNS, firewall rules, and private endpoints.

Test monitoring, diagnostic settings, logging, and alert notifications.

Validate subscription vending and automation workflows.

Execute security baseline and configuration compliance checks.

Track defects, configuration gaps, exceptions, and remediation activities.

Obtain Customer validation and approval for the implemented platform foundation.

J. Documentation, Knowledge Transfer and Operational Handover

Prepare and maintain:

Current-state assessment report.

Target-state Azure Landing Zone architecture.

High-level and low-level design documents.

Management-group and subscription hierarchy.

Network architecture and IP addressing documentation.

RBAC and Azure Policy configuration documents.

Security and monitoring baseline documents.

Subscription-vending workflows and automation documentation.

Infrastructure-as-code repositories and deployment guides.

Testing plans, implementation evidence, and exception registers.

As-built architecture and operational runbooks.

Conduct technical walkthroughs and knowledge-transfer sessions.

Define operational ownership, support responsibilities, and escalation procedures.

Complete implementation handover to Customer cloud and operations teams.

3. Required Technical Experience

Proven experience architecting, assessing, and implementing enterprise-scale Azure Landing Zones.

Strong hands-on expertise with Azure management groups, subscriptions, resource organization, and governance.

Deep understanding of Microsoft Cloud Adoption Framework and Azure Landing Zone architecture principles.

Strong experience with Azure networking, including:

Virtual Networks, subnets, and VNet peering.

Hub-and-spoke architecture.

Azure Firewall and Network Security Groups.

User-defined routes and network segmentation.

ExpressRoute and VPN connectivity.

Azure DNS, Private DNS Zones, and private endpoints.

Hands-on experience with Azure Policy, initiatives, RBAC, and privileged access.

Experience implementing Microsoft Defender for Cloud and Azure security baselines.

Experience with Azure Monitor, Log Analytics, diagnostic settings, and alerting.

Strong infrastructure-as-code experience using Terraform or Bicep.

Experience developing and managing deployment pipelines using Azure DevOps or GitHub Actions.

Ability to assess existing Azure environments, identify gaps, and develop actionable implementation plans.

Experience leading technical implementation teams and coordinating with Customer network, security, and cloud stakeholders.

Strong troubleshooting, technical documentation, and client-facing communication skills.

4. Preferred / Good-to-Have Experience

Azure Expert MSP or enterprise-scale Azure platform implementation experience.

Subscription-vending automation and governance frameworks.

Large-scale Azure migration and cloud transformation programs.

Higher education or university cloud environments.

Hybrid campus network integration and ExpressRoute implementations.

Microsoft Sentinel architecture and integration.

FinOps, Azure cost management, budgeting, and tagging strategies.

Azure certifications such as AZ-305, AZ-104, AZ-700, AZ-500, or Terraform Associate.

5. Key Project Deliverables

Azure current-state assessment and gap analysis report.

Azure Landing Zone target-state architecture and approved design.

Management-group and subscription hierarchy implementation.

RBAC, privileged access, and Azure Policy configuration.

Azure network foundation and connectivity implementation.

Azure security and compliance baseline.

Monitoring, logging, and alerting foundation.

Subscription-vending design and automation.

Infrastructure-as-code modules and deployment pipelines.

Platform validation and testing evidence.

As-built architecture, operational runbooks, and knowledge-transfer documentation.

6. Scope Boundaries and Assumptions

The engagement establishes and validates the Azure Landing Zone platform foundation; it does not automatically include bulk migration or remediation of existing application workloads.

Existing subscriptions will be assessed for onboarding suitability. Migration or remediation of all existing subscriptions is not assumed.

Customer remains responsible for campus-side network changes, ExpressRoute provisioning, physical connectivity, IP allocation approvals, and related infrastructure dependencies.

Customer will provide the required Azure tenant access, subscriptions, licenses, network information, and stakeholder availability.

Application-level configurations and workload-specific remediation remain outside the platform scope unless explicitly approved.

Employers have access to artificial intelligence language tools (“AI”) that help generate and enhance job descriptions and AI may have been used to create this description. The position description has been reviewed for accuracy and Dice believes it to correctly reflect the job opportunity.
  • Dice Id: 91089145
  • Position Id: 9147498
  • Posted 24 minutes ago

Company Info

About SDH Systems

SDH Systems is a team of creatives with experience in design, content, vision and mission. Using these skills we create creative assets.
We always ensure that our software solutions help your business/organization to enhance their productivity by providing you the unmatched developement solutions tailored to suit your needs. Most of our team has on the job experience in more than one medium, so that we can integrate these to build a creative identity.

About_Company_OneAbout_Company_Two
Contact the job poster
VA

Vidhaan Aggarwal

Recruiter @ SDH Systems

Create job alert
Never miss an opportunity! Create an alert based on the job you applied for.