Why should you care?

Multinational CRM customers forbid US model processing for EU employee data — global design encodes residency.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Global/RegionRouter.cs
public sealed class RegionRouter(ITenantStore tenants)
{
    public Uri ResolveOpenAiEndpoint(string tenantId)
    {
        var region = tenants.GetDataRegion(tenantId); // "eu" | "us"
        return region == "eu"
            ? new Uri("https://agentnest-openai-eu.openai.azure.com/")
            : new Uri("https://agentnest-openai-us.openai.azure.com/");
    }
}

What happened?

• RegionRouter picks Azure OpenAI endpoint from tenant data region — global SaaS without cross-border model calls.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Store DataRegion on tenant record at provisioning.
2. Deploy paired stacks in EU and US with Front Door geo routing.
3. Localize prompt templates via IStringLocalizer.
4. Add ap-southeast region for APAC hospital tier.
5. Fail over within region pair only — never cross residency.

Remember

Global AgentNest routes tenants to regional model endpoints. DataRegion drives OpenAI, storage, and backup location. Localize prompts; monitor regional latency SLIs.

EU CRM rollout

German subsidiary onboarded with strict EU data residency.

Outcome: RegionRouter sends all inference to EU OpenAI; vectors stay in EU Qdrant cluster.