Azure Landing Zone Discovery & Architecture Review

Azure Landing Zone Discovery & Architecture Review

Private 1:1 Architecture Service

Price: $300 USD

Includes: Two 50-Minute Private 1:1 Sessions — 100 Minutes Total

Designing an Enterprise Azure Landing Zone requires more than following a Reference Architecture or Deploying a Predefined Template.

Every Organization has different requirements, existing Infrastructure, Network Architecture, Identity Dependencies, Security requirements, Governance Requirements, Workloads, Connectivity, Cloud platforms, and Operational Constraints.

The Azure Landing Zone Discovery & Architecture Review is a Private 1:1 Technical Engagement focused specifically on your existing or proposed Environment and the goals you need to accomplish.

Before the First Live Session, you submit detailed information about your current environment and your objectives. Your submitted environment is reviewed before the Discovery Sessions begin.

The two private Discovery sessions are then used to review the environment with you, ask and Answer Technical Questions, Identify Architectural Concerns, discuss requirements and constraints, and provide Azure Landing Zone Guidance, recommendations, Do's and Don'ts.

Phase 1 — Discovery & Architecture Review

The initial $300 USD Engagement Includes:

Two 50-minute Private 1:1 Sessions  - 100 minutes total.

Phase 1 is dedicated to:

• Reviewing your current or proposed environment
• Understanding your existing Architecture
• Understanding what you need to accomplish
• Reviewing your submitted Architecture diagrams and technical information
• Discussing existing design decisions
• Identifying Architecture concerns and potential problems
• Identifying dependencies and technical constraints
• Asking detailed technical questions
• Answering your Azure Landing Zone questions
• Providing Architecture recommendations
• Providing Azure Landing Zone general guidelines
• Providing Azure Landing Zone Do's and Don'ts
• Discussing alternatives where appropriate
• Identifying areas requiring redesign or additional Architecture work
• Establishing the scope and complexity of any Custom Architecture work you may elect to pursue

Required before discovery can begin

You must provide complete and accurate information about your current environment before the Discovery Engagement can begin.

The information should include everything relevant to the Azure Landing Zone Architecture and your Stated Objectives.

Depending on your environment, this may include:

• Microsoft Entra Tenants
• Azure Management Group Hierarchy
• Azure Subscriptions and their Purposes
• Azure Regions
• Existing Azure Landing Zone Architecture
• Existing Virtual Networks and CIDR Allocations
• Hub-Spoke Architecture
• Azure Virtual WAN
• Network Peering
• Azure Firewall
• Third-party Firewalls and Network Virtual Appliances
• Network Security Groups
• User Defined Routes
• Private Endpoints
• Private DNS
• Azure DNS Private Resolver
• ExpressRoute
• Site-to-Site VPN
• Point-to-Site VPN
• On-Premises Datacenters
• Active Directory Domain Services
• Microsoft Entra ID
• Hybrid Identity
• RBAC Architecture
• Azure Policy
• Security and Governance requirements
• Logging and Monitoring Architecture
• Production and Non-Production environments
• Business Continuity and Disaster Recovery requirements
• Existing Architecture diagrams
• Regulatory or Compliance requirements
• Known Technical Limitations
• Existing Architectural Problems
• Planned Migrations or Major Infrastructure Changes

Multi-Cloud and Hybrid Environments

You must disclose all other infrastructure and Cloud Platforms that are relevant to the requested Architecture.

For Example, if your environment includes:

Azure + AWS + On-Premises Datacenters, all three must be disclosed in the Original Environment submission if they are relevant to the Architecture.

AWS, Google Cloud, additional Azure Tenants, Acquired-Company Environments, Datacenters, Third-Party Networks, Security Platforms, or other Dependencies must not be omitted when they materially affect the requested Azure Landing Zone Architecture.

You must clearly state your goals

In addition to your current environment, you must clearly describe what you need to accomplish.

Examples Include:

• Design a new Enterprise Azure Landing Zone
• Review an existing Azure Landing Zone
• Prepare an existing Environment for Landing Zone Adoption
• Restructure Management Groups and Subscriptions
• Establish Production and Non-Production Separation
• Design Hub-Spoke Networking
• Evaluate Azure Virtual WAN
• Establish Enterprise CIDR Architecture
• Integrate Azure with existing Datacenters
• Integrate Azure with AWS or another Cloud Platform
• Establish Private Endpoint and Private DNS Architecture
• Implement Azure Firewall and Routing Architecture
• Establish Azure Policy and Governance
• Design RBAC Boundaries
• Improve Security Architecture
• Prepare for Multi-Region Deployment
• Design Disaster Recovery and Resiliency
• Identify Architectural Problems in an Existing Environment

