All Integrations
Azure SQL
x

Connect Azure SQL to Pigment and plan from current actuals

Bring actuals and operational data from Azure SQL into Pigment through a native connector, so forecasts and planning models start from current numbers. FP&A teams forecast and report without rebuilding extracts each cycle. IT keeps the connection read-only and controls which Applications can use it.

Azure SQL

Azure SQL

Import data from Azure SQL into Pigment to forecast, report, and plan from current actuals

Category

Data Warehouses & Lakehouses

Integration method

Native Connector

Best for

Actuals refresh · Forecasting · Variance analysis

See documentation

What can you do with Azure SQL and Pigment?

  • Start variance reviews from current actuals. Schedule an actuals import from Azure SQL so budget-versus-actual analysis starts from current numbers.
  • Build drivers from transaction detail. Import transaction-level records into a Transaction List, then model your forecast drivers from that detail.
  • Import only what plans need. Write a SQL query filtered to the entities, periods, or accounts you're planning, and nothing else.
  • Time refreshes around reporting deadlines. Run imports ahead of each reporting cycle so FP&A builds the management pack from the latest data, without requesting a new extract from IT.

How the Azure SQL integration works

Pigment connects to Azure SQL Database, Azure SQL Managed Instance, or Microsoft Fabric Data Warehouse. On the Azure side, your administrator registers an application in Microsoft Entra ID (formerly Azure AD) to act as Pigment's service account. They grant it the read-only db_datareader role and add Pigment's 4 server IP addresses to the firewall allowlist.

A Workspace Admin then adds the Azure SQL connection in Pigment's integration settings and chooses which Applications can use it. From there, you open the import screen for the object you want to fill, such as a Transaction List, and enter a SQL query.

Key capabilities

  • Combine tables before import. Pigment imports your SQL query's results, so you can join and aggregate tables in the database before data reaches your model.
  • Keep the source database read-only. Pigment's service account gets only the db_datareader role, so planning work can’t change the data other systems rely on.
  • Control which Applications connect. Workspace Admins choose which Applications can use each connection, keeping sensitive data with the models that need it.
  • Set imports to run on their own. Schedule each import up to 4 times, such as weekly and month-end runs, and get notified in Pigment, by email, or in Slack if a run fails.
  • Govern access through groups. Grant access directly or through a Microsoft Entra ID security group, so IT manages Pigment like other database access.

Frequently Asked Questions

What data can I import from Azure SQL into Pigment?

You import the results of a SQL query you write into the Pigment object you choose, such as a Transaction List. To bring in a specific table or view, reference it in your query.

Can FP&A teams refresh actuals without asking IT for a new extract each time?

Yes. After IT and a Workspace Admin set up the connection, people working in Applications with access can run imports from the import screen. Scheduled imports then keep the data current without anyone rerunning them by hand.

Can Pigment send data back to Azure SQL?

Not through the Azure SQL connector, which only imports data. Pigment can export data as CSV files to Azure Data Lake Storage Gen2, and your team can load it into Azure SQL from there.

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