Sending Bulk Email on Azure, and Finding Out What Happened

Sending a large batch of email and understanding what happened to it are two different jobs, and most teams end up with two different tools for them. BulkForge and InsightForge are built for exactly that split. BulkForge sends. InsightForge shows you what the providers reported afterwards. This post covers how they fit together, and where they stop.

The sending half: BulkForge

BulkForge orchestrates bulk sends: scheduling, job dispatch and a per-recipient audit trail. A BulkForge agent runs as Azure Functions in your own subscription and delivers through your own Postmark, Azure Communication Services or SendGrid account, with the delivery credential held in your Key Vault. BulkForge is not an email provider, and the delivery itself happens at the provider.

The explaining half: InsightForge

Once a message has left, the interesting facts are at the provider: which messages bounced, which drew complaints, how long delivery took. InsightForge is deployed into your Azure subscription, reads those events from Postmark, Azure Communication Services and SendGrid, and puts them in one dashboard. For an individual bounce it can also explain the failure in plain English, using an Azure OpenAI resource you own.

Why they pair

• The same three providers. Both products work with Postmark, Azure Communication Services and SendGrid, so you do not need a different habit for each one.
• The same deployment model. Both run in your own Azure subscription, and both keep provider credentials with you rather than in a vendor-hosted database.
• A send is not the end of the job. A bulk send that finished without errors can still produce bounces and complaints. The send record tells you what was dispatched. The provider's events tell you what then happened to it.

How to set them up together

Install each from the Azure Marketplace; they are separate offers with separate plans. In InsightForge, connect the provider account that BulkForge sends through, for example the Postmark server or Azure Communication Services resource your BulkForge agent uses. Nothing needs to be configured inside BulkForge for this.

What they do not do

• There is no direct integration. BulkForge does not push anything to InsightForge. InsightForge reads from your provider, so it sees whatever that provider account sent, whether or not BulkForge sent it.
• InsightForge does not change how BulkForge sends. It explains and reports. It does not edit suppression lists, DNS or sending settings, and it does not pause a job.
• They are priced and bought separately. You can run either one without the other.