The more clearly your Objectives are defined, the more effectively the Discovery Sessions can be used.

Pre-Session Environment Review

After payment and the complete required environment information and Objectives have been received, your submitted environment will be reviewed before the first Discovery Session.

Please allow up to Seven Business Days for this review.

The purpose of the Pre-Session Review is to understand the submitted Environment before meeting with you so that the live sessions can focus on Meaningful Technical Discussion rather than spending your purchased Session time reading Documentation for the first time.

Your Initial Submission Establishes the Scope

The Environment, Platforms, Dependencies, Requirements, and Objectives included in your Original Submission establish the Scope of the Initial Discovery Engagement.

Phase 1 will be conducted based on the environment and requirements you submitted for review.

Additional or Previously Undisclosed Scope

Material infrastructure, Cloud platforms, Datacenters, Networks, Security Systems, requirements, dependencies, or other Architectural Components introduced after the Initial Environment Submission are Considered Additional Scope.

For Example, if the original submission describes an Azure-Only Environment and it is subsequently disclosed that the proposed Architecture must also integrate with AWS and Multiple On-Premises Datacenters, those Additional Environments represent Additional Scope.

Additional Scope may require further review and additional Discovery Sessions.

Additional Discovery Session: $150 USD per 50 minutes

Complex environments may require additional discovery

The initial engagement includes Two 50-Minute Discovery Sessions.

For many environments, this may provide sufficient time to complete the initial Discovery and Architecture Review.

However:

The purchase of Phase 1 does not guarantee that Discovery can be completed within the initial 100 minutes.

Large or Highly Complex Environments may require additional Discovery Time.

Examples may Include:

• Large Enterprise Azure Environment
• Multiple Azure Tenants
• Large numbers of Subscriptions
• Multiple Azure Regions
• Hybrid Azure and On-Premises environments
• Azure and AWS Multi-Cloud Environments
• Multiple Datacenters
• Complex ExpressRoute Architectures
• Large Hub-Spoke Environments
• Complex Azure Virtual WAN Environments
• Multiple Network Virtual Appliances
• Complex DNS Environments
• Large Private Endpoint Deployments
• Complex Identity architectures
• Significant Regulatory Requirements
• Environments Resulting from Mergers or Acquisitions
• Existing Environments requiring Substantial Architectural Remediation

If additional Discovery is required, additional Sessions are available at:

$150 USD Per 50-Minute Session

Discovery continues until sufficient understanding of the agreed environment and requirements has been established.

What Phase 1 Does NOT Include

The $300 USD Phase 1 engagement does NOT include the creation, engineering, documentation, implementation, deployment, migration, or delivery of a Custom Azure Landing Zone Architecture.

What Phase 1 Does Include

Discovery + Environment Review + Questions & Answers + General Architecture Guidance + Do's and Don'ts + Recommendations

Phase 1 does not include the development or delivery of Custom Azure Landing Zone Architecture.

Phase 1 must be completed before Custom Architecture Development begins.

Phase 2  - Custom Azure Landing Zone Architecture

After Phase 1 Discovery has been completed, you may elect to continue with Phase 2  - Custom Azure Landing Zone Architecture.

Phase 2 is Optional.

There is no obligation to continue after Phase 1.

If you elect to proceed, Custom Architecture Services are provided at:

$150 USD per 50-Minute Private Architecture Session

There is no predetermined number of Phase 2 Sessions.

The amount of Architecture time required depends upon the:

• Size of the Environment
• Complexity of the Environment
• Number of Cloud Platforms
• Number of Azure Tenants
• Number of Subscriptions
• Number of Regions
• Hybrid Infrastructure Requirements
• Network Complexity
• Identity Architecture
• Security Requirements
• Governance Requirements
• Regulatory Requirements
• Existing Technical Debt
• Migration Requirements
• Required Architecture Scope
• Required Deliverables
• Customer Objectives

A relatively simple Azure-Only Landing Zone will not require the same amount of Architecture work as a large Enterprise Environment Incorporating Azure, AWS, multiple Datacenters, multiple Regions, Hybrid Identity, ExpressRoute, complex Security Controls, and Regulatory Requirements.

For this reason, the total number of Phase 2 Sessions cannot be established until Discovery has been completed.

Additional Phase 2 Sessions may be purchased for as long as you elect to continue the Architecture Engagement.

Scheduling

The first Discovery Session will be scheduled only after:

Payment has been received

AND

The required Environment Information has been submitted

AND

Your goals and Objectives have been Clearly Stated and submitted

Please allow up to Seven Business Days for the formal Environment Review after we confirm that Sufficient Environment Information, requirements, Objectives, and Supporting Details have been received.

Incomplete Environment Submissions may Delay Scheduling.

Do Not Provide:

• Passwords
• Access Keys
• Client Secrets
• API Keys
• SAS Tokens
• Authentication Tokens
• Private Keys
• Certificates containing Private Keys
• Recovery Codes
• MFA Credentials
• Other Authentication Secrets

Security Requirement: Architecture information must be provided without exposing Credentials, Secrets, Authentication Information, or other Sensitive Information that could compromise or weaken the Security of your Environment. Before submitting any Documentation, Diagrams, Screenshots, Configuration Information, or other Materials, you are responsible for Reviewing and Redacting Information that is not required for the Architecture Review.

Never Submit Passwords, Access Keys, Client Secrets, API Keys, SAS Tokens, Authentication Tokens, Private Keys, MFA Credentials, Recovery Codes, or other Authentication Credentials.

We will never request Passwords, Authentication Credentials, Private Keys, or other Secrets as part of the Azure Landing Zone Discovery and Architecture Review.

 The Quality and Completeness of the Discovery Process depend on the Accuracy and Completeness of the Information Provided.

The Customer is responsible for Identifying and Disclosing Infrastructure, Dependencies, Requirements, and Constraints that materially affect the requested Architecture.

Previously Undisclosed Information that materially changes the Scope of the Engagement may require additional Discovery and Additional Paid Sessions.

Phase 1 - Azure Landing Zone Discovery & Architecture Review

Price: $300 USD
Sessions: 2 × 50 Minutes
Total Live Session Time: 100 Minutes
Pre-Session Review: Up to 7 Business Days
Includes: Environment Review, Discovery, Q&A, General Architecture Guidance,   Do's and Don'ts, Observations and Recommendations
Custom Architecture Design: Not Included
Additional Discovery: $150 USD per 50-Minute Session

Phase 2 — Custom Azure Landing Zone Architecture

Optional: Yes
Price: $150 USD per 50-Minute Session
Number of Sessions: Determined by Environment Complexity, Architecture Scope and Customer Requirements
Commitment: No obligation to continue after Phase 1

Purchasing the Azure Landing Zone Discovery & Architecture Review does not purchase Azure Landing Zone Architecture.

The initial $300 USD Service provides Two 50-Minute Private Discovery and Architecture Review Sessions based on the Environment and Objectives Submitted before the Engagement.

Custom Architecture Development is a separate, optional Phase 2 Service billed at $150 USD per 50-Minute Session. The number of Sessions required depends on the complexity of the Architecture and the Scope of Architecture Development you elect to Pursue.

Contact Information and Pre-Session Review Requirements

To complete the Environment Review and prepare for the Discovery Sessions, we must be able to contact you if clarification or additional information is required.

When submitting your environment information, you must also provide:

• Full Name
• Contact Email Address
• Time Zone
• Preferred Hours for Contact

During our Initial Review of your Submitted Environment, we may identify missing Information, Unclear Architecture Details, Conflicting Information, or Additional Technical Details Required to properly understand your current Environment.

If additional information or clarification is required, we will contact you using the information you provided.

The Seven-Business-Day Environment Review Period begins only after we determine that Sufficient Environment Information, requirements, Objectives, and Supporting Documentation have been received to reasonably understand the current Environment and begin the formal Environment Review.

The initial Seven-Business-Day Environment Review Period does not begin Automatically on the Date of Purchase or the Date of the First Submission.

The Seven-Business-Day period begins only after we have received Sufficient Environment Information, Requirements, Objectives, and Supporting Details necessary to reasonably understand the current Environment and begin the formal Environment Review.

If we request additional information or Clarification before the formal review can begin, the Seven-Business Day review period will not begin until the requested information has been received.

If Additional Information is required during the Seven Business Day Review Period, the review timeline may be extended by the amount of time required to receive and Evaluate the Requested Information.

If you have any questions or need additional information regarding the Discovery and Architecture Review Service, please contact us via email: support@ITCloudAcademy.net

Preferred Hours for Technical Follow-Up:

Monday to Friday
9:00 AM to 6:00 PM MST

Customer response time may affect Scheduling
Timely communication is required during the Environment Review.
Delays in responding to requests for Missing Information, Clarification, Documentation, Diagrams, Requirements, or other necessary Technical Details will extend the Environment Review timeline and may delay Scheduling of the First Discovery Session.

The first Discovery session will not be scheduled until the Environment Review has been completed, and Sufficient Information has been Obtained to conduct a meaningful Discovery Engagement.