Self-Healing Operations

A diagram-led introduction to AI-assisted modernization and safer operations with GitHub and Azure.

Format:
talk
When:
Slides:
8
Download
Open presentation

Arrow keys to navigate. F for fullscreen. P for presenter notes.

Read all slides

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