Why should you care?

ERP close weekend forbids agent outages; hospital triage needs rollback in minutes if new kernel plugin misbehaves.

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/Deployment/FeatureFlags.cs
public static class FeatureFlags
{
    public const string CrmCopilotV2 = "crm-copilot-v2";
}

// Program.cs
builder.Services.AddFeatureManagement(builder.Configuration.GetSection("FeatureManagement"));

// Controller
[FeatureGate(FeatureFlags.CrmCopilotV2)]
app.MapPost("/api/crm/copilot/v2", ...);

What happened?

• Feature flags decouple deploy from exposure — v2 agent ships dark until flag enabled per tenant in Azure App Configuration.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Deploy to staging slot; run smoke eval against staging OpenAI.
2. Swap slots or shift Container Apps traffic 10/90 canary.
3. Enable feature flag for pilot tenant; monitor error rate.
4. Automate flag enable from Azure DevOps gate after eval pass.
5. Pair deploy with database migration for audit schema.

Remember

Use slots, canary traffic, and feature flags for AI releases. Pilot new agents on one tenant before global enable. Rollback via config flags when possible.

CRM copilot v2 rollout

New CrmCopilotAgent ships Saturday; only two tenants opt into beta flag.

Outcome: Stable weekend for others; beta feedback fixes prompt before general availability.