[Epic] Choose the right Azure architecture, service, region, and sample

## Problem statement

Developers must reconcile service capabilities, regional availability, quotas, cost, architecture tradeoffs, and sample quality before implementation. Fragmented guidance produces poor or non-deployable choices.

## Outcome

Developers receive workload-aware recommendations for an Azure architecture, services, region, cost model, and maintained deployable sample.

## Goals

- Compare services using workload requirements and constraints
- Account for regional availability, quota, capacity, and cost
- Recommend maintained samples and templates that match language and architecture
- Explain tradeoffs and assumptions

## Non-goals

- Guaranteeing future capacity or pricing
- Maintaining every external sample

## Success criteria

- [ ] Recommendations identify relevant constraints and tradeoffs
- [ ] Suggested samples and templates are valid and deployable
- [ ] Evaluation coverage includes ambiguous architecture decisions

## Dependencies

Azure service metadata, pricing and quota tools, template catalogs, and service owners.

No files, tests, or entry points are named. Start by reviewing the goals, non-goals, dependencies, and success criteria, then identify the project components responsible for recommendations and evaluation coverage; done means recommendations account for constraints and tradeoffs and suggested samples are valid and deployable.

Written by the indexing model from the issue text.