DevBlogs
Read post

Building an operations assistant on Azure that waits for approval before it acts

A reference implementation of an operations assistant on Azure that enforces human approval before executing mutations. The assistant retrieves runbooks via Azure AI Search using hybrid lexical+vector search with semantic reranking, calls Azure OpenAI for reasoning, and separates read-only tool calls from write operations. When the model proposes an action like opening an incident, it records a pending action and returns a preview — execution only happens after the authenticated user explicitly confirms. Key engineering decisions covered include: identity-scoped session isolation using Container Apps Entra ID auth headers, managed identity for keyless Azure service access, idempotent confirmation handling with in-process locking, separate telemetry vs. audit streams, and honest acknowledgment of what the single-replica in-memory design cannot yet handle at scale.

    #azure#ai-agents
Aug 03•10m read time•From devblogs.microsoft.com
Post cover image
Table of contents
The shape of it Copy linkRetrieve the evidence before you ask the model anything Copy linkKeep the read path and the write path apart Copy linkPut identity where the authorization decision is Copy linkLet managed identity carry the credentials Copy linkIdempotency and concurrency are backend problems, not model problems Copy linkTelemetry and audit answer different questions Copy linkWhat this slice does not pretend to solve Copy link
188 Impressions
DevBlogs's image
DevBlogs

DevBlogs is a curated collection of articles and blog posts from developers and tech enthusiasts wor...

1.1K Followers

•

5.1K Upvotes

Would you recommend this post?

Copy link
WhatsApp
Facebook
X
New Squad
  • © 2026 Daily Dev Ltd.
  • Guidelines
  • Explore
  • Tags
  • Sources
  • Squads
  • Leaderboard