Content & Documents · Integration
Azure Blob Storage
Add Azure Blob Storage to your product for your customers, and give your AI agents governed access to it.
Object storage looks simple until the details bite. A Blob Storage integration works containers and the blobs inside them, along with blob metadata, ETags and versions, in a storage account the customer owns. Two facts drive the design. Access tiers change what a read costs and whether it works at all, because an archived blob has to be rehydrated before anything can open it, and that takes hours rather than milliseconds. And a shared access signature is minted with a fixed expiry, so a link handed to a long-running job or a slow uploader can die halfway through and needs reissuing rather than retrying. fastn keeps each account's credentials, mints signatures with sensible lifetimes and tracks the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer nominate their own container so files your product produces land in storage they already govern.
Check the access tier before you promise a read, since an archived blob has to be rehydrated first.
Hand out short-lived signed URLs for uploads and downloads instead of routing the bytes through your own servers.
Use ETags so a concurrent write does not quietly overwrite a blob another process changed a moment earlier.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists what is in a container and reads a permitted blob, and the container it touched is recorded.
An agent uploads a file your product produced into the container that customer approved, with the write attributed.
An agent reports that a requested blob is archived and says what rehydrating it would involve.
Example prompt
What is in this container from last month, and which blobs are sitting on an archive tier?
Set up Azure Blob Storage in 4 steps
- 01Enable the Azure Blob Storage connector from your fastn dashboard.
- 02Have each customer authorise their own Azure Blob Storage account, so calls run under their credentials rather than a shared key.
- 03Decide which containers, blobs and access tiers your product needs, and decide how long a shared access signature should live for the jobs that use it.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Azure Blob Storage integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Azure Blob Storage integration without building it. Your customers connect their own Azure Blob Storage account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Azure Blob Storage update is not your on-call problem.
- One integration serves your product and your agents. The same governed Azure Blob Storage connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
AWS Simple Storage Service
Azure File Storage
WasabiOften used alongside
Tools the same teams tend to run next to Azure Blob Storage, across other categories.
Shopify
Stripe
Jira
AsanaAzure Blob Storage integration FAQ
How do I add an Azure Blob Storage integration to my product?
Enable the Azure Blob Storage connector in your fastn dashboard, then let each customer authenticate their own Azure Blob Storage account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Azure Blob Storage client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Azure Blob Storage account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Azure Blob Storage account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Azure Blob Storage integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent lists what is in a container and reads a permitted blob, and the container it touched is recorded.
Who maintains the Azure Blob Storage integration?
fastn does. When Azure Blob Storage changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the Azure Blob Storage integration run under?
Each customer's own Azure Blob Storage grant. Where Azure Blob Storage holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Azure Blob Storage automatically?
Where Azure Blob Storage supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Azure Blob Storage integration?
A common starting point: let a customer nominate their own container so files your product produces land in storage they already govern. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Azure Blob Storage integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Azure Blob Storage does not change your per-connector cost. You can start free with 3 connected accounts.
Add Azure Blob Storage to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.