Why should you care?

Agent features fail if Redis, vector DB, or OpenAI endpoint is mis-sized — infrastructure is part of the product SLA.

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.Infrastructure/IaC/main.bicep excerpt
resource openAi 'Microsoft.CognitiveServices/accounts@2023-05-01' = {
  name: 'agentnest-openai-prod'
  location: location
  kind: 'OpenAI'
  sku: { name: 'S0' }
  properties: { customSubDomainName: 'agentnest-openai-prod', publicNetworkAccess: 'Disabled' }
}

What happened?

• Bicep provisions private Azure OpenAI with custom subdomain — baseline infra AgentNest apps reference via App Configuration.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Define Bicep/Terraform modules for OpenAI, Postgres, Redis, Service Bus.
2. Deploy dev/staging/prod with separate OpenAI instances.
3. Wire managed identity from App Service to each resource.
4. Add geo-redundant Redis for session memory failover.
5. Parameterize SKUs per environment in Bicep.

Remember

AgentNest infra includes models, vectors, cache, queue, and SQL. Provision per environment with IaC templates. Use private networking for regulated tenants.

Production go-live checklist

New region launch requires full AgentNest stack in West Europe.

Outcome: Bicep module deploys matched infra; agents pass health checks before tenant migration.