I have deployed Drasi enough times now to know exactly where the pain shows up: too much manual scaffolding, inconsistent post-provision steps, and "it worked in one environment but not the other" cluster setup drift.
So I built a custom Azure Developer CLI extension for AZD called azure.drasi to standardize that workflow end-to-end.
It gives you a clean, repeatable way to:
Today, we are going to look at a preview feature that solves one of the most common pain points in SPA (single page application) or Static Web App deployments - build-time environment variable injection - using Azure App Configuration with Azure Front Door.
If you have ever had to rebuild a React or Vue app just because the API URL changed between staging and production, this one is for you.
As the AI Dev Days Hackathon comes to an end, I want to share my submission.
Today, I want to walk through something I have been building over the last wee while - a project called NimbusIQ. It is my submission for the AI Dev Days Hackathon, and it sits across the Best Multi-Agent System and Best Enterprise Solution categories - NimbusIQ.
At its core, NimbusIQ is built on Microsoft Agent Framework - Microsoft's orchestration layer for composing multi-agent pipelines in .NET. It gives you a WorkflowBuilder pattern for wiring agents together with explicit edges, lifecycle management via InProcessExecution, and the structure needed to run ten specialised agents in a coordinated sequence without the whole thing becoming a tangle of custom plumbing.
Today, we are going to look at change-driven architecture on Azure using Drasi, and why it matters from a Well-Architected perspective.
If you have ever built a system that polls a database every few seconds, asking, "Has anything changed?" - this one is for you.
I recently built an Emergency Alert System and Santa Digital Workshop and Automate Azure Bastion with Drasi Realtime RBAC Monitoring proof of concepts on Azure that use Drasi for reactive data processing. One of the most interesting things I discovered was that change-driven architecture fundamentally shifts how you think about reliability, cost, and operational efficiency.
Every time I see a production container running as root, I wince.
It is one of those things that is easy to fix but gets overlooked because the app "works fine" without it. But container security is not just about non-root users. It is about the full stack: image build, runtime configuration, network policy, input validation, and rate limiting.
In this post, I will walk through a checklist I used to harden a .NET project running on Azure Container Apps.