Topic
Azure & Architecture
Identity, deployment, events, recovery and the boundaries that decide how a cloud system behaves.
Human Approval After a Restart: One Reviewed Proposal, One Local Effect
Bind approval to the exact draft, evidence and policy, resume a pending review from an Agent Framework checkpoint in a new process, and recover a lost receipt without a second effect.
Azure Decision APIs: Root, Deployment, Operation and Token Audience
Microsoft-Decision-1 and Azure OpenAI Decisions use different paths, serializers and token audiences. Bind each to one validated C# profile and keep the token inside the deadline.
The Hidden Network Work of a Blazor Search Box
Out-of-order responses, stale errors and abandoned server work in a Blazor search box, reproduced on .NET 10, and a component where debounce, cancellation and a generation each do their job.
Copilot Studio over Direct Line: Track Accepted Work, Not Chat Bubbles
A Direct Line page is a batch of activities, not an answer. Build a .NET client that keys acceptance by task, keeps the watermark opaque and commits each page atomically.
Reservation Confirmed or Work Accepted: What 201 and 202 Promise
A 202 promises an operation, not a reservation. Build both designs on SQL Server: idempotent admission, a claim that really skips locked rows, and leases fenced by generation.
The Cost of One Task on Azure: Metered, Allocated and Reconciled
Azure bills resources, not tasks. Measure model tokens per task, pick billed or amortized cost, allocate shared cost by a named policy in exact cents, and reconcile with the meter.
A Minimal .NET Agent Platform: Four Jobs, Two Workers, One Restart
Stop a small ASP.NET job service while it still owns work, then restart it. Four jobs show what can resume, what must wait, and what only the receiver's receipt can settle.
Permission Changed Mid-Answer: Gate the Write, Not Just the Check
A streamed answer that checks permission on every chunk can still leak after revocation. Gate the write, choose a snapshot contract deliberately, and keep retrieved text out of your logs.
Deployer, Runtime, Operator: Three Azure Identities and One Cache Key
Follow four tokens through one Azure service: audience checks, workspace membership, a cache key that leaks across tenants, and why publishing code is data access.
A recovery runbook should refuse the wrong next step
A SQL Server restore that verifies, opens and answers queries can still be the wrong database, miss a committed write or load the wrong file. Make each check permit exactly one next step.
A Verified SQL Backup Is Not Yet a Recovered Application
VERIFYONLY passed, CHECKDB was clean and the invoice service still failed. A SQL Server recovery drill that checks history, logins, TDE keys and the real operation.
Database Cutover: Fence the Old Writer Before You Move the Endpoint
A client timeout, a stale connection and a green probe can still split your history. Reconcile by operation key, fence the old writer inside the database, then route.