All Integrations
Azure Blob Storage
x

Connect Azure Blob Storage to Pigment and retire manual uploads

Load the CSV extracts your data teams already store in Azure Blob Storage into Pigment, and export planning data to your Azure storage through Pigment’s API. Built for IT and Transformation teams fitting planning into an existing Azure stack, and for FP&A teams who want current actuals without handling files.

Azure Blob Storage

Azure Blob Storage

Import CSV files from Azure Blob Storage containers into Pigment Blocks, then reuse or schedule the import.

Category

File Storage Systems

Integration method

Native Connector
API

Best for

ERP actuals loads · HR and salary extracts · data lake landing zones

See documentation

What can you do with Azure Blob Storage and Pigment?

  • Refresh the forecast after close. An FP&A analyst points a saved import at the newest dated actuals file and reruns it after each close, so variance analysis starts from the extract the data team published.
  • Load the latest salary extract. HR and workforce planning teams pull the newest dated salary file into a headcount Block, so compensation modeling runs on current pay data.
  • Keep regional data separate. IT gives each region's container its own named connection, so planners pick the right source by name.
  • Give modelers data without Azure credentials. IT stores the connection’s credentials in Pigment, so model builders import without their own Azure access.

How the Azure Blob Storage integration works

Setup starts in Azure, where an administrator creates an App Registration with a client secret and assigns it the Storage Blob Data Reader role on the container. In Pigment, a Workspace Admin adds the connection in Workspace Settings with the Application ID, Directory ID, secret, account name, and container name.

To import into a Block, choose Import data in the Block header, or Start from an import for a new Block, then pick the connection. Pigment loads either one fixed file or the most recent file that matches a dated naming convention, and you can save the import to reuse or schedule it. Exports run through a different path, with Azure Data Factory calling the Pigment REST API and saving Views, Lists, Metrics, or Tables as CSV files in Azure Data Lake Storage Gen2.

Key capabilities

  • Keep your pipeline’s file names. Pigment reads ISO 8601 dates in file or folder names, so data teams don’t rename exports for planning.
  • Grant read-only access by container. Pigment reads through an App Registration with the Storage Blob Data Reader role on each container, so Azure administrators decide exactly what Pigment can read.
  • Enter credentials only once. Credentials go into Workspace Settings once, so model builders only select the connection and never handle the client secret.
  • Turn recurring loads into settings. Save an import configuration, then reuse or schedule it, so nobody rebuilds the same load each cycle.
  • Export on your own schedule. Run the export from Azure Data Factory on a schedule, and choose which Views, Lists, Metrics, or Tables land in your Azure storage.

View technical documentation

Frequently Asked Questions

Which file formats and import modes does the Azure Blob Storage integration support?

The integration loads CSV files in two modes. Fixed file mode loads one exact path, such as folder1/folder2/file.csv. Most recent file mode uses a date placeholder in the file or folder name and loads the newest matching file.

Can I connect more than one container?

Yes. Each connection points to one container, so you create a separate connection for every container you want to import from.

Can Azure Blob Storage imports run on a schedule?

Yes. You can schedule a saved import configuration to run automatically, with up to four schedules per configuration and notifications if an import fails. With most recent file mode, each scheduled run picks up the newest dated file in the folder.

Can Pigment export data to Azure storage?

Yes, through the Pigment REST API rather than the native connector. Azure Data Factory calls the export API and saves data from Views, Lists, Metrics, or Tables as CSV files in Azure Data Lake Storage Gen2, which is built on Azure Blob Storage.

See Pigment in action

The fastest way to understand Pigment is to see it in action. Sign up today and explore how agentic AI can transform the way you plan.

Three colleagues focused on an iMac screen in a bright office with plants and modern artwork.

From 8 days to 4 min

Update P&L actuals & financial forecasting

80%

Time cut on data aggregation

12 hours

Saved per month on executive reporting

6 days faster

For scenarios creation and analysis