Reference · built on requestConnectorFiles, documents & spreadsheets

Azure Blob Storage

Containers and blobs in Azure Blob Storage through the Blob Service REST API, with Event Grid events on blob writes.

Request accessPricing ↗

About

Azure Blob Storage holds text and binary objects in a storage account. Its REST API at <account>.blob.core.windows.net defines operations on the account, its containers, and block, append, and page blobs: List Blobs, Get Blob, Put Blob, Set Blob Metadata, Set Blob Tags, Set Blob Tier, Lease Blob, and Copy Blob among them. Storage accounts of kind StorageV2, BlockBlobStorage, and BlobStorage publish Microsoft.Storage.BlobCreated and BlobDeleted events to Event Grid.

Through Fibric, an operator receives those events, reads the blob's properties and index tags, and proposes an upload, a tag, a metadata change, or a tier move. You approve it. A receipt records what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Azure Blob Storage and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Blobs in a container through List Blobs, up to 5,000 items a page with a NextMarker continuation token
  • Blob properties, user metadata, and index tags through Get Blob Properties, Get Blob Metadata, and Get Blob Tags
  • Blobs matching a tag expression across the account through Find Blobs By Tags
  • Soft-deleted blobs, snapshots, versions, immutability policy, and legal hold when List Blobs includes them
  • Microsoft.Storage.BlobCreated and Microsoft.Storage.BlobDeleted events from Event Grid, with api, blobType, contentLength, url, and sequencer
  • Microsoft.Storage.BlobTierChanged and Microsoft.Storage.LifecyclePolicyCompleted events when tiering or a lifecycle policy runs

Proposed actions

  • Target capability: propose an upload through Put Blob, or Put Block and Put Block List for blobs over 5,000 MiB
  • Target capability: propose index tags through Set Blob Tags, with the tag set shown before it applies
  • Target capability: propose user metadata through Set Blob Metadata
  • Target capability: propose a tier move through Set Blob Tier, or a copy through Copy Blob into another container or account

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Prove the nightly backup arrived

    The operator filters BlobCreated events by subject prefix on the backup container, checks contentLength and eventTime against the expected window, and proposes a record of what landed and what did not.

    With Backup Proof

  • Find evidence that carries no hold

    The operator lists a container with legalhold and immutabilitypolicy included, flags evidence blobs that carry neither, and proposes an index tag naming the matter so a person can apply the hold.

    With Compliance Evidence, Audit Trail

  • Tier cold data before the bill grows

    The operator sums contentLength by container from List Blobs, reads each blob's properties for its last write, and proposes a Set Blob Tier move for your approval.

    With Storage Growth, Idle Resources

Requirements

  • A storage account created with the Azure Resource Manager deployment model, since only those accept Microsoft Entra authorization
  • A role assignment for Storage Blob Data Reader, or Storage Blob Data Contributor where writes are approved, scoped to the container or account
  • For events, an account of kind StorageV2, BlockBlobStorage, or BlobStorage and an Event Grid subscription on it
  • REST API version 2017-11-09 or later for Microsoft Entra authorization, and 2019-12-12 or later for blob index tags
Authentication
A Microsoft Entra ID service principal or managed identity holding an Azure RBAC role such as Storage Blob Data Reader or Storage Blob Data Contributor, sending OAuth 2.0 bearer tokens; Shared Key and SAS remain options.

Limits

  • Role assignments can take up to 30 minutes to propagate before data access works
  • List Blobs returns at most 5,000 items a call; a full listing walks NextMarker until it is empty
  • BlobCreated fires on PutBlob, PutBlockList, and CopyBlob once a block blob is committed; general-purpose v1 accounts emit no events
  • A hot partition returns 503 Server Busy or 500 Operation Timeout before the account reaches its published targets; retries need exponential backoff

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Azure Blob Storage ↗

Questions and answers

Which operations raise a Microsoft.Storage.BlobCreated event?
PutBlob, PutBlockList, and CopyBlob on the Blob REST API, once the block blob is fully committed. On accounts with a hierarchical namespace, CreateFile and FlushWithClose raise it; filter on FlushWithClose to see only committed files. SFTP uploads raise two events, SftpCreate and SftpCommit.
Can Fibric read blob data with a Contributor role on the account?
No. Owner, Contributor, and Storage Account Contributor manage the account but grant no blob data access through Microsoft Entra ID. Fibric needs Storage Blob Data Reader, or Storage Blob Data Contributor for approved writes, assigned at container or account scope.
How large can a block blob be?
A block blob holds up to 50,000 blocks of 4,000 MiB each, about 190.7 TiB, on service version 2019-12-12 or later. A single Put Blob write is capped at 5,000 MiB. An append blob reaches about 195 GiB and a page blob 8 TiB.
Ask about Azure Blob Storage

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Azure Blob Storage through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy