Cloud Editor @InfoQ, Microsoft Azure MVP, Crew Member @AzureLowLands, Traveller, Runner, #Seahawks, #SeaUsRise, #SeaKraken, Metal Music, Opinions are my own!

Ede, Gelderland, Netherlands
MCP vs API is the wrong question. I put both in one Azure Functions app: same backend, a REST door for developers, an MCP door for agents. The agent chained three tools nobody orchestrated. Full sample, Bicep, and deploy lessons: dev.to/steefjan_wiggers_34a4… #azurefunctions #mcp
1
1
90
47,004 input tokens for a 280-token answer. My scam-checking agent on Azure Functions hosted skills taught me when NOT to let the model orchestrate: gather evidence in code, keep judgment in the model. Full story + repo: dev.to/steefjan_wiggers_34a4… #azurefunctions #aiagents
92
Multi-agent systems need two memory scopes: shared state for coordination and private state to keep each agent's persona separate. Handoff mechanism: change feed. One agent's write is the next agent's signal; no polling. @AzureCosmosDB sjwiggers.com/2026/09/10/cos…
1
96
SteefJan Wiggers (aka Lian’s Husband) retweeted
What happens when you actually build nine agentic AI design patterns on Azure instead of just diagramming them? Steef-Jan Wiggers shares what worked, what broke, and lessons around Azure Cosmos DB RBAC, Foundry, Event Grid, Bicep, and more. msft.it/6011aTZ8W #AzureCosmosDB #AgenticAI
2
7
610
Partition key and item shape decide whether a Cosmos DB agent memory schema holds up. TTL trick: -1 on the container, override per item. Short-term turns expire; long-term memories don't. Same container. sjwiggers.com/2026/09/01/cos… #agenticai
3
2
85
Agent ≠ Model. Foundry's model router now spans 28 regions and refreshes its pool under a stable endpoint. Models are becoming swappable parts; the durable investment is the control plane. Where routing is the wrong answer: sjwiggers.com/2026/08/31/bui… #microsoftfoundry
85