Azure Central US region for Serverless
Status: Underway — target end of September
Priority: Must have
Audience: Platform, networking, application owners
Why it matters
Your primary Azure region is Central US — where production clusters and the application monolith already run. Serverless Search should be in that region for latency. If it is not, traffic would need another Azure region (for example East US) plus extra replication — more cost and complexity.
Region guidance
| Region | Role |
|---|---|
| Central US | Required — primary production region |
| East US | Not the production target (nice to have / stale ask only) |
| East US 3 | Longer-term failover / DR once Serverless is available there |
Current state
- Azure Central US for Serverless is in progress and treated as high priority.
- Target: end of September.
- Until Central US is live, do not assume production interactive search can sit in-region.
Recommendation
- Keep Central US as the hard regional requirement for production.
- Do not design production around East US as the home region.
- Avoid a standing cross-region replica as the default architecture; that is a contingency if Central US slips, not the plan.
- Pair the region with Private Link in the same footprint when it lands.
Options
| Option | What it means | Tradeoff |
|---|---|---|
| A. Wait for Azure Central US (recommended) | Production Serverless in the primary region | Depends on end-of-September target |
| B. Run production in East US | Use an available Azure region now | Misses latency / locality requirement |
| C. Cross-region replication into Central US later | Temporary East US plus replication | Extra cost and complexity — last resort |
Recommendation: Option A. Track the end-of-September target; do not lock cutover on East US.
Acceptance criteria
- Serverless Search project available in Azure Central US
- Private connectivity validated in that region
- Target end of September confirmed in production
- DR strategy documents East US 3 as the future secondary (when available)
Related
- Private networking (Private Link)
- Snapshot restore → Point-in-time restore