Azure OpenAI Service

Pull your Azure OpenAI spend into Flowstate so it sits next to payroll and projects rather than inside a subscription nobody in finance can open.

What syncs

Data	Grain
Invoiced cost	Per resource and service, per day, for the subscription you nominate

Azure Cost Management reports money, not tokens, and it has no user dimension — so per-person attribution comes from the Flowstate Agent rather than from Azure. The figures are your actual billed cost, so Flowstate treats them as authoritative and never adds price-table estimates on top.

What you'll see in Flowstate

• Spend reconciliation — Azure's billed cost next to Agent telemetry. See Spend.
• Per-project attribution — with the Agent, Azure OpenAI calls are attributed to a person, project and cost centre. See Attribution.
• Cost trends — daily burn across your Azure OpenAI deployments.

Getting started

You need Cost Management Reader on the subscription, plus someone who can add a federated credential to an Entra app registration (the app owner, or an Application Administrator, Cloud Application Administrator, Global Administrator or Hybrid Identity Administrator).

Flowstate reads Cost Management without a client secret. Your app registration trusts Flowstate's OIDC issuer, scoped to your organisation, so no credential is uploaded.

1. In Microsoft Entra, open your app registration → Certificates & secrets → Federated credentials → Add credential, and add one for Flowstate using the Other issuer scenario
2. Give that app Cost Management Reader on the subscription you want to track (granting it needs User Access Administrator or Owner on that scope)
3. In Flowstate, open Settings → Integrations → Azure OpenAI Service, paste the tenant, client and subscription ids, then click Verify and connect — Flowstate makes one read-only call to check it works before saving anything

Enterprise Agreement customers need one extra switch

On an EA, the RBAC role alone is not enough. An Enterprise Administrator must also turn on the "Account owners can view charges" policy under Cost Management + Billing → Billing scopes → Billing account → Policies. Without it, every query comes back empty and the connection looks broken when it isn't.

How syncing works

Spend syncs hourly, and the first connect backfills history automatically.

Azure retains cost data well beyond a year, but the Cost Management surface exposes roughly the last 13 months — that is the practical ceiling on how far back the first backfill reaches.

If the federated credential or the role assignment is wrong, the connection shows Azure's real error on its provider page rather than reporting no spend.