Discovery Sessions Overview
DOCUMENT CATEGORY: Runbook SCOPE: Customer discovery session framework PURPOSE: Structure and guide discovery workshops MASTER REFERENCE: Microsoft Learn - Azure Local Planning
Status: Active
Discovery sessions are structured workshops conducted with customer stakeholders to gather requirements, assess infrastructure, and plan Azure Local deployments. This framework ensures consistent, thorough discovery across all engagements.
Overview
The discovery process is organized into five phases that progressively build the complete picture needed for successful Azure Local deployment:
- Pre-Discovery Planning - Internal preparation and scheduling
- Customer Workshops - Stakeholder interviews and requirements gathering
- Workload Assessment - Technical analysis of existing workloads
- Data Consolidation - Compile and validate gathered information
- Deliverables Handoff - Formal handover of discovery artifacts
Sessions
| Session | Description | Duration | Participants |
|---|---|---|---|
| Pre-Discovery Planning | Internal prep, scheduling, initial data request | 2-4 hours | deployment team |
| Customer Workshops | Business & technical requirements gathering | 4-8 hours | Customer + Azure Local Cloud |
| Workload Assessment | Existing infrastructure and workload analysis | 4-6 hours | Technical teams |
| Data Consolidation | Compile, validate, and organize discovery data | 2-4 hours | deployment team |
| Deliverables Handoff | Formal handover of completed discovery package | 1-2 hours | All stakeholders |
Workflow
flowchart LR
A["Pre-Discovery<br/>Planning"] --> B["Customer<br/>Workshops"]
B --> C["Workload<br/>Assessment"]
C --> D["Data<br/>Consolidation"]
D --> E["Deliverables<br/>Handoff"]
E --> F["Discovery<br/>Complete"]
Key Deliverables
| Deliverable | Description |
|---|---|
| Discovery Questionnaire | Completed customer requirements document |
| Site Assessment Report | Physical and network infrastructure evaluation |
| Workload Inventory | Catalog of workloads to migrate/deploy |
| Architecture Design | Proposed cluster topology and network design |
| Bill of Materials | Hardware, licensing, and resource requirements |
Prerequisites
Before beginning discovery sessions:
- Customer engagement approved and scheduled
- Azure Local Cloud discovery team assigned
- Initial data request sent to customer
- Access to customer stakeholders confirmed
Next Steps
After completing discovery, proceed to CI/CD Infrastructure to establish automation infrastructure.