← redevops.ioAll reference implementations →
Reference implementation · Azure Semantic Kernel

Semantic Kernel plans the deploy.
ReDevOps decides if it may ship.

A real Microsoft Semantic Kernel v1.36.0 agent — a Kernel, plugin functions, auto function-calling — runs in-process with the Mission SDK. No mock, no sidecar approximation.

▸ runs locally · no Azure cloud credentials · Entra identity modelled as policy
Semantic Kernel
Kernel · plugins / functions
function-calling · planners
the agent loop
the agent — kept intact
→
rAIls
Compliance-control gate
Authority · Entra deny-wins
Approval · Replay
deployment as a governed Mission

Semantic Kernel's strongest abstraction is function-calling, so we test the boundary immediately outside it. The agent invokes request_deploy(...) whenever it decides to — with no notion of whether the target is compliant or the identity authorized. ReDevOps admits the deploy only when every required compliance control for the environment is evidenced, and the Entra role permits it — then runs it as a Mission.

Compliance gate

Compliant and authorized, or it doesn't ship

3/3 denied · 0 wrong

The real SK agent plans a deployment in every case. ReDevOps denies each one that is missing a required control or unauthorized for the environment — deny-by-default — while admitting 2 of 2 fully-evidenced, authorized deployments.

Governed deploy

Behaviour, not a plan

0 unauthorized · 0 duplicates

An admitted deploy still runs only through a Mission: approval held; exactly-once execution; replay reconstructs from the event ledger and fires zero extra deploys. A stateless re-run re-ships on every crash.

Authority composition

Deny-wins over Entra

grant ∩ role

Effective authority is the intersection of the framework grant and the Entra role — never the union. A fully-compliant production deploy is still denied when the identity's Entra role does not permit production. The restrictive policy governs.

The gate is deterministic — the value is the enforced mechanism, not a model score. The real Semantic Kernel agent genuinely plans and invokes the deployment; what ReDevOps changes is whether that request is allowed to become a deployment.

View the Semantic Kernel reference implementation → Run the benchmark → Read the architecture article →
// conformance summary   every native-vs-native+ReDevOps comparison is classified — PARITY / FRAMEWORK_NATIVE_ADVANTAGE / REDEVOPS_DELTA / EXPECTED_IMPLEMENTATION_DIFFERENCE / BUG. Azure suite: 7 REDEVOPS_DELTA · 1 PARITY · 0 EXPECTED_IMPLEMENTATION_DIFFERENCE · 0 BUG. Full tables, environment and acceptance hashes on the benchmark page.

// semantic-kernel 1.36.0 · Mission SDK 0.2.0 · Context Runtime 0.2.0 · local, no Azure cloud · github.com/redevops-io/redevops-integrations

Azure, Entra, and Semantic Kernel are trademarks of Microsoft Corporation. This is an independent integration, not a Microsoft product or endorsement, and uses no Azure services.