Free Starter Pack Before you start using Claude for Excel, apply these best practices
← All Integrations
Azure Blob Storage Logo

Azure Blob Storage + Go Fig

Data Stack

Connect Azure Blob Storage to Go Fig for seamless file-based data integration.

Azure Blob Storage holds critical business data for many organizations. Go Fig connects to your blob containers, processing files automatically and incorporating them into your unified financial data platform. Handle exports, partner feeds, and archival data with ease.

Key facts

File formats
Parquet, CSV, JSON, XLSX
Auth
SAS, Service Principal, Managed Identity
Containers
Multi-container per connection
Sync mode
Blob-version tracked

SOC 2 Type II ยท All integrations

What you can do with Azure Blob Storage data in Go Fig

Azure Ecosystem Integration

Pull data from Azure-native applications and services via blob storage.

Export Processing

Automatically process data exports from systems that write to Azure.

Cross-Cloud Analytics

Combine Azure data with AWS and GCP sources in one platform.

Data available from Azure Blob Storage

Go Fig extracts and normalizes the following data from your Azure Blob Storage account:

Blob files
Container contents
CSV/Excel data
JSON documents
Parquet files
File metadata
Change detection
Archive tiers

How to connect Azure Blob Storage

1

Choose an authentication method

For a quick start, generate a read-only SAS token scoped to the container Go Fig should access. For production, register a Service Principal in Azure AD and grant Storage Blob Data Reader on the storage account or container.

2

Configure containers and prefixes

Specify storage account, container name, and optional prefix path. Go Fig respects Azure's hierarchical namespace if you're on Azure Data Lake Storage Gen2, so directory traversal is efficient even on multi-million-blob containers.

3

Handle archive-tier files

Blobs in Cool or Archive tiers have higher retrieval latency and cost. Go Fig flags Archive-tier files at sync time rather than transparently rehydrating them, so you don't get a surprise Azure bill from a backfill job that touches old data.

4

Schedule and route data

Default polling is every 15 minutes; Event Grid notifications enable near-real-time ingestion. Once landed, blob data flows into the same warehouse layer as your QuickBooks, Salesforce, and HRIS data for joined analysis.

Authentication: Connection options: SAS token (scoped to specific containers and read-only), Service Principal via Azure AD, or Managed Identity if Go Fig is running in your tenant. SAS is fastest to set up; Service Principal is the standard enterprise path.

Common Questions About Azure Blob Storage Integration

Does Go Fig support Azure Data Lake Storage Gen2 (ADLS Gen2)?

Yes. ADLS Gen2 hierarchical namespaces are first-class. This means directory listings, ACL-based access control, and Hive-partitioned queries all behave correctly. If you're using ADLS for an Azure-native lakehouse pattern, Go Fig integrates without any data movement.

Which authentication methods does Go Fig support?

SAS tokens for fastest setup (recommended for proof-of-concept), Service Principal via Azure AD for production, and Managed Identity for customers running Go Fig in their own Azure tenant. Account keys are supported but not recommended because they grant full storage account access.

How does Go Fig handle Azure's blob tiering (Hot, Cool, Archive)?

Hot and Cool blobs are read normally with appropriate cost awareness in our docs. Archive-tier blobs are not auto-rehydrated; Go Fig surfaces them in the file list with a flag so you can decide whether to rehydrate (which has cost and latency implications) or skip. This avoids surprise rehydration bills.

Can Go Fig handle Excel (.xlsx) files in blob storage?

Yes. .xlsx is a common export format from Microsoft-heavy finance teams. Go Fig parses sheet-by-sheet, preserving sheet name as a column. Multi-sheet workbooks (e.g., a P&L workbook with one sheet per entity) can be pivoted into a single normalized table by a flow.

What about private endpoints and VNet restrictions?

If your storage account is locked to a VNet via Private Endpoint, Go Fig's egress IPs can be allowlisted in your network rules. For stricter environments, the connector can run inside your own Azure tenant via a customer-deployed runner so traffic never leaves your VNet.

Industries running Azure Blob Storage with Go Fig

Strategic CFOs in these industries typically stitch Azure Blob Storage into their Financial Intelligence Graph alongside their ERP and operational systems.

Ready to connect Azure Blob Storage?

See how your Azure Blob Storage data looks in Go Fig with a personalized demo.

Book a Demo