Self-Healing Operations

Two loops. One reviewed handoff.

Raghib Hasan

Two loops, one handoff

Two loops, one handoff A software change moves from assessment through deployment. An operations loop observes, investigates, acts, and verifies. A recurring incident feeds the next reviewed change. MODERNIZE OPERATE NEXT CHANGE INCIDENT EVIDENCE OBSERVE AGAIN Assess Change Review Deploy Observe Investigate + act Verify

Agents propose. Runtimes enforce.

Agent proposal and runtime controls Evidence informs an agent's tool proposal. The runtime checks resource permissions and action policies before a tool runs, then returns its result to the agent. ALT [APPROVED] [DENIED] PROPOSE SCOPE ROLE ALLOWS REQUEST REVIEW APPROVE INVOKE RESULT DENY REPORT Agent Runtime Resource roles what can it reach? Human Tool

One app, one operating loop

GitHub and Azure operating architecture GitHub Actions deploys a reviewed repository change to App Service. Azure Monitor sends signals to an SRE agent, which uses repository context and proposes a scoped action for approval. GITHUB AZURE REVIEW + SHIP SIGNALS ACTION CODE CONTEXT GitHub repo code + runbook GitHub Actions tests + deploy App Service one nonproduction app Azure Monitor telemetry SRE Agent investigate + propose

Upgrade code. Plan the migration.

Two paths to a tested change From an existing application, upgrade frameworks and dependencies or assess a platform migration. Test actual behavior before reviewing and deploying either change. CODE PLATFORM App Change scope? Upgrade code framework + packages Plan migration assess readiness Test behavior Deploy after review

Recovery must be verified

A bounded incident recovery A sandbox alert moves through investigation, proposal, reviewed action, and a user-journey check. Verification ends in recovered or escalated, without an automatic retry loop. PRIMARY PHASES WAIT / REVIEW TERMINAL OUTCOMES REVIEW APPROVED PASS FAIL DENIED Alert Inspect + propose Act Verify Await approval human consent Recovered Escalate

Permission is not approval

Five independent operating controls Scoped identity, Azure action review, connector policies, GitHub release protections, and post-action health checks govern different parts of operation. ENFORCEMENT SURFACE CONTROL · ACTOR · TIMING EXCEPTION / GAP 01 Identity Workload identity PLATFORM · RUN Resource roles PLATFORM · RUN Scope limits PLATFORM · RUN Emergency access not specified 02 Action policy Azure review HUMAN · RUN Connector policy PLATFORM · RUN Tool hooks PLATFORM · RUN Other tools: define separately 03 Merge Required review HUMAN · MERGE Branch rules PLATFORM · MERGE Required tests CODE · MERGE Bypass route not specified 04 Deploy Environment gate HUMAN · DEPLOY OIDC identity PLATFORM · DEPLOY Release workflow PLATFORM · DEPLOY Denied approval: no deploy 05 Verify Telemetry alert PLATFORM · RUN Journey check HUMAN · AFTER ACTION Escalation owner HUMAN · FAILURE Failed check: escalate Illustrative control map · verify each control and exception path in the target environment

References

This talk explains two connected jobs: modernizing software and restoring service safely. It is a conceptual walkthrough and a proposed nonproduction exercise, not a report of a completed deployment.

Modernization changes the application over time. Incident response restores an acceptable operating state. The loops connect through evidence: a recurring incident can become an issue with logs, a reproduction, and a proposed durable fix. "ZeroOps" describes an ambition to reduce toil, not the disappearance of operational responsibility.

The model does not directly restart a service. A runtime invokes a tool under configured permissions and policies. Resource permissions answer what an identity can access. Approval and tool policy answer which actions need consent or are denied. Review mode gates Azure infrastructure actions; other connector actions need their own policies or hooks. Reference: https://learn.microsoft.com/en-us/azure/sre-agent/run-modes

This is a logical architecture, not a network or resource-containment diagram. Start with one nonproduction App Service application. Keep application code, infrastructure definitions, tests, and an operational runbook together in the repository. The approval gate represents human consent plus tool policies; the agent's identity separately needs the required resource permission. Repository Code Access and GitHub issue/workflow connectors are separate capabilities. References: https://learn.microsoft.com/en-us/azure/sre-agent/github-connector and https://learn.microsoft.com/en-us/azure/sre-agent/overview

An upgrade changes frameworks, dependencies, and project formats. A migration assesses readiness and plans supported changes for a target platform. The work can be done separately or together. Build success alone does not establish that business behavior is unchanged. References: https://learn.microsoft.com/en-us/dotnet/core/porting/github-copilot-upgrade/overview and https://learn.microsoft.com/en-us/azure/developer/github-copilot-app-modernization/overview

Connect telemetry and an availability alert to SRE Agent. Set the response plan to Review before stopping a nonproduction app. Inspect the diagnosis and proposed start action; approve only the action scoped to that application. Check the endpoint and a representative user journey. The pass/fail branches are the outcome; command success alone is not recovery. The example's consecutive checks and one-attempt limit are proposed lab rules, not measured results or production objectives. Reference: https://learn.microsoft.com/en-us/azure/sre-agent/run-modes

These controls solve different problems. An approval does not grant resource permission. Review gates Azure infrastructure actions, not every connector write; other tools require their own policies or hooks. Use scoped identities, branch and environment protections, audit trails, bounded actions, and a named escalation owner. References: https://learn.microsoft.com/en-us/azure/sre-agent/run-modes, https://learn.microsoft.com/en-us/azure/sre-agent/github-connector, and https://docs.github.com/en/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-azure

Documentation checked November 12, 2026.