Content & Documents · Integration

Azure File Storage

Add Azure File Storage to your product for your customers, and give your AI agents governed access to it.

Embed an Azure File Storage integration so your customers can read and write files in their own shares from inside your product, with access scoped per tenant and every call audited. Pagination and throttling are handled for you, so a large listing does not exhaust a customer's allowance.

Start freeBook a demo

In your product

Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.

Let customers read and write files in their own shares from your product.

List directories so your product can browse their existing structure.

Read file metadata so your product can act without downloading everything.

Trigger your product when a file is added or changed.

For your AI agents

Governed, audited access for the agents you build, through the MCP server.

An agent reads a file to answer a question grounded in the customer's own data.

An agent writes an output file within governed permissions.

An agent reacts to a new file and starts the next processing step.

Example prompt

List files added to this share in the last day over 5 MB, with their paths.

Set up Azure File Storage in 4 steps

  1. 01Open the Azure File Storage connector from your fastn dashboard.
  2. 02Have each customer authenticate their Azure storage account.
  3. 03Map the shares and directories your product may access, then enable actions and triggers.
  4. 04Call them from your product, or expose them to an agent through the MCP server.

Why teams use the Azure File Storage integration

What you get by embedding it with fastn instead of building it yourself.

  • Ship an Azure File Storage integration without building it. Your customers connect their own Azure File 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 File Storage update is not your on-call problem.
  • One integration serves your product and your agents. The same governed Azure File 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

MarketingHR & People OpsOperations

Compare with

AWS Simple Storage ServiceAzure Blob StorageMicrosoft OneDrive

Often used alongside

Tools the same teams tend to run next to Azure File Storage, across other categories.

ShopifyStripeJiraAsana

Azure File Storage integration FAQ

How do I add an Azure File Storage integration to my product?

Enable the Azure File Storage connector in your fastn dashboard, then let each customer authenticate their own Azure File Storage account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Azure File 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 File Storage account?

Yes. Every connection is scoped to the individual customer, so each authorises their own Azure File 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 File 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 reads a file to answer a question grounded in the customer's own data.

Who maintains the Azure File Storage integration?

fastn does. When Azure File 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 File Storage integration run under?

Each customer's own Azure File Storage grant. Where Azure File 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 File Storage automatically?

Where Azure File 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 File Storage integration?

A common starting point: read and write files in their own shares from your product. 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 File Storage integration cost?

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Azure File Storage does not change your per-connector cost. You can start free with 3 connected accounts.

Add Azure File Storage to your product

Start free with 3 connected accounts. No sales call required, and no per-customer integration code.

Start freeRead the docs
← All integrations