| Organizations that need broad infrastructure managed services and architecture choice | Cloud infrastructure data application container serverless and artificial intelligence services | Breadth creates flexibility and requires disciplined architecture security and cost governance | Use the official Well Architected Framework and test the selected services in the required regions |
|---|
| Microsoft centered organizations and workloads requiring broad cloud or hybrid capability | Cloud infrastructure application data integration identity and artificial intelligence services | Service selection identity and governance need clear ownership across the Microsoft environment | Use the official Well Architected Framework and verify region service and identity requirements |
|---|
| Data intensive artificial intelligence container and modern application workloads | Cloud infrastructure analytics data container application and artificial intelligence services | Teams still need planned architecture identity operations and cost governance | Use the official Cloud Architecture Framework and verify selected regional services |
|---|
| Smaller engineering teams seeking a focused cloud service catalogue and direct developer experience | Compute managed data container application storage and network services | A focused catalogue can simplify choice while providing less breadth than the largest clouds | Test required services regions recovery monitoring support and scaling with the real workload |
|---|
| Global web applications interfaces edge workloads media and distributed services | Distributed compute storage data media network and artificial intelligence capabilities | The execution and data model differs from conventional server hosting | Validate runtime limits data needs observability regions and failure behaviour with a representative proof |
|---|
| Frontend teams and modern web applications aligned with supported framework workflows | Managed web builds deployments previews functions and global delivery | Platform conventions reduce delivery work and create dependencies that should be understood | Test the actual framework build runtime data integrations observability and transition path |
|---|
| Composable websites and modern web applications using managed delivery workflows | Managed builds hosting previews functions edge services forms and web delivery | Backend intensive systems may require additional services and coordinated ownership | Test build runtime function data identity monitoring and integration requirements directly |
|---|
| Teams that value managed application deployment over direct infrastructure control | Managed application runtimes build workflows extensions and data services | Operational convenience comes with platform conventions and less infrastructure control | Validate runtime data add on region recovery support and current operating cost needs |
|---|
| Teams deploying web applications interfaces workers jobs containers and managed data | Managed application and data services connected with source repositories | Integrated services reduce setup while region and service fit must be checked | Test deployment preview network scaling recovery observability and required region availability |
|---|
| Distributed container applications agents and workloads that benefit from regional placement | Container compute private networking storage and distributed application services | The platform gives application teams control and expects meaningful infrastructure knowledge | Test deployment state network storage recovery observability and regional behaviour with the real architecture |
|---|