Why should you care?

Buyers evaluate data residency, role-based access, and cost caps before enabling copilots on production customer data.

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.Api/Tenancy/TenantAiContext.cs
public sealed record TenantAiContext(
    string TenantId,
    string ModelDeployment,
    int MonthlyTokenQuota,
    IReadOnlySet<string> AllowedPlugins);

public interface ITenantAiContextAccessor
{
    TenantAiContext Current { get; }
}

What happened?

• TenantAiContext bundles per-tenant model choice, spend limits, and plugin allow lists.
• Middleware resolves it from JWT claims before any agent executes.

Practice next

1. Add TenantAiContext and resolve it in middleware from auth claims.
2. Store quotas in SQL and decrement in a delegating IChatClient wrapper.
3. Map AllowedPlugins to Semantic Kernel plugin registration filters.
4. Add DataRegion to TenantAiContext for EU-only Azure deployments.
5. Return 429 with Retry-After when MonthlyTokenQuota is exceeded.

Remember

Enterprise AI wraps models with tenant context and policy. AgentNest gates plugins and deployments per customer. Quotas and audit trails are first-class, not afterthoughts.

Multi-tenant SaaS launch

AgentNest sells CRM copilot to 200 tenants on one cluster.

Outcome: TenantAiContext enforces plugin boundaries and token budgets without separate deployments per customer.