Linking Microsoft Azure Cost Management as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Microsoft Azure Cost Management connector syncs cost by service, cost by resource group, cost by resource, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Pull your daily Azure spend, broken down by service, resource group, and resource.
Register an app in Microsoft Entra ID, create a client secret for it, and give its service principal the Cost Management Reader role on the scope you want to sync. Then enter the directory (tenant) ID, the application (client) ID, and the secret value.
The scope is the Azure Resource Manager path to read cost for, without a leading slash - for example subscriptions/00000000-0000-0000-0000-000000000000 for one subscription, or providers/Microsoft.Billing/billingAccounts/1234567 for an enterprise billing account.
You'll be asked for:
- Directory (tenant) ID: for example
00000000-0000-0000-0000-000000000000. - Application (client) ID: for example
00000000-0000-0000-0000-000000000000. - Client secret
- Scope: for example
subscriptions/00000000-0000-0000-0000-000000000000.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Some Microsoft Azure Cost Management tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
Directory (tenant) ID | text | Yes |
Application (client) ID | text | Yes |
Client secret | password | Yes |
Scope | text | Yes |
Start date (historical backfill) | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
cost_by_service | Daily actual cost per Azure service. Supports incremental sync on the usage date. | Incremental, Full refresh | usage_date | — |
cost_by_resource_group | Daily actual cost per resource group. Supports incremental sync on the usage date. | Incremental, Full refresh | usage_date | — |
cost_by_resource | Daily actual cost per resource. The widest table — one row per resource per day. | Incremental, Full refresh | usage_date | — |
amortized_cost_by_service | Daily amortized cost per Azure service, spreading reservation and savings-plan purchases across their term. | Incremental, Full refresh | usage_date | — |
forecast | Azure's forecast of upcoming daily cost per service. Full refresh only. | Full refresh | — | — |
dimensions | Dimensions available for grouping and filtering cost on this scope. Full refresh only. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the client secret is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.