Skip to main content
Azure Blob triggers start Planasonix pipelines when new blobs appear in Azure Storage containers. You wire Event Grid to emit Blob Created events, then point Planasonix at the event destination (webhook, queue, or event hub pattern) your deployment supports.
See Triggers for shared guidance on filters, duplicate events, and idempotent processing.

​
Event Grid subscription setup

1

Choose the storage account scope

In Azure Portal → your Storage account → Events, or in Event Grid → Subscriptions → + Event subscription, select the storage account or a specific container as the event source, depending on how narrowly you want to scope emissions.
2

Select the blob created event

For new files, subscribe to Blob Created (Microsoft.Storage.BlobCreated). Omit unrelated event types to reduce volume and cost.
3

Configure the endpoint

Choose the endpoint type Planasonix documents for your tenant—often Web Hook with a validation handshake, Storage Queue for durable buffering, or Event Hubs for high throughput. Apply filters before the endpoint when possible.
4

Name and save the subscription

Use a descriptive name (planasonix-landing-created). Confirm metrics show deliveries after you upload a test blob.

​
Container and blob path filters

Event Grid supports subject begins with and subject ends with filters on blob events. Typical patterns:
Filter subject begins with to /blobServices/default/containers/<container-name>/blobs/<optional-prefix> so only that container (and optional virtual folder) emits events.
Align Event Grid filters with Planasonix trigger filters so you do not pay to deliver events the pipeline will ignore—or worse, accidentally broaden filters later without updating both places.
Blob events can arrive more than once or out of order relative to producer intent. Design loads to tolerate duplicates (ETag, file name manifests, merge keys).

​
Authentication: managed identity or connection string

Choose how Planasonix (or your middleware) authenticates to Azure when it reads blobs or pulls from queues.
Some integrations accept a connection string or SAS token scoped to the container and allowed operations (rl read/list as needed). Rotate SAS before expiry; prefer short-lived SAS with IP restrictions when you must use tokens.
When Event Grid pushes to a webhook, complete the validation handshake Planasonix exposes. For queue endpoints, ensure the data plane role can enqueue and Planasonix can dequeue with matching credentials.

​
Network rules and private endpoints

If the storage account uses firewalls or private endpoints, allow Event Grid infrastructure and Planasonix egress paths as required by Microsoft’s documentation for your endpoint type. Misconfigured networks produce delivery failures in Event Grid metrics with no application-level error in Planasonix.
Turning on storage firewalls without updating trusted services and subnet rules breaks both blob reads and event delivery. Test with a non-production storage account first.
In Planasonix, create or edit an Azure Blob trigger:
  • Provide subscription identifiers, endpoint URLs, or connection references as prompted.
  • Mirror prefix/suffix logic if the product applies a second filter layer.
  • Run a test upload and confirm a pipeline run (or a queued run) appears in orchestration history.

Triggers overview

Event ordering, security, and batching concepts.

Cloud storage connections

Azure Storage credential patterns.