Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides a template for startups building a cloud-native business in Azure. It helps you document operational models, responsibilities, training plans, platform architecture, and workload details to ensure a successful migration.
Operating model and responsibilities
| Category | Documentation to add |
|---|---|
| Operating model | Specify whether your operating model is centralized or not. |
| Responsibilities | Define and assign responsibility for the platform and workload(s). Include names, roles, and specific tasks. |
For more information, see Prepare your organization.
Cloud training plan
| Category | Documentation to add |
|---|---|
| Learning sandbox | Provide details about the sandbox environment subscription, access policies, and usage guidelines. |
| Continuous learning program | Outline the monthly learning time allocated, recognition systems (points, badges), and plans for community engagement, such as events or user groups. |
For more information, see Prepare your people.
Azure landing zone architecture
| Category | Documentation to add |
|---|---|
| Resource hierarchy | Define the hierarchy, including management groups, subscriptions, and resource groups. |
For more information, see Plan your Azure landing zone architecture
Requirements for each cloud-native workload
For each workload you plan to build, document business and technical requirements.
Workload business requirements for cloud-native builds
| Workload business details | Documentation to add |
|---|---|
| Workload name | Enter the official name used across the organization |
| Workload description | Write a single sentence describing the workload's purpose |
| Timelines | List the target date to have production-ready workload |
| Workload owners | List individuals accountable for workload |
| Compliance requirements | Specify regulatory standards or certifications required |
| Target users | Document number and locations of user base |
For more information, see Document workload business details.
Workload technical requirements for cloud-native builds
| Workload technical details | Documentation to add |
|---|---|
| Component requirements | List performance metrics (CPU, memory, IOPS, throughput), OS versions, VM sizes, storage types, and licensing details |
| SLAs (RTO/RPO) | Define service-level agreements, recovery point objectives (RPO), and recovery time objectives (RTO). Use this information to guide backup, replication, and failover strategies |
For more information, see Assess your workload.
Target Azure architecture for the workload
| Azure workload details | Documentation to add |
|---|---|
| Target architecture | Add a link to a diagram you created or sample architecture on Azure Architecture Center |
| Azure services and SKUs | List the Azure services and SKUs required for the workload |
| Azure regions | Specify the Azure regions where the workload will be hosted |
| Estimated workload cost | Calculate estimated cost using the Azure Pricing calculator |
| Estimated workload operational cost | Estimate how many people or hours you dedicate to this workload |