Production Strategy: Should we start with Semantic Kernel and migrate to Agent Framework post-GA

[kalmeshcs]

Microsoft Agent Framework is currently in beta with no announced GA date. I believe using preview/beta frameworks in production applications is not recommended.

Is it advisable to:

• Build our initial release using Semantic Kernel
• Migrate to Agent Framework later once it reaches GA

Looking for:

• Guidance on production readiness of Agent Framework beta
• Any visibility into GA date/timeline
• Recommended approach for enterprise production deployments
• Migration complexity assessment (SK ↔ Agent Framework)

[aeris-systems]

Great questions — we're wrestling with similar decisions.

On SK vs Agent Framework in production:

Semantic Kernel is production-ready today and used in enterprise deployments. The filter architecture (IPromptRenderFilter, IAutoFunctionInvocationFilter) gives you hooks for validation, logging, and guardrails that are essential for production.

Agent Framework is promising but still evolving. For initial production release, SK makes sense — you can build with confidence and migrate later if AF's capabilities become compelling. The mental models (plugins, planners, filters) are similar enough that migration shouldn't be a rewrite.

Key production considerations (from our experience):

1. Tool-call validation — When agents call external tools, you need pre/post-call checks. SK's filter pipeline is designed for this.

2. Trust boundaries — User input → LLM → tool execution is a chain where each hop needs scrutiny. Filter-based validation catches issues before they propagate.

3. Observability — SK's event system integrates well with OpenTelemetry; essential for debugging production issues.

Re: migration complexity:

SK → AF migration is less about code rewrite and more about understanding AF's agent lifecycle vs SK's kernel-centric model. Start with SK, invest in solid filter/plugin patterns, and those patterns transfer.

We're working on production-hardening examples (prompt validation filters specifically) — happy to share if useful. See PR #13519 for what we're contributing back.

[jagmarques]

For production deployments, starting with SK now is reasonable - the core kernel, connectors, and plugin system are stable. The Agent Framework adds orchestration patterns (group chat, handoffs) on top.

The main thing to watch: the Agent Framework API is still evolving, especially around multi-agent coordination and state management. If you build on SK core (Kernel + plugins + planners), migration to the Agent Framework later is incremental since agents use the same kernel underneath.

Practical advice: use SK core for your business logic and plugin definitions. Keep agent orchestration patterns in a thin layer you can swap out. That way you are not blocked waiting for GA but also not locked into pre-GA APIs.

[moonbox3]

Microsoft Agent Framework is now at GA. We'd recommend starting there.