The full, reproducible evidence behind the integration page. A real semantic-kernel 1.36.0 agent, run locally and in-process with the Mission SDK — no Azure cloud — measured on compliance-gated deployment, a governed deploy, and Entra deny-wins authority. Every comparison is classified — this is conformance, not a scorecard.
| Experiment | Native role | ReDevOps addition | Result | Classification |
|---|---|---|---|---|
| AZ-A Compliance gate | SK invokes request_deploy | deny-by-default control gate | 3/3 bad denied · 0 wrong | REDEVOPS_DELTA |
| AZ-A Compliant admitted | — | authorized work admitted | 2/2 admitted | PARITY |
| AZ-B Governed deploy | agent plans the deploy | authority · approval · replay | 0 unauthorized · 0 duplicates | REDEVOPS_DELTA |
| AZ-C Deny-wins | framework grant | ∩ Entra role | prod denied though compliant | REDEVOPS_DELTA |
| AZ-E Telemetry | SK agent/function spans | Mission-root nesting | preserved (nested) | REDEVOPS_DELTA |
A real Semantic Kernel agent plans request_deploy(service, environment) for each request — and it does, in all five cases. ReDevOps admits the deployment only when every required compliance control for the target environment is evidenced (staging needs encryption + an approved image; production also needs a network policy + change approval) and the identity's Entra role permits the environment. Native SK would proceed on all five; ReDevOps denies the 3/3 that are missing a control or unauthorized (0 wrong) and admits the 2/2 that are fully evidenced and authorized.
An admitted deploy still runs only through a Mission. Missing grant ⇒ 0 unauthorized. Grant but no approval ⇒ parked at a human gate, 0 deploys. Approved ⇒ fires exactly once. Replay ⇒ 0 duplicate deploys, reconstructed from the event ledger.
Effective authority is the intersection of the framework grant and the Entra role, never the union. A CI identity with a framework grant for staging + production but an Entra role scoped to staging only gets staging only: a fully-compliant production deploy is still denied. The restrictive policy governs — a permissive framework grant never widens cloud identity.
Each run writes a reproducibility record — framework version, model ids, per-finding classification, and a content-addressed result digest.
// reproducible · local, no Azure cloud · github.com/redevops-io/redevops-integrations/integrations/azure · integration page · architecture article