Notes from building on Azure.
Practical writing on the problems InsightForge, BulkForge, and Vigil actually solve — plus digital legacy planning from Dad Is Dead. No product pitches disguised as articles.
Azure Key Vault's own near-expiry events cover less than most teams assume. Here's exactly what's missing, and what it takes to close the gap yourself.
Teams migrating between providers, or running both during a transition, lose visibility the moment delivery data splits across two dashboards. Here's what that actually costs you.
Every bulk-send platform asks for your API key up front. Here's what you're actually agreeing to when you hand it over, and why regulated teams increasingly won't.
A direct answer: Key Vault emits a near-expiry event for certificates, secrets, and keys — but none of it is wired to anything by default. Here's exactly what Key Vault does and doesn't warn you about.
A single bounce-rate number hides the difference between a typo in an email address and a sender-reputation problem that's about to get worse.
Every new bulk-send tool is another vendor with access to your delivery credentials. Here's why that chain keeps growing, and how to add scale without adding a link to it.
SendGrid joins Postmark and Azure Communication Services as a connected provider. Here's exactly what's covered, what setup looks like, and what isn't included yet.
BulkForge now supports SendGrid alongside Postmark and Azure Communication Services. Here's what changes, what doesn't, and why it matters more than a checkbox on a feature list.
One Key Vault is fine to monitor by hand. Here's the point where per-vault alerting stops being manageable, and what changes once you're past it.
Most bulk-send tools take your API key and send on their behalf. BulkForge deploys an agent into your own Azure subscription instead — here's the mechanics, and the trade-off